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 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 > > 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 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 this work? > > > > > > > > BR//Rex > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >