>>- On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run).
I think that's because you should use -DdryRun=true. Thanks Adam -----Original Message----- From: Dev at weitling [mailto:[email protected]] Sent: 13 March 2009 10:57 To: [email protected] Subject: Several questions regarding release-plugin/scm/multi-module Hi, sorry for starting my newbie-career with a lot of questions... All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6 x86. The layout is like this Variant A) testA/ testA/pom.xml testMain/ testMain/pom.xml Variant B) testMain/ testMain/pom.xml testMain/testA/ (via svn:externals) testMain/testA/pom.xml where testMain/pom.xml hast defined testA as submodule (../testA). Now the bunch of questions/oddities: - On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). - How can I exclude modules from being versioned/tagged? - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). - Is there a way to call release:prepare on each (sub-)module while updating the changed dependencies? The reasons for using externals 1) tagging a set of modules using testMain's pom just for convenience and 2) refactoring takes place immediately on affected modules. I hope I'm not too confusing. Any help is greatly appreciated. Florian --------------------------------------------------------------------- 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]
