On 2/12/07, Guijie (Maggie) Ma <[EMAIL PROTECTED]> 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!
I believe Maven has designed Modules to be released as a group.
They are an all or nothing concept. You do not release modules individually.
So it is easier to set the version number up in the root pom and keep
the modules in sync with this value.
If you want to release your modules individually or have different
version ids then maybe you should consider creating separate projects.
At least this is the way I am using them, someone with more intimate
knowledge may be able to provide corrections.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
