maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Casey <>
Subject Re: MNG-3038
Date Fri, 27 Mar 2009 15:15:40 GMT
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 


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:
For additional commands, e-mail:

View raw message