unfortunately, you can't. If in continuum, the user is prompted for all
the versions.
What the plugin does however is suggest a default, which is what it
currently does. Of course, the default isn't always appropriate for all
cases, but generally it should suffice.
If you want a new algorithm or calculation in mind to use as default,
you can suggest it in jira and we can probably think about implementing
it or supporting it in one of the future versions.
Guijie (Maggie) Ma wrote:
But if there are more than one module and there are dependency between, the
change of one module can lead the version changes of other modules. The change
rule of version number should be different, not all be updated from
0.5.0-SNAPSHOT to 0.5.1-SNAPSHOT, maybe from 0.5.0-SNAPSHOT to 0.6.0-SNAPSHOT.
Could I change the rule of the version identification ? Thank you!
Maggie
"Barrie Treloar" <[EMAIL PROTECTED]> 2/11/2007 11:01 PM >>>
On 2/12/07, Guijie (Maggie) Ma <[EMAIL PROTECTED]> wrote:
Do you think it is more convenient if the release plugin can deal with the
revision number automatically?
I have attached the snapshot of the release-prepare.
The attached snapshot was cut by the list.
I am successfully using the release plugin and it will correctly
transform my current version of "0.5-SNAPSHOT" into the release
version "0.5" and the next development version of "0.6-SNAPSHOT".
If I have "0.5.0-SNAPSHOT" then it will transform this into
"0.5.1-SNAPSHOT" instead.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
