Brett Porter wrote, On 10/31/2005 12:52 PM:
Not exactly. The soft version is the version that will be used if it
fits in the valid ranges, and ignored if not. The conflict resolver in
play decides whether to use the nearest or newest of these versions -
in 2.0 only "nearest" was enabled.
If you
This is starting to sound pretty interesting. Could you flesh out this
example for those who are not maven gurus?
Regards,
Alan
Brett Porter wrote, On 10/31/2005 12:20 PM:
Yes, version ranges work, but simply omitting the version won't do it.
You could have [2.4,2.5) to pick up 2.4, 2.4-1,
Not exactly. The soft version is the version that will be used if it
fits in the valid ranges, and ignored if not. The conflict resolver in
play decides whether to use the nearest or newest of these versions -
in 2.0 only "nearest" was enabled.
If you want to allow a range, you have to give it an
From what I read on the maven wiki, you support soft versions, so
using the style you described below would 2.4
resolve to the newest 2.4* version you have in your local repo. Is
that accurate?
-dain
On Oct 31, 2005, at 12:20 PM, Brett Porter wrote:
Yes, version ranges work, but simply
Yes, version ranges work, but simply omitting the version won't do it.
You could have [2.4,2.5) to pick up 2.4, 2.4-1, 2.4-2, etc. though.
Cheers,
Brett
On 11/1/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> Oh, I thought one of the big features of m2 was support for version
> ranges.
>
> BTW I
Oh, I thought one of the big features of m2 was support for version
ranges.
BTW I find the name servlet-2.4-1.0 confusing myself.
-dain
On Oct 31, 2005, at 12:10 PM, Brett Porter wrote:
Actually, I meant a version of 2.4-1, 2.4-2.
I think there is advantages and disadvantages to each, so I
Just re-reading that I realised it could be a bit confusing as 2.4-1
and 2.4-1.0 look very similar.
The difference is that the first would be:
servlet
2.4-1
as opposed to
servlet-2.4
1.0
I think this is an interesting thing to discuss and perhaps feed back
into the Maven default versioning rules
Actually, I meant a version of 2.4-1, 2.4-2.
I think there is advantages and disadvantages to each, so I'll let you
all decide what's best to work with. I just wanted to point out that
omitting the version won't work so it'll need to be specified, and
personally I'd find that a bit confusing prese
Just to clarify you mean we should have this:
org.apache.geronimo.specs
servlet-2.4
Geronimo :: Servlet API
1
So the version number is a single non-dotted increasing integer?
BTW for most APIs we will be able to simply release a certified
version and never update, but for some APIs, l
I think this versioning has potential to be confusing, and the
omission of below doesn't actually do that - though it is
probably possible with a version of (,) that includes everything.
Personally, I'd prefer to have:
servlet-api-2.4
servlet-api-2.4-1
servlet-api-2.4-2
or similar.
(Technically,
I know this has been talked about before on this list, but I'd like
to get the proposal in one place. With the help of Alan and Jason,
this is what I got:
Normally we just have this directory structure:
specs/trunk/servlet-2.2/src/
specs/trunk/servlet-2.4/src/
specs/trunk/jsp-2.4/src/
When
11 matches
Mail list logo
