Am 06/14/14 08:39, schrieb Hervé BOUTEMY: > this is one of the problems when using version ranges, tied to > reproducibility > and definition of the algorithm for Maven to choose one version in the range > adapted to the actual context.
It's not only about version ranges. It seems inconsistent to allow the following to build at all. No ranges involved. <version>1.0</version> <dependency> <version>2.2-SNAPSHOT</version> </dependency> This should make Maven error out immediately stating that a non-snapshot POM cannot depend on a snapshot POM. Maven could do this for ranges automatically. <version>1.0-SNAPSHOT</version> <dependency> <version>[1.*]</version> </dependency> The range [1.*] may resolve to a SNAPSHOT version. Changing the version of that POM to <version>1.0</version> the range [1.*] may not resolve to a snapshot version. > but the question is: how to avoid non-SNAPSHOT resolution/choice when doing a > release, while resolving SNAPSHOTs when not doing a release? > How to affect the algorithm that magically choose on version in the range? Why not the same way 'release:prepare' enforces above logic ? Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
