You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2011/07/16 19:29:59 UTC
Coordinating with Aether
Folks,
I've submitted one tiny fix to Aether, and I have a feature proposal
I'm discussing with the proprietor: making the *-pattern in mirrors a
bit richer.
Eventually, this would be 'as simple' as a change to the aether
provider to take a newer aether. However, I wonder if the PMC has
established any organized process of coordinating.
--benson
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Coordinating with Aether
Posted by Hervé BOUTEMY <he...@free.fr>.
yes, that would be a good option and seems reasonable from my perspective
Le dimanche 17 juillet 2011, Benson Margulies a écrit :
> Well, I'm not a PMC member, so I'll just follow instructions. Someone
> might wonder if, given the progressive calm that has settled over the
> trademark business, perhaps Sonatype might go back to dual-licensing
> if asked?
>
> On Sat, Jul 16, 2011 at 5:36 PM, Hervé BOUTEMY <he...@free.fr>
wrote:
> > Good question :)
> >
> > Current Maven versions (3.0.3 and 3.0.4-SNAPSHOT) use Aether 1.11, which
> > has a dual EPL/ASLv2 license [1].
> > As far new versions of Aether stay under ASLv2 license, there is no
> > question for Maven when upgrading dependency.
> >
> > Now, Aether 1.12 was released under EPL license only, and actual
> > 1.13-SNAPSHOT sources are EPL only too. Upgrading Maven dependency will
> > imply a license change, that must be voted upon.
> >
> > Regards,
> >
> > Hervé
> >
> >
> > [1]
> > http://maven.apache.org/ref/3.0.4-SNAPSHOT/apache-maven/dependencies.htm
> > l
> >
> > Le samedi 16 juillet 2011, Benson Margulies a écrit :
> >> Folks,
> >>
> >> I've submitted one tiny fix to Aether, and I have a feature proposal
> >> I'm discussing with the proprietor: making the *-pattern in mirrors a
> >> bit richer.
> >>
> >> Eventually, this would be 'as simple' as a change to the aether
> >> provider to take a newer aether. However, I wonder if the PMC has
> >> established any organized process of coordinating.
> >>
> >> --benson
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Coordinating with Aether
Posted by Benson Margulies <bi...@gmail.com>.
Well, I'm not a PMC member, so I'll just follow instructions. Someone
might wonder if, given the progressive calm that has settled over the
trademark business, perhaps Sonatype might go back to dual-licensing
if asked?
On Sat, Jul 16, 2011 at 5:36 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> Good question :)
>
> Current Maven versions (3.0.3 and 3.0.4-SNAPSHOT) use Aether 1.11, which has a
> dual EPL/ASLv2 license [1].
> As far new versions of Aether stay under ASLv2 license, there is no question
> for Maven when upgrading dependency.
>
> Now, Aether 1.12 was released under EPL license only, and actual 1.13-SNAPSHOT
> sources are EPL only too. Upgrading Maven dependency will imply a license
> change, that must be voted upon.
>
> Regards,
>
> Hervé
>
>
> [1] http://maven.apache.org/ref/3.0.4-SNAPSHOT/apache-maven/dependencies.html
>
> Le samedi 16 juillet 2011, Benson Margulies a écrit :
>> Folks,
>>
>> I've submitted one tiny fix to Aether, and I have a feature proposal
>> I'm discussing with the proprietor: making the *-pattern in mirrors a
>> bit richer.
>>
>> Eventually, this would be 'as simple' as a change to the aether
>> provider to take a newer aether. However, I wonder if the PMC has
>> established any organized process of coordinating.
>>
>> --benson
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Coordinating with Aether
Posted by Hervé BOUTEMY <he...@free.fr>.
Good question :)
Current Maven versions (3.0.3 and 3.0.4-SNAPSHOT) use Aether 1.11, which has a
dual EPL/ASLv2 license [1].
As far new versions of Aether stay under ASLv2 license, there is no question
for Maven when upgrading dependency.
Now, Aether 1.12 was released under EPL license only, and actual 1.13-SNAPSHOT
sources are EPL only too. Upgrading Maven dependency will imply a license
change, that must be voted upon.
Regards,
Hervé
[1] http://maven.apache.org/ref/3.0.4-SNAPSHOT/apache-maven/dependencies.html
Le samedi 16 juillet 2011, Benson Margulies a écrit :
> Folks,
>
> I've submitted one tiny fix to Aether, and I have a feature proposal
> I'm discussing with the proprietor: making the *-pattern in mirrors a
> bit richer.
>
> Eventually, this would be 'as simple' as a change to the aether
> provider to take a newer aether. However, I wonder if the PMC has
> established any organized process of coordinating.
>
> --benson
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org