Hervé BOUTEMY wrote:
But anyway, how
does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of
2.0.0) to include anything from the 2.0.0. branch?
if you don"t want to include anything from the 2.0.0 branch, you have to write
you range as [1.0.0,2.0.0-SNAPSHOT), which is con
Le dimanche 16 novembre 2008, Dave Syer a écrit :
> Hervé BOUTEMY wrote:
> > [1] http://docs.codehaus.org/display/MAVEN/Versioning
>
> I didn't see any reference there to special qualifiers.
See "Proposal" section,
"strings are checked for well-known qualifiers and the qualifier ordering is
used
On Mon, 17 Nov 2008 00:43:03 Dave Syer wrote:
>
> Michael McCallum-3 wrote:
> >
> > just start at 2.1 and everything just works and makes sense...
> >
>
> Sorry, not to me, and not to anyone I know who uses version ranges. The
works or make sense ;-)
> OSGi version conventions always used to
just adopt the same rules - at least they are
sane, and proven in production use?
If 2.0.0 is the upper exclusive bound, I definitely do not want 2.0.0-* to
be included. It's completely counter intuitive.
--
View this message in context:
http://www.nabble.com/Version-range-special-cases--tp204
On Sun, 16 Nov 2008 21:51:18 Dave Syer wrote:
>
> Hervé BOUTEMY wrote:
> >
> > [1] http://docs.codehaus.org/display/MAVEN/Versioning
> >
>
> I didn't see any reference there to special qualifiers. But anyway, how
> does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of
> 2.0.
s just confising for users.
Those jars that are being used as OSGi usually have non-Maven version ids
already (i.e. in Maven language, not using the same qualifiers) because
people don't realise that there are any special rules.
--
View this message in context:
http://www.nabble.com/Version-r
yes, there are special cases hardwired, that were not meant to be weird but
useful features added to Maven Artifact 3.0 :)
see the proposal [1], the current implementation [2] and test-case [3]
the rationale is that snapshot < alpha < beta < milestone < release candidate
< release < service pack
ase hard wired to recognise "M"
and "RC" as special prefixes (and do the wrong thing with them - as far as I
can see).
This is with 3.0-alpha-2-SNAPSHOT version of maven-artifact.
--
View this message in context:
http://www.nabble.com/Version-range-special-cases--tp20480510
