You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@tesla.io> on 2012/10/01 02:04:41 UTC
Aether 0.9.0.M1
I'm working on the Aether Ant Tasks and in order to make them work with the new Eclipse release of Aether I had to start refactoring the the core -- maven-aether-provider specifically -- in order to make them work. If no one objects to using a milestone from Eclipse then I will make the changes in the core to use the Eclipse Aether, otherwise I can keep my branch and rebase when an official release comes out and merge it then.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
Re: Aether 0.9.0.M1
Posted by Ralph Goers <ra...@dslextreme.com>.
On Oct 6, 2012, at 4:23 AM, Hervé BOUTEMY wrote:
> Aether 0.9.0.M1 is now in central [1]
> and Benjamin did the upgrade on his own Maven 3 branch [2]
>
> Question: do we need a formal vote for the upgrade of this dependency?
No.
> Any objection to do the upgrade without vote, given it's just a new home for a
> compoennt we already use?
No.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Olivier Lamy <ol...@apache.org>.
no objections from me.
2012/10/6 Stephen Connolly <st...@gmail.com>:
> The dependency we currently have is EPL and the "replacement" is EPL so I
> don't see the need to vote. Only if the license was changing or if we were
> moving from eclipse to a non-foundation hosted artifact would I see the
> need for a vote.
>
> In any case I think we can hold back the decision until the release vote
> unless people see the risk of rollback as too high
>
> Our original intent in voting to accept the EPL licensed aether from
> sonatype was that the eclipse one was taking too long, so I viewed the vote
> as being both to take the eclipse one AND pragmatically take the sonatype
> one until eclipse had a release.
>
> If others viewed it differently, they really should shout out now, or -1
> the commit
>
> On Saturday, 6 October 2012, Hervé BOUTEMY wrote:
>
>> Aether 0.9.0.M1 is now in central [1]
>> and Benjamin did the upgrade on his own Maven 3 branch [2]
>>
>> Question: do we need a formal vote for the upgrade of this dependency?
>> Any objection to do the upgrade without vote, given it's just a new home
>> for a
>> compoennt we already use?
>>
>> Regards,
>>
>> Hervé
>>
>> [1] http://central.maven.org/maven2/org/eclipse/aether/
>>
>> [2] https://github.com/bentmann/maven-3
>>
>> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
>> > I'm working on the Aether Ant Tasks and in order to make them work with
>> the
>> > new Eclipse release of Aether I had to start refactoring the the core --
>> > maven-aether-provider specifically -- in order to make them work. If no
>> one
>> > objects to using a milestone from Eclipse then I will make the changes in
>> > the core to use the Eclipse Aether, otherwise I can keep my branch and
>> > rebase when an official release comes out and merge it then.
>> >
>> > Thanks,
>> >
>> > Jason
>> >
>> > ----------------------------------------------------------
>> > Jason van Zyl
>> > Founder & CTO, Sonatype
>> > Founder, Apache Maven
>> > http://twitter.com/jvanzyl
>> > ---------------------------------------------------------
>> >
>> > A party which is not afraid of letting culture,
>> > business, and welfare go to ruin completely can
>> > be omnipotent for a while.
>> >
>> > -- Jakob Burckhardt
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
>> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>>
>>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Barrie Treloar <ba...@gmail.com>.
On Sat, Oct 6, 2012 at 11:04 PM, Stephen Connolly
<st...@gmail.com> wrote:
> Our original intent in voting to accept the EPL licensed aether from
> sonatype was that the eclipse one was taking too long, so I viewed the vote
> as being both to take the eclipse one AND pragmatically take the sonatype
> one until eclipse had a release.
>
> If others viewed it differently, they really should shout out now, or -1
> the commit
That was my understanding as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Stephen Connolly <st...@gmail.com>.
The dependency we currently have is EPL and the "replacement" is EPL so I
don't see the need to vote. Only if the license was changing or if we were
moving from eclipse to a non-foundation hosted artifact would I see the
need for a vote.
In any case I think we can hold back the decision until the release vote
unless people see the risk of rollback as too high
Our original intent in voting to accept the EPL licensed aether from
sonatype was that the eclipse one was taking too long, so I viewed the vote
as being both to take the eclipse one AND pragmatically take the sonatype
one until eclipse had a release.
If others viewed it differently, they really should shout out now, or -1
the commit
On Saturday, 6 October 2012, Hervé BOUTEMY wrote:
> Aether 0.9.0.M1 is now in central [1]
> and Benjamin did the upgrade on his own Maven 3 branch [2]
>
> Question: do we need a formal vote for the upgrade of this dependency?
> Any objection to do the upgrade without vote, given it's just a new home
> for a
> compoennt we already use?
>
> Regards,
>
> Hervé
>
> [1] http://central.maven.org/maven2/org/eclipse/aether/
>
> [2] https://github.com/bentmann/maven-3
>
> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
> > I'm working on the Aether Ant Tasks and in order to make them work with
> the
> > new Eclipse release of Aether I had to start refactoring the the core --
> > maven-aether-provider specifically -- in order to make them work. If no
> one
> > objects to using a milestone from Eclipse then I will make the changes in
> > the core to use the Eclipse Aether, otherwise I can keep my branch and
> > rebase when an official release comes out and merge it then.
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder & CTO, Sonatype
> > Founder, Apache Maven
> > http://twitter.com/jvanzyl
> > ---------------------------------------------------------
> >
> > A party which is not afraid of letting culture,
> > business, and welfare go to ruin completely can
> > be omnipotent for a while.
> >
> > -- Jakob Burckhardt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>
Re: Aether 0.9.0.M1
Posted by Hervé BOUTEMY <he...@free.fr>.
Aether 0.9.0.M1 is now in central [1]
and Benjamin did the upgrade on his own Maven 3 branch [2]
Question: do we need a formal vote for the upgrade of this dependency?
Any objection to do the upgrade without vote, given it's just a new home for a
compoennt we already use?
Regards,
Hervé
[1] http://central.maven.org/maven2/org/eclipse/aether/
[2] https://github.com/bentmann/maven-3
Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
> I'm working on the Aether Ant Tasks and in order to make them work with the
> new Eclipse release of Aether I had to start refactoring the the core --
> maven-aether-provider specifically -- in order to make them work. If no one
> objects to using a milestone from Eclipse then I will make the changes in
> the core to use the Eclipse Aether, otherwise I can keep my branch and
> rebase when an official release comes out and merge it then.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
> -- Jakob Burckhardt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Jason van Zyl <ja...@tesla.io>.
Doesn't bother me if you use Aether directly.
Even in a component that is ostensibly shared it is but one set of use cases. Everyone was arguing to shield the base artifact resolution service behind one facade, not the single set solution that is represented in the tree component. Extending the Maven Artifact API to complete and using that in the tree component versus using Aether directly. I think using Aether directly in the tree component is fine too.
On Oct 2, 2012, at 1:11 PM, Mark Struberg <st...@yahoo.de> wrote:
> I don't get it. Having shared/maven-dependency-tree hiding all that stuff will perfectly allow us to switch to another dependency resolution approach without having to change anything. Having maven plugins depend on aether directly is what creates tons of problems as those plugins would not work anymore under a newer maven version.
>
> LieGrue,
> strub
>
>
>
>
> ----- Original Message -----
>> From: Jason van Zyl <ja...@tesla.io>
>> To: Maven Developers List <de...@maven.apache.org>
>> Cc:
>> Sent: Tuesday, October 2, 2012 8:10 PM
>> Subject: Re: Aether 0.9.0.M1
>>
>>
>> On Oct 2, 2012, at 10:15 AM, Hervé BOUTEMY <he...@free.fr> wrote:
>>
>>> Le lundi 1 octobre 2012 19:34:27 Jason van Zyl a écrit :
>>>> On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY <he...@free.fr>
>> wrote:
>>>>> Given this milestone will be available in central repo [1], I
>> don't see
>>>>> any
>>>>> problem: I created MNG-5354 to track this.
>>>>
>>>> Cool, thanks.
>>>>
>>>>> Of course, as requested by our dependency policy [2], we need a
>> formal
>>>>> vote
>>>>> approved by PMC majority: this intent declaration is useful before
>> calling
>>>>> for a formal vote just to see if there is some specific problem.
>>>>>
>>>>> I'll do parallel work on maven-dependency-tree support for
>> Maven 3.1, to
>>>>> be
>>>>> able to release Maven 3.1-compatible plugins ASAP, since moving to
>>>>> org.eclipse.aether will cause some incompatibilities
>>>>
>>>> They shouldn't cause incompatibilities if they are using the Maven
>> Artifact
>>>> APIs. We have plugins directly bound to Aether?
>>> plugins requiring precise dependency calculation, with complete graph
>>> traversal, use maven-dependency-tree, and maven-dependency-tree 2.0 uses
>>> Aether when run under Maven 3
>>> http://maven.apache.org/shared/maven-dependency-tree/
>>
>> Sure, I just remember you all complaining that you didn't want to expose
>> yourselves to Aether and that you would have made changes to get the same in the
>> Maven Artifact APIs.
>>
>> Yes, it's easier to just rely on Aether then remake it all.
>>
>>>
>>>>> I have only one request: please complete previous
>> tests/documentation on
>>>>> JSR-330 and slf4j associated to MNG-5343 and MNG-5344
>>>>
>>>> Yup, no problem. Just busy here at JavaOne and trying update the m2e
>>>> connector catalog which is causing uses lots of grief.
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>>
>>>>> [1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
>>>>>
>>>>> [2] http://maven.apache.org/developers/dependency-policies.html
>>>>>
>>>>> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
>>>>>> I'm working on the Aether Ant Tasks and in order to make
>> them work with
>>>>>> the
>>>>>> new Eclipse release of Aether I had to start refactoring the
>> the core --
>>>>>> maven-aether-provider specifically -- in order to make them
>> work. If no
>>>>>> one
>>>>>> objects to using a milestone from Eclipse then I will make the
>> changes in
>>>>>> the core to use the Eclipse Aether, otherwise I can keep my
>> branch and
>>>>>> rebase when an official release comes out and merge it then.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder & CTO, Sonatype
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>> A party which is not afraid of letting culture,
>>>>>> business, and welfare go to ruin completely can
>>>>>> be omnipotent for a while.
>>>>>>
>>>>>> -- Jakob Burckhardt
>>>>>
>>>>>
>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder & CTO, Sonatype
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> A language that doesn’t affect the way you think about programming is
>> not
>>>> worth knowing.
>>>>
>>>> -- Alan Perlis
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> I never make the mistake of arguing with people for whose opinions I have no
>> respect.
>>
>> -- Edward Gibbon
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: Aether 0.9.0.M1
Posted by Mark Struberg <st...@yahoo.de>.
I don't get it. Having shared/maven-dependency-tree hiding all that stuff will perfectly allow us to switch to another dependency resolution approach without having to change anything. Having maven plugins depend on aether directly is what creates tons of problems as those plugins would not work anymore under a newer maven version.
LieGrue,
strub
----- Original Message -----
> From: Jason van Zyl <ja...@tesla.io>
> To: Maven Developers List <de...@maven.apache.org>
> Cc:
> Sent: Tuesday, October 2, 2012 8:10 PM
> Subject: Re: Aether 0.9.0.M1
>
>
> On Oct 2, 2012, at 10:15 AM, Hervé BOUTEMY <he...@free.fr> wrote:
>
>> Le lundi 1 octobre 2012 19:34:27 Jason van Zyl a écrit :
>>> On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY <he...@free.fr>
> wrote:
>>>> Given this milestone will be available in central repo [1], I
> don't see
>>>> any
>>>> problem: I created MNG-5354 to track this.
>>>
>>> Cool, thanks.
>>>
>>>> Of course, as requested by our dependency policy [2], we need a
> formal
>>>> vote
>>>> approved by PMC majority: this intent declaration is useful before
> calling
>>>> for a formal vote just to see if there is some specific problem.
>>>>
>>>> I'll do parallel work on maven-dependency-tree support for
> Maven 3.1, to
>>>> be
>>>> able to release Maven 3.1-compatible plugins ASAP, since moving to
>>>> org.eclipse.aether will cause some incompatibilities
>>>
>>> They shouldn't cause incompatibilities if they are using the Maven
> Artifact
>>> APIs. We have plugins directly bound to Aether?
>> plugins requiring precise dependency calculation, with complete graph
>> traversal, use maven-dependency-tree, and maven-dependency-tree 2.0 uses
>> Aether when run under Maven 3
>> http://maven.apache.org/shared/maven-dependency-tree/
>
> Sure, I just remember you all complaining that you didn't want to expose
> yourselves to Aether and that you would have made changes to get the same in the
> Maven Artifact APIs.
>
> Yes, it's easier to just rely on Aether then remake it all.
>
>>
>>>> I have only one request: please complete previous
> tests/documentation on
>>>> JSR-330 and slf4j associated to MNG-5343 and MNG-5344
>>>
>>> Yup, no problem. Just busy here at JavaOne and trying update the m2e
>>> connector catalog which is causing uses lots of grief.
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>>
>>>> [1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
>>>>
>>>> [2] http://maven.apache.org/developers/dependency-policies.html
>>>>
>>>> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
>>>>> I'm working on the Aether Ant Tasks and in order to make
> them work with
>>>>> the
>>>>> new Eclipse release of Aether I had to start refactoring the
> the core --
>>>>> maven-aether-provider specifically -- in order to make them
> work. If no
>>>>> one
>>>>> objects to using a milestone from Eclipse then I will make the
> changes in
>>>>> the core to use the Eclipse Aether, otherwise I can keep my
> branch and
>>>>> rebase when an official release comes out and merge it then.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder & CTO, Sonatype
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> A party which is not afraid of letting culture,
>>>>> business, and welfare go to ruin completely can
>>>>> be omnipotent for a while.
>>>>>
>>>>> -- Jakob Burckhardt
>>>>
>>>>
> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> A language that doesn’t affect the way you think about programming is
> not
>>> worth knowing.
>>>
>>> -- Alan Perlis
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> I never make the mistake of arguing with people for whose opinions I have no
> respect.
>
> -- Edward Gibbon
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Jason van Zyl <ja...@tesla.io>.
On Oct 2, 2012, at 10:15 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> Le lundi 1 octobre 2012 19:34:27 Jason van Zyl a écrit :
>> On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>>> Given this milestone will be available in central repo [1], I don't see
>>> any
>>> problem: I created MNG-5354 to track this.
>>
>> Cool, thanks.
>>
>>> Of course, as requested by our dependency policy [2], we need a formal
>>> vote
>>> approved by PMC majority: this intent declaration is useful before calling
>>> for a formal vote just to see if there is some specific problem.
>>>
>>> I'll do parallel work on maven-dependency-tree support for Maven 3.1, to
>>> be
>>> able to release Maven 3.1-compatible plugins ASAP, since moving to
>>> org.eclipse.aether will cause some incompatibilities
>>
>> They shouldn't cause incompatibilities if they are using the Maven Artifact
>> APIs. We have plugins directly bound to Aether?
> plugins requiring precise dependency calculation, with complete graph
> traversal, use maven-dependency-tree, and maven-dependency-tree 2.0 uses
> Aether when run under Maven 3
> http://maven.apache.org/shared/maven-dependency-tree/
Sure, I just remember you all complaining that you didn't want to expose yourselves to Aether and that you would have made changes to get the same in the Maven Artifact APIs.
Yes, it's easier to just rely on Aether then remake it all.
>
>>> I have only one request: please complete previous tests/documentation on
>>> JSR-330 and slf4j associated to MNG-5343 and MNG-5344
>>
>> Yup, no problem. Just busy here at JavaOne and trying update the m2e
>> connector catalog which is causing uses lots of grief.
>>> Regards,
>>>
>>> Hervé
>>>
>>>
>>> [1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
>>>
>>> [2] http://maven.apache.org/developers/dependency-policies.html
>>>
>>> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
>>>> I'm working on the Aether Ant Tasks and in order to make them work with
>>>> the
>>>> new Eclipse release of Aether I had to start refactoring the the core --
>>>> maven-aether-provider specifically -- in order to make them work. If no
>>>> one
>>>> objects to using a milestone from Eclipse then I will make the changes in
>>>> the core to use the Eclipse Aether, otherwise I can keep my branch and
>>>> rebase when an official release comes out and merge it then.
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder & CTO, Sonatype
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> A party which is not afraid of letting culture,
>>>> business, and welfare go to ruin completely can
>>>> be omnipotent for a while.
>>>>
>>>> -- Jakob Burckhardt
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> A language that doesn’t affect the way you think about programming is not
>> worth knowing.
>>
>> -- Alan Perlis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
I never make the mistake of arguing with people for whose opinions I have no respect.
-- Edward Gibbon
Re: Aether 0.9.0.M1
Posted by Hervé BOUTEMY <he...@free.fr>.
Le lundi 1 octobre 2012 19:34:27 Jason van Zyl a écrit :
> On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> > Given this milestone will be available in central repo [1], I don't see
> > any
> > problem: I created MNG-5354 to track this.
>
> Cool, thanks.
>
> > Of course, as requested by our dependency policy [2], we need a formal
> > vote
> > approved by PMC majority: this intent declaration is useful before calling
> > for a formal vote just to see if there is some specific problem.
> >
> > I'll do parallel work on maven-dependency-tree support for Maven 3.1, to
> > be
> > able to release Maven 3.1-compatible plugins ASAP, since moving to
> > org.eclipse.aether will cause some incompatibilities
>
> They shouldn't cause incompatibilities if they are using the Maven Artifact
> APIs. We have plugins directly bound to Aether?
plugins requiring precise dependency calculation, with complete graph
traversal, use maven-dependency-tree, and maven-dependency-tree 2.0 uses
Aether when run under Maven 3
http://maven.apache.org/shared/maven-dependency-tree/
> > I have only one request: please complete previous tests/documentation on
> > JSR-330 and slf4j associated to MNG-5343 and MNG-5344
>
> Yup, no problem. Just busy here at JavaOne and trying update the m2e
> connector catalog which is causing uses lots of grief.
> > Regards,
> >
> > Hervé
> >
> >
> > [1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
> >
> > [2] http://maven.apache.org/developers/dependency-policies.html
> >
> > Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
> >> I'm working on the Aether Ant Tasks and in order to make them work with
> >> the
> >> new Eclipse release of Aether I had to start refactoring the the core --
> >> maven-aether-provider specifically -- in order to make them work. If no
> >> one
> >> objects to using a milestone from Eclipse then I will make the changes in
> >> the core to use the Eclipse Aether, otherwise I can keep my branch and
> >> rebase when an official release comes out and merge it then.
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder & CTO, Sonatype
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> A party which is not afraid of letting culture,
> >> business, and welfare go to ruin completely can
> >> be omnipotent for a while.
> >>
> >> -- Jakob Burckhardt
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A language that doesn’t affect the way you think about programming is not
> worth knowing.
>
> -- Alan Perlis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Aether 0.9.0.M1
Posted by Jason van Zyl <ja...@tesla.io>.
On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> Given this milestone will be available in central repo [1], I don't see any
> problem: I created MNG-5354 to track this.
Cool, thanks.
> Of course, as requested by our dependency policy [2], we need a formal vote
> approved by PMC majority: this intent declaration is useful before calling for
> a formal vote just to see if there is some specific problem.
>
> I'll do parallel work on maven-dependency-tree support for Maven 3.1, to be
> able to release Maven 3.1-compatible plugins ASAP, since moving to
> org.eclipse.aether will cause some incompatibilities
>
They shouldn't cause incompatibilities if they are using the Maven Artifact APIs. We have plugins directly bound to Aether?
> I have only one request: please complete previous tests/documentation on
> JSR-330 and slf4j associated to MNG-5343 and MNG-5344
Yup, no problem. Just busy here at JavaOne and trying update the m2e connector catalog which is causing uses lots of grief.
>
> Regards,
>
> Hervé
>
>
> [1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
>
> [2] http://maven.apache.org/developers/dependency-policies.html
>
> Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
>> I'm working on the Aether Ant Tasks and in order to make them work with the
>> new Eclipse release of Aether I had to start refactoring the the core --
>> maven-aether-provider specifically -- in order to make them work. If no one
>> objects to using a milestone from Eclipse then I will make the changes in
>> the core to use the Eclipse Aether, otherwise I can keep my branch and
>> rebase when an official release comes out and merge it then.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> A party which is not afraid of letting culture,
>> business, and welfare go to ruin completely can
>> be omnipotent for a while.
>>
>> -- Jakob Burckhardt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A language that doesn’t affect the way you think about programming is not worth knowing.
-- Alan Perlis
Re: Aether 0.9.0.M1
Posted by Hervé BOUTEMY <he...@free.fr>.
Given this milestone will be available in central repo [1], I don't see any
problem: I created MNG-5354 to track this.
Of course, as requested by our dependency policy [2], we need a formal vote
approved by PMC majority: this intent declaration is useful before calling for
a formal vote just to see if there is some specific problem.
I'll do parallel work on maven-dependency-tree support for Maven 3.1, to be
able to release Maven 3.1-compatible plugins ASAP, since moving to
org.eclipse.aether will cause some incompatibilities
I have only one request: please complete previous tests/documentation on
JSR-330 and slf4j associated to MNG-5343 and MNG-5344
Regards,
Hervé
[1] http://dev.eclipse.org/mhonarc/lists/aether-dev/
[2] http://maven.apache.org/developers/dependency-policies.html
Le dimanche 30 septembre 2012 17:04:41 Jason van Zyl a écrit :
> I'm working on the Aether Ant Tasks and in order to make them work with the
> new Eclipse release of Aether I had to start refactoring the the core --
> maven-aether-provider specifically -- in order to make them work. If no one
> objects to using a milestone from Eclipse then I will make the changes in
> the core to use the Eclipse Aether, otherwise I can keep my branch and
> rebase when an official release comes out and merge it then.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
> -- Jakob Burckhardt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org