That's impossible. How can the test plugin know what test classes and other jars I need for my code? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
Laird Nelson <[EMAIL PROTECTED]> wrote on 06/09/2003 04:45:58 AM: > Andy Jefferson wrote: > > >You could take it further and think of the whole issue of > dependencies and the > >fact that there are basically 3 'types' ... build, test, and runtime. > > > > > Or: each plugin has dependencies, and the java:compile one fills its > dependency list from the POM, the test:* one fills its dependency list > from some other location in the POM, etc. > > Saying that each plugin can have a dependency but that that dependency > list can come from anywhere (like the POM, i.e. it doesn't need to be > hardcoded) allows for more flexibility in the future. > > L > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
