This idea would require a POM change, but similar to repository definitions having the option of declaring "release" or "snapshot"'s being enabled, maybe something similar could be provided for dependencies.
Or, with modifying the POM itself, we could extend the capability of the <classifier> attribute to somehow express "NO CLASSIFIER" which would exclude -SNAPSHOT, -alpha etc. etc. Maybe <classifier/> or <classifier></classifier> could handle that, which is different to it being absent. This does beg the question of weather -SNAPSHOT is or is not a classifier or not - having -SNAPSHOT just be a "magically" part of the version and not a classifier has always been a bug bear, esp. with timestamp'd SNAPSHOTs breaking the 1-1 mapping of direction/filenames On 29/09/2012, at 3:06 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > I'm not comfortable with the idea of excluding SNAPSHOT from ranges: if we do > so, it's not a *range* any more but a range + a filter > (1.7.1-SNAPSHOT is in [1.7,1.8] range,"in plain english")
