Here's something I'm sure someone has encountered before ... We use M2 and Subversion to build web-apps.
We make a QA/ branch from dev/ when a release cycle begins and run the maven 'release' goal to build the first release candidate [RC]. Version numbering looks like '1.2.3-RC-n'. Only changes necessary to fix release-blocking issues are allowed in the QA/ branch. Some of these changes occur in locally built jars. POM <dependency> tags are used used for these artifacts, but according to M2 none of the dependency artifacts can be SNAPSHOT versions. A series of successive RCs are built on the QA/ branch until one is approved. At that point the project is rebuilt on the QA/ branch without '-RC-n' in the version string and it becomes the final distribution. In the meantime, development has continued on the dev/ branch, with commits occurring in the main project as well as in sub-projects for any of the local jars. Dependencies refer to SNAPSHOT versions. We're getting tangled trying to reconcile versions of these local artifacts. Version 2.3.4 of a local jar doesn't necessarily represent the same content in the QA/ and dev/ branches. How should we be working this. Are mutiple 'release' repositories part of the answer? Thanks. Brad -- View this message in context: http://www.nabble.com/Release-Strategy-tf3607319s177.html#a10078348 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
