I did this and only see a reference to maven-surefire-reports in the reporting section but not elsewhere.
My objective is to clean up my pom's and not repeat what is not really needed. It seams like having a reference to surefire in a build section in every module pom is tedious to include and maintain. thanks L Wayne Fay wrote: > >> thanks, so there is absolutely no way to rid every single pom.xml with >> some >> reference to junit for example? > > I guess I still don't know what your objective is. > > Surefire is in the super pom (in Maven's jars), so *all* poms will > have a reference to it, directly or inherited. If you make a new > project with a nearly empty pom and try "mvn help:effective-pom", > you'll see Surefire in it. > > As for JUnit, Surefire knows how to run JUnit tests, but it doesn't > explicitly depend on JUnit, so you'll need to include a reference to > it at least in the top parent's pom files and it should be inherited > by the children. So no, you don't need to include junit in "every > single pom.xml". > > I think you need to make some sample projects and play around with > help:effective-pom to see how it all works, then come back with > specific questions if you have any. > > 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--tp20924140p20943614.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]
