esolution strategies start appearing, life will
be
infinitely more complicated. If you use a different strategy
and I
consume your artifacts, I need to be able to interpret your
strategy
and
use it when calculating your part of the tree. (and someone
else's
etc).
That means the strategies need t
.
so that 20030607 should be less than 1.0!!!
2009/2/10 Brian E. Fox :
Once multiple resolution strategies start appearing, life will be
infinitely more complicated. If you use a different strategy
and I
consume your artifacts, I need to be able to interpret your
strategy
and
use
f maven, and we cannot use them because version ranges only
work for three digit version numbers...
So now you have decided that OSGi is great, let's make OSGi work...
well that's great, just when you're making OSGi work, don't add stuff
in that breaks the rest of us
I
consume your artifacts, I need to be able to interpret your
strategy and
use it when calculating your part of the tree. (and someone
else's etc).
That means the strategies need to be implemented and available in
the
repository for mercury to use.
-Original Message-
From: St
ocess without
knocking build tooling off it's feet.
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, February 10, 2009 3:32 AM
To: Maven Developers List
Subject: Version comparison rules
OK, here's a hairy old chestnut...
Maven has a
when calculating your part of the tree. (and someone else's etc).
>>> That means the strategies need to be implemented and available in the
>>> repository for mercury to use.
>>>
>>> -Original Message-
>>> From: Stephen Connolly [mailto:stephen
Christian Schulte schrieb:
> Stephen Connolly schrieb:
>> What I'm thinking is that if we had some metadata associated with the
>> groupId, it could specify what the version comparison rule is for that
>> groupId (and all it's child groupIds)...
>
> It would be very cool to have some general purpo
Stephen Connolly schrieb:
> What I'm thinking is that if we had some metadata associated with the
> groupId, it could specify what the version comparison rule is for that
> groupId (and all it's child groupIds)...
It would be very cool to have some general purpose grouplevel metadata!
Various thin
nd available in the
repository for mercury to use.
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, February 10, 2009 3:32 AM
To: Maven Developers List
Subject: Version comparison rules
OK, here's a hairy old chestnut...
Maven has a
nolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Tuesday, February 10, 2009 3:32 AM
> To: Maven Developers List
> Subject: Version comparison rules
>
> OK, here's a hairy old chestnut...
>
> Maven has a set of version comparison rules... they don't work for
>
s the strategies need to be implemented and available in the
repository for mercury to use.
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, February 10, 2009 3:32 AM
To: Maven Developers List
Subject: Version comparison rules
OK, here's a
OK, here's a hairy old chestnut...
Maven has a set of version comparison rules... they don't work for
everyone... well life sucks
Mercury has a new set of version comparison rules... they're a lot
better, but probably don't work for everyone... life still sucks...
I&#
12 matches
Mail list logo
