maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Schneider <pschnei...@gmail.com>
Subject Re: MNG-3038
Date Fri, 27 Mar 2009 15:30:59 GMT
Okay, cool.  Like I said...  it's been awhile  :)

Anyway, I'll start working on this today and be in touch.

On Fri, Mar 27, 2009 at 10:15 AM, John Casey <jdcasey@commonjava.org> wrote:

> Looks like another victim of the version shift. The "2.1" referred to in
> that comment is what we're now referring to as "3.0.x"...aside from that,
> I'm not entirely sure why Joakim said it wasn't fixable until that release.
>
> -john
>
>
> Patrick Schneider wrote:
>
>> Hi All,
>>
>> It's been awhile since I've had the availability to do any Maven work, but
>> I'd like to get back into it.  I have a few open JIRA issues, and I figure
>> MNG-3038 is as good a place to start as any.
>>
>> I notice that the first comment states that the issue will likely not be
>> fixed for 2.0.x, and will be taken into consideration as a use case for
>> the
>> 2.1 artifact resolution spec.
>>
>> In light of the 2.1.0 release, is this issue valid anymore?  If so, which
>> development line should I resolve this in?
>>
>> Thanks,
>>
>>
>> Patrick
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message