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.
This is sometimes incorrectly (IMHO) told as "maven ranges with non-SNAPSHOT bounds should not contain SNAPSHOTs" in fact, ranges do contain SNAPSHOTs: it's mathematical 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? Regards, Hervé Le samedi 14 juin 2014 07:27:06 Christian Schulte a écrit : > Am 06/14/14 04:50, schrieb talios: > > Github user talios commented on the pull request: > > https://github.com/apache/maven/pull/21#issuecomment-46076519 > > > > Interesting about the version range changes in aether there - whilst > > the [2.2.*] range is nice, that doesn't offer SNAPSHOT exclusion - > > unless the `VersionFilter` is being exposed somehow to maven - I > > don't see maven directly supporting that. Tho this discussion should > > be taken off-issue I guess. > I did not follow any discussion about SNAPSHOT handling in version > ranges. From a version specification grammar point of view, '-SNAPSHOT' > is just another qualifier without special meaning. The special meaning > comes from Maven changing behaviour when detecting that qualifier. > Dealing with this could be as simple as changing version range behaviour > based on that qualifier as well. So when a POM defines that qualifier, > Maven includes versions carrying that qualifier, and if a POM does not > define that qualifier, Maven excludes that qualifier. Actually, it's a > flag indicating a project to be work in progress. If 'true', that > project is allowed to depend on other projects flagged work in progress, > if 'false', it's not. Just an idea, however. > > Regards, --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
