Sounds like there are two separate problems: Problem 1:
Stephen Connolly-2 wrote: > > however, when you create from an archetype in a directory which > conatins a pom, the created module gets added as a new child module, > so that the build will build the parent and the newly created child > I think this should do it, it would involve separating your it projects into with-pom and without-pom subdirectories. Not super-elegant but it works. for the generate goal <pomIncludes> <pomInclude>with-pom/*/pom.xml</pomInclude> <pomInclude>without-pom/*</pomInclude> </pomIncludes> for the verify goal <pomIncludes> <pomInclude>with-pom/*/pom.xml</pomInclude> <pomInclude>without-pom/pom.xml</pomInclude> </pomIncludes> So you would have src/it/projects/with-pom and src/it/projects/without-pom directories Problem 2: Max Spring wrote: > > We have a parent POM design where the multi-module POM in the parent > directory != parent POM. > This is a capability/configurability problem with the archetype plugin, not with the testing methods, right? -- View this message in context: http://old.nabble.com/unit-testing-archetypes-tp27544824p27571519.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]
