Jesse already answered about your solution. But I'm worried about what you're trying to do. Can you explain a bit why you don't want to include those module inside the parent one? I have some difficulties to understand how one could have the need to put a project inside a multi-module hierarchy, but without wanting to include it in this build hierarchy. Wouldn't it make more sense to extract those to-be-built-separately projects from the multi-module project?
Cheers 2010/3/9 bendg <[email protected]> > > Hi > > I am running release:prepare to generate .tag and .next versions of poms. > > However, some of my modules are not in the overall build. > > Therefore, I need to cd into the directory to execute the release:prepare > for these modules which is not great... > > Is there any way of maintaining a separate pom hierarchy for modules that I > do not want in the main build? ie. dev-build.pom.xml ? > > > -- > View this message in context: > http://old.nabble.com/release-plugin-tp27832814p27832814.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] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
