I have a repository which looks something like this:
/
/resources/resource1.txt
/resources/resource2.txt
/code/
/code/C/...
/code/java/pom.xml
/code/java/src/main/XYZ.java
/code/java/src/main/ABC.java
In other words, there is a maven project rooted in /code/java/, and there are resource files located at /resources/.
Now, I want to refer to the resource files in my code. The code will be something like the files in /code/java/src/main/XYZ.java. How should I refer to this file?
I do not want to hard code the filepath from my local machine. For example, I do not want something like /Users/agnishom/projectX/resources/resource1.txt. This will make it difficult for other people who clone my repository to make it work.
I would like to be able to name a file by their relative path, possibly relative to the pom.xml file.
What is the best way to do this? Moving the resource files into the /code/java/ is not an option because they are shared by other projects which are not part of the java
In the build section of your pom.xml, you can specify the resources directory relative to the project's base directory (/pom.xml), as you were suggesting:
<build>
...
<resources>
<resource>
<targetPath>.</targetPath>
<directory>${basedir}/../../resources</directory>
</resource>
</resources>
</build>
targetPath is the path to where included resources should be placed, relative to the jarfile/resulting build.
directory is the directory to include resources from.
I have configuration.properties in configs/Configuration.properties where I have url path = http://finacial/dev3/api
http:// financial/{env}/api
I want to load the environment value from the pom.xml to replace dev 3 according to the environment property set in pom.xml.
You could use the filter option of the maven resources plugin, it does exactly that.
Variables can be included in your resources. These variables, denoted by the ${...} delimiters, can come from the system properties, your project properties, from your filter resources and from the command line.
E.g. if you have a property url in your pom
<properties>
<url>abc</ulr>
</properties>
and your .properties file contains a value ${url} and you include the file in the resource section of the pom, then ${url} will be replaced in the output file in the build target location by abc upon issuing mvn resources:resources
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
I am having an issue running my cucumber project with device farm.
I am getting this error:
[TestNG] Caused by: java.lang.IllegalArgumentException: Not a file or directory: /tmp/scratchheDEgq.scratch/test-packagex5ZhYf/src/test/java/cucumber/features
I understand from this message that there is an issue with the path of the features directory in my project but locally it works.
This is how I put it in my code:
#CucumberOptions(features = "src/test/java/cucumber/features", glue = "cucumber.steps")
Should I provide a different path to device farm? What am I missing here?
Thanks
By default the src/test/java/cucmber directory(if it exists in the project) is not included the *-test.jar file. Try putting the feature files in the src/test/resources directory as shown in the Device Farm sample project.
https://github.com/aws-samples/aws-device-farm-appium-cucumber-tests-for-sample-app/tree/master/src/test/resources/LoginTest
Alternatively, you can implement the testResources tags in the pom.xml to explicitly reference another directory besides src/test/resources assuming that we're using maven:
<testResources>
<testResource>
<directory>${project.basedir}/src/test/YOUR_DIRECTORY_HERE</directory>
</testResource>
</testResources>
Check out this link for more info on the testResources tag
https://maven.apache.org/pom.html#Resources
testResources: The testResources element block contains testResource elements. Their definitions are similar to resource elements, but are naturally used during test phases. The one difference is that the default (Super POM defined) test resource directory for a project is ${basedir}/src/test/resources. Test resources are not deployed.
HTH
-James
In pom.xml of my java project, I have provided resource path like this,
<resource>
<directory>C:/Softwares/apache-tomcat-7.0.82/conf</directory>
</resource>
When I do mvn install, resource that is getting added is
C:Softwares/apache-tomcat-7.0.82/conf
Because of this, the following issue occurs
Build path entry is missing: C:Softwares/apache-tomcat-7.0.82/conf
I have tried pointing the directory thru environment variable like this,
${env.CATALINA_HOME}/conf
Still the problem exists.
It was a slash problem. The problem was resolved after I changed the path to
C:\Softwares\apache-tomcat-7.0.82\conf
I'm using Maven for desktop build application. I read about Maven standard directory layout and I have this project structure for now:
App
|-- pom.xml
`-- src
|-- main
|-- java
| `-- java classes
|-- resources
| `-- images
| `-- app images
`--config
`--config.xml
I want to find a way to load my resources and config files. I read some articles and topics and found this (simplified example from my code):
//class for loading config
public class Preferences {
public Preferences() {
InputStream image = Preferences.class.getResourceAsStream("images/image.png");
InputStream config = Preferences.class.getResourceAsStream("config.xml");
}
}
But image and config variables contains null. I was trying different variants of loading (from root folder, with this.getClass() instead of Preferences.class, and others), but it's always null. I really don't understand this resource loading system and I didn't find any good documentation about it. It would be nice, if somebody gives a good explanation about this mechanism (or just give a link on docs).
So, the main question is: How can I load my resources and config files?
You can use getResourceAsStream() method of java.lang.Class as you have done, but you have to add / before the path.
This question is tricky.
1. Two methods with same name
First of all, exist two methods of same name and same signature in these two classes:
java.lang.Class
java.lang.ClassLoader
They have the same name: getResource(String) (and getResourceAsStream(String) is alike).
2. They accept params of different format
Then, the param of them has different format:
The method java.lang.Class.getResouce<asStream>() accepts path with and without the leading /, resulting in different resources searching strategies. If a path has no /, Java will search the resource in the package/folder where the .class file resides. If it has /, Java will begin the searching from classpath root.
The method java.lang.ClassLoader.getResource<asStream>() accepts only path without /, because it always search from classpath. In a classpath based path, / is not a valid character. *
*: As this answer states: this.getClass().getClassLoader().getResource("...") and NullPointerException
How to add a folder to classpath? In Eclipse we resolve to the context menu of a project: "Build path" - "Configure build path..." and add some folder to build path.
3. When it comes to Maven
At last, if a project is a Maven project, by default src/main/resources is in the classpath, so we can use
Class.getResource("/path-to-your-res");
or,
ClassLoader.getResource("path-to-your-res");
, to load anything under src/main/resources.
If we want to add another resources folder, as you have mentioned, it is done in pom.xml. And they are added into classpath as well, done by Maven. No extra config is needed.
4. Example
For example, if your config.ini is under src/main/resources/settings, myAvatar.gif under src/main/images, you can do:
In pom.xml:
<build>
<resources>
<resource>
<directory>src/main/images</directory>
</resource>
</resources>
</build>
In code:
URL urlConfig = MyClass.class.getResource("/settings/config.ini"); //by default "src/main/resources/" is in classpath and no config needs to be changed.
InputStream inputAvatar = MyClass.class.getResourceAsStream("/myAvatar.gif"); //with changes in pom.xml now "src/main/images" is counted as resource folder, and added to classpath. So we use it directly.
We must use / above.
Or, with ClassLoader:
URL urlConfig = MyClass.class.getClassLoader().getResource("settings/config.ini"); //no leading "/"!!!
InputStream inputAvatar = MyClass.class.getClassLoader().getResourceAsStream("myAvatar.gif"); //no leading "/"!!!
I think I found the solution. As Juned Ahsan and mR_fr0g write, I need to use ClassLoader class, instead of this.getClass().getResource(). But, it works only for resource folder. But maven allows to add other folders as resource folders. I was just needed to add this section to pom.xml:
<build>
<resources>
<resource>
<directory>src/main/config</directory>
</resource>
</resources>
</build>
And working java code is:
InputStream image = this.getClass().getClassLoader().getResourceAsStream("images/image.png");
InputStream config = ClassLoader.getSystemResourceAsStream("config.xml");
public Preferences() {
InputStream image = this.getClass().getClassLoader().getResourceAsStream("image.png");
InputStream config = this.getClass().getClassLoader().getResourceAsStream("config.xml")
}
How about using this appraoch:
InputStream file = ClassLoader.getSystemResourceAsStream("res.txt");
or
InputStream file = Thread.currentThread().getContextClassLoader().getResourceAsStream("MyProperty.properties");
As you currently have it there, that will look for the MyProperty.properties file at the top of your classpath. The could be in your src/main/resources directory or other src folder -- it would depend on how your application (jar/war) is built.
If you are building a jar then you should be able to unpack it and see your properties file at the top level of the jar. If you are building a war, maybe it should be in the WEB-INF/classes directory. Again, it depends on how it was built.
Try to build the project before.
If you just put the files in the resources folder then you need to build the project in order to copy the new resource files into target folder
It's an old answered question, but I found that you need to use the include tag set or it won't find the resource when you call.
ClassLoader.getSystemResource("config.xml").
I'm using the latest maven (Oct 2020) on JDK14
Here's the working xml. Hope it helps as I tried it as stated in the solution here and it would not work until my xml looked as follows.
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<includes>
<include>**/*.xml</include>
<!-- or whatever other file extensions you want to include -->
</includes>
</resource>
</resources>
</build>