t;> which had some _serious_ fixes, etc. + upgrade to the new apache parent
> and
> >> other stuff which have been no maven-core part directly, but got fixed
> >> subsequently.
> >> >
> >> > LieGrue,
> >> > strub
> >> >
>
Only that the majority of users will get just get "unable to resolve artifact"
errors, and probably never know that they can update aether - which, whilst it
isn't a difficult thing to do is just a bit fiddly - instead they'll just get
frustrated that once again "maven black magic sucks".
If ro
, 8/20/11, Mark Derricutt wrote:
> From: Mark Derricutt
> Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
> To: "Maven Developers List"
> Date: Saturday, August 20, 2011, 10:46 AM
> Please - for the love of ANY Maven
> user - please do NOT roll a
Please - for the love of ANY Maven user - please do NOT roll a 3.0.4 with any
Aether thats NOT 1.12.
1.11 that ships with the current Maven 3.0.3 has fundamental issues with your
local repository has artifacts from both mirrors and non-mirrors. I'm finding
more and more users getting hit with
For what it's worth, working around Maven not having had a release since the
1.12 release of Aether has been an unwelcome hassle. (FYI, I reported one
of the issues Jason mentioned, MNG-5087.)
I don't have much perspective on the intricacies or history of the licensing
and governance issues that
t change
>> >> much.
>> >>> The following scenarios are possible:
>> >>>
>> >>> a.) The vote fails and maven stays at aether 1.11. In
>> >> this case we still should ship a 3.0.4 to fix a few bugs on
>> >> our side.
>>
ot fixed
> subsequently.
> >
> > LieGrue,
> > strub
> >
> > --- On Fri, 8/19/11, Jason van Zyl wrote:
> >
> >> From: Jason van Zyl
> >> Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
> >> To: "Maven Developers List&quo
aven-core part directly, but got fixed subsequently.
>
> LieGrue,
> strub
>
> --- On Fri, 8/19/11, Jason van Zyl wrote:
>
>> From: Jason van Zyl
>> Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
>> To: "Maven Developers List"
>>
gt;>
>> c.) The vote passes and aether GAV and package names are allowed to remain
>> com.sonatype.* In this case users might also manually update if they want.
>>
>> In any case we should ship maven-3.0.5 once there is a new aether version
>> shipped by the E
:
> From: Jason van Zyl
> Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
> To: "Maven Developers List"
> Date: Friday, August 19, 2011, 11:45 AM
> I think we should wait for the vote
> to finish as it appears the vote will pass and then a
> release
the Eclipse Foundation AND we did run sufficient tests with this
> version on our side.
>
> LieGrue,
> strub
>
>
> --- On Fri, 8/19/11, Jason van Zyl wrote:
>
>> From: Jason van Zyl
>> Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
>> To:
d ship maven-3.0.5 once there is a new aether version
shipped by the Eclipse Foundation AND we did run sufficient tests with this
version on our side.
>
> LieGrue,
> strub
>
>
> --- On Fri, 8/19/11, Jason van Zyl wrote:
>
>> From: Jason van Zyl
>> Subject: Re:
side.
LieGrue,
strub
--- On Fri, 8/19/11, Jason van Zyl wrote:
From: Jason van Zyl
Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether
To: "Maven Developers List"
Date: Friday, August 19, 2011, 11:09 AM
Mark,
I think you're jumping the gun a bit. The vote that Ar
ship maven-3.0.5 once there is a new aether version
shipped by the Eclipse Foundation AND we did run sufficient tests with this
version on our side.
LieGrue,
strub
--- On Fri, 8/19/11, Jason van Zyl wrote:
> From: Jason van Zyl
> Subject: Re: [DISCUSS] release maven-3.0.4 now with the
Mark,
I think you're jumping the gun a bit. The vote that Arnaud proposed is not
finished yet. Many PMC members have not voted yet and at the very least to
short-circuit the vote we need to reach a majority amongst the PMC. Once that
happens then I think we can start discussing a 3.0.4 release.
Den 19.08.2011 11:34, skrev Mark Struberg:
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package names now and start with
th
+1 from me too.
Kristian
Den 19.08.2011 11:34, skrev Mark Struberg:
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package n
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package names now and start with
the upgrade later?
+1 from me.
LieGrue,
strub
18 matches
Mail list logo
