> Without it Maven quite easily gets seriously broken :( Thats exactly the reason. Do you like to have the Apache Maven project depending on a part which you have no control over? Which might change in a way which just doesn't fit for Maven?
Remember: all this used to be just a part of maven-core in v2... LieGrue, strub --- On Wed, 7/27/11, Mark Derricutt <m...@talios.com> wrote: > From: Mark Derricutt <m...@talios.com> > Subject: Re: [VOTE] Incorporate EPL Ether in Maven Releases > To: "Maven Developers List" <dev@maven.apache.org> > Date: Wednesday, July 27, 2011, 8:32 PM > As long as 1.12+ of Aether makes it > into the 3.0.4 release: > > +1 NON Binding > > Without it Maven quite easily gets seriously broken :( > > On 28/07/2011, at 6:45 AM, Benson Margulies wrote: > > > As per the approved policy, this message opens a vote > to allow Maven > > releases to depend on EPL (and thus Category B) > versions of Aether. > > The vote will be open for 72 hours and the results > determined > > according to the policy. Discussion on this question > took place on a > > thread labelled '[DISCUSS] incorporate EPL Aether'. > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
