Hello! we have about 20 multiprojects composed of several java projects. Typically, a subsystem would be a J2EE application or a common component developed by one team. The build of the whole system is cascaded, approximately 5 levels. So we have dependencies between the multiproject.
Does anybody have experience with defining a release process and versioning with m2 for such a usecase? Every multiproject is released and tested in 3 week iterations. E.g. for Release 2.3.x we would have 2.3-alpha-1, 2.3-alpha-2, 2.3-beta-1, 2.3-beta-2, 2.3-rc-1, 2.3 In practice, for each iteration several builds might be required, let's say artifact A has 2.3-beta-1.1, 2.3-beta-1.2. Typically, the development version would be 2.3-SNAPSHOT. Now, artifact B from an other subsystem depends on A 2.3-SNAPSHOT. On the release:prepare run, the plugin resolves the this snapshot with 2.3. But this isn't an existing version . How can I improve this release process with maven release plugin? Defining a snapshot version like 2.3-beta-1.x-SNAPSHOT doesn't work, since I can't predict the next version. It might be 2.3-beta-1.x+1 or 2.3-beta-2. Furthermore, it seams that this versioning scheme isn't supported by maven. An other way would be to renounce the qualifier and use build numbers instead, like 2.3-5532 , 2.3-5533 Though, I'd lose the information about the release quality. Any thoughts or ideas? Thanks a lot. Kuno -- View this message in context: http://www.nabble.com/Release-plugin-and-versioning-with-Maven2-tp18402101p18402101.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]
