Java -jar : access external configuration file

Question

I\'m looking to do something which I thought was not going to be difficult.

I have an application that I\'d like to package up as a jar because I\'ve got ~30 depend

Answer 1

I will preserve for posterity my solution to this problem.

I think it's possible that I was expecting java -jar to do something it doesn't do.

If you use the regular java command you can include the jar on the classpath and you'll end up with pretty much the same thing as java -jar, only you have to specifically name the class you want to use. It looks like this:

java -cp .:path/to/Jar.jar com.company.package.Class arg1=val1 arg2=val2 ....

Chances are you're going to build a script to start the program for you anyway, so the added complexity of the command line call doesn't really amount to much, since you'll only build it once anyway.

You'll see I included '.' as the first item on the classpath, which means anything in the same directory as the jar will be included on the classpath as well. Of course everything inside the jar is included on the classpath also, since the jar itself is on the classpath too.

You'll also see that I've shown how you can still hand in args on the command line. This was something I was unsure about when I started but it works as expected.

I'm sure this is just basic java deployment knowledge, but I was lacking it for some reason.

I hope this helps someone else. It certainly would have saved me a lot of time if someone had been able to say "don't bother trying to get the -jar thing working - just use the -cp method"...

Answer 2

You need to add "." to the classpath of the jar file you are building for your application.

So in the manifest, I'd expect to see

Main-Class: some.full.Name
Class-Path: . needed-lib.jar other-lib.jar 

Then, when you run your app by executing

java -jar myapp.jar

it actually uses

java -classpath .;needed-lib.jar;other-lib.jar some.full.Name

This way any file in the directory with the myapp.jar file will also be on the classpath. That classpath is relative to the location of jar containing it.

Log4j for one expects the log4j.xml configuration file to be on the classpath. If you aren't using the name log4j.xml you also have to add a system property to your start up command to tell the log4j library to look for a different name.

I'm not sure what Spring expects for configuration files. And property file loading depends on what mechanism is used to load the file. Using a FileReader or InputStream doesn't use the classpath mechanism at all. In that case you need to know where the application is expecting the file to be relative to the current working directory.