java.class.path under maven2 won't give you the path for the project
dependencies ... it's different from under maven1
On 1/30/08, Rex Huang [EMAIL PROTECTED] wrote:
the application use System.getProperty(java.class.path) to get
classpath.
Rex
On Jan 30, 2008 10:46 AM, Rex Huang [EMAIL
the application use System.getProperty(java.class.path) to get classpath.
Rex
On Jan 30, 2008 10:46 AM, Rex Huang [EMAIL PROTECTED] wrote:
exec-maven-plugin is good, but in my case, the application also run javac
to generate jar file, and it use its classpath instead of dependency
exec-maven-plugin is good, but in my case, the application also run javac to
generate jar file, and it use its classpath instead of dependency
information.
I use java to run it with classpath is ok.
BR//Rex
On Jan 29, 2008 7:53 PM, Wayne Fay [EMAIL PROTECTED] wrote:
The exec-maven-plugin
your plugin is interesting, but how to add argument to run application?
BR//Rex
On Jan 29, 2008 11:16 PM, Nick Stolwijk [EMAIL PROTECTED] wrote:
I worked with the Application Assembler Plugin [1] which generates a
directory under target, with a startup script, a lib directory with all
the
I just give mainclass and parameters information,
then maven runs the mainclass and use dependence artifact information as
classpath.
Can this work?
BR//Rex
The exec-maven-plugin should interest you:
http://mojo.codehaus.org/exec-maven-plugin/usage.html
Wayne
On 1/29/08, Rex Huang [EMAIL PROTECTED] wrote:
I just give mainclass and parameters information,
then maven runs the mainclass and use dependence artifact information as
classpath.
Can
I worked with the Application Assembler Plugin [1] which generates a
directory under target, with a startup script, a lib directory with all
the dependencies and some other files.
Maybe that is what you're looking for.
Hth,
Nick Stolwijk
[1]
