You should use version ranges[0] and/or the release plugin[1].
Stefan
[0]
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
[1] http://maven.apache.org/plugins/maven-release-plugin/
Victor Tsoukanov wrote:
I would like to use versioning based on JSR-277. They use the following format:
major[.minor[.micro[.update]]][-qualifier]. Some extraxt from spec
1. Major version number should be incremented for making changes that are not
backward compatible.
2. Minor version number should be incremented for making medium or minor
changes that the software remains largely backward compatible, although minor
incompatibilities might be possible.
For example I have 3 modules: m1, m2 and m3 (m2 and m3 depends on m1). But m2 depends on m1 with version 1.0.0.0 and m3 depends on 1.1.0.0. As you see the changes in m1 are "largely backward compatible" - it means I can compile m2 and m3 with m1(1.1.0.0). When I try to compile it in maven m3 was compiled with m1(1.1.0.0) and m2 was compiled with m1(1.0.0.0) since they declared such dependencies, but I would like that maven compile both modules with last version of m1(1.1.0.0).
As I know for this cases maven suggests to use snapshot, but I would like to have version history in my repository.
Could somebody help me how could I implement such behavior in maven.
Thanks
---------------------------------------------------------------------
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]
