Alex,
I too went through this problem and hopefully I can be of some assistance to
you. It seems you are close to a solution, but I would like to offer a
different approach from the executable jar.
Within your assembly descriptor, you can output your dependent jars into a
desired folder
<dependencySets>
<dependencySet>
<scope>compile</scope>
<outputDirectory>lib</outputDirectory>
</dependencySet>
</dependencySets>
this puts the needed jars into a lib directory in the root of your zip
structure, provided your project modules dependencies are configured
properly.
In order to get java to use your jars, you must tell it to look for the
specific lib directory: -Djava.ext.dirs="/path/to/lib"
In order to get java to pick up properties files, they need to be located in
the java/lib/ext directory, then append that location to the above perhaps
like this.
-Djava.ext.dirs="/path/to/lib";"$MY_JAVA_HOME/lib/ext"
Instead of creating an executable jar, you can call your main class with the
java command from within the script.
java -Djava.ext.dirs="/path/to/lib";"$MY_JAVA_HOME/lib/ext"
foo.bar.MyMainClass
Hopefully this will help!
~Tommy
alexworden wrote:
>
> My problem is that I need to specify an additional path to my classpath
> that contains some properties files for the target platform. If I use the
> -classpath, I can no-longer invoke my executable jar. I've tried just
> setting CLASSPATH but this has no effect.
>
--
View this message in context:
http://www.nabble.com/Packaging-an-application-that-can-be-run-tp20016263p20016815.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
