You could add junit as a test <dependency> to your parent pom... that is a dependency not dependencyManagement....
Might cause more problems than it fixes though! -Stephen 2008/12/10 CheapLisa <[EMAIL PROTECTED]> > > thanks, so there is absolutely no way to rid every single pom.xml with some > reference to junit for example? > > Lisa > > > > Wayne Fay wrote: > > > >> I do not want this plugin section in every pom.xml in > >> every sub-module > >> (some 5 deep) > >> How do I do this to make it go? > > > > Generally, you should configure plugins like this in the > > <pluginManagement> section in the top parent, and then when you > > declare the plugin in each child, it will inherit the configuration > > from the parent. > > > > So the parent has the "big configuration" section in pluginMgmt, and > > the children just have: > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-surefire-plugin</artifactId> > > </plugin> > > > > Of course, surefire is already declared in the super pom, so you > > shouldn't even need to include that in the children. Check "mvn > > help:effective-pom" in a child once you've added that configuration to > > the top parent -- it should show up. > > > > Wayne > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/How-to-run-JUnit-tests-in-sub-modules-without-surefire-reference--tp20924140p20929409.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] > >
