Other people have asked for/suggested this previously, but it seems no one has actually done it yet, so if it is functionality you desire, I'd strongly suggest implementing it in a way that you like, and then contributing it back.
You might want to check JIRA to make sure a bug hasn't already been filed for this issue, so you can attach your code patch to the proper issue, or make a new one if none exists. Wayne On 5/1/07, David Roussel <[EMAIL PROTECTED]> wrote:
If you've got that far, then your on your way to making a change and trying it out Have a look at: - http://maven.apache.org/guides/development/guide-m2-development.html - http://maven.apache.org/plugin-developers/index.html - http://maven.apache.org/developers/index.html David C. Hicks wrote: > > Well, I did a little browsing through the maven-release-plugin code > base, and I see that what I'm looking for (below) isn't currently > possible. It doesn't look like it would be terribly difficult to insert > a check for a system property into DefaultVersionInfo#getNextVersion, > though, that could pull off this stunt. Since I'm not involved in the > plugin development, I guess the best I can do is offer it up as a thought. > > David C. Hicks wrote: >> Maybe it's a bad idea and please feel free to let me know if there is >> a good reason to change this strategy, but we don't use the typical >> Maven version numbering scheme. We work in an agile environment and >> use our iteration number as the minor version number. The major >> number is reserved for major releases, as usual. The revision is used >> when we release a "patch" release during an iteration to fix specific >> problems for our QE department prior to the usual iteration release. >> So, for example, my current project's release is 0.18.0 meaning that >> we've released iteration 18 to QE. We're currently working on >> 0.19.0-SNAPSHOT. >> >> I understand that I can use the --batchmode switch to keep the release >> plugin from asking me for new release numbers, a big problem because >> we have about six sub-projects that all must be re-versioned for both >> release and a new snapshot. It's not good to have to key in new >> versions six times each. :-) What would be nice, is if I could >> specify the new release/snapshot versions in some kind of system >> property, something like the -DdryRun property. Do you know if this >> is possible? >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/HOWTO%3A-%28Build---%29-Release-mgmt-in-multi-environment-tf3663526s177.html#a10269969 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
