You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by Arnaud Héritier <ah...@gmail.com> on 2011/08/18 11:23:57 UTC

[VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Hi all,

  Thus as decided with Mark and Kristian I relaunch a new vote with a better
scope about what we are voting for.

  Next releases of SISU and Aether will be released at Eclipse.org under EPL
1.0 license.
  Before they were published under ASL or dual ASL/EPL licenses thus as
defined in our policy [1] this change put them in Category B [2] and we need
to validate this change by a vote with a majority of the PMC in favor (but
the vote is open to everybody).
  I push only one vote for both dependencies as for now I see no reason to
accept one and not the other.
  This vote will be open for 6 days as we are in august (If we have not
enough votes at the end of next wednesday will see if we really need to
extend it).

  The vote :

  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
published under EPL 1.0 License and released under eclipse.org governance
  [+0] No opinion, do what you want.
  [-1] I'm against because .... (please elaborate)

Arnaud

[1] http://maven.apache.org/developers/dependency-policies.html
[2] http://www.apache.org/legal/resolved.html#category-b

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Kristian Rosenvold <kr...@gmail.com>.

+1 binding

Kristian

Den 18.08.2011 11:23, skrev Arnaud Héritier:
> Hi all,
>
>    Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
>
>    Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
>    Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
>    I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>    This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
>
>    The vote :
>
>    [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance
>    [+0] No opinion, do what you want.
>    [-1] I'm against because .... (please elaborate)
>
> Arnaud
>
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Dennis Lundberg <de...@apache.org>.

+1

On 2011-08-18 11:23, Arnaud Héritier wrote:
> Hi all,
> 
>   Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
> 
>   Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
>   Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
>   I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>   This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
> 
>   The vote :
> 
>   [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance
>   [+0] No opinion, do what you want.
>   [-1] I'm against because .... (please elaborate)
> 
> Arnaud
> 
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 10:36 AM, Mark Struberg wrote:

> Me also, or should we ask on the eclipse aether list? (is there such a list already?)
> 

Not until project provisioning, which happens when the project creation review is over next week.

> LieGrue,
> strub
> 
> --- On Thu, 8/18/11, Olivier Lamy <ol...@apache.org> wrote:
> 
>> From: Olivier Lamy <ol...@apache.org>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 2:34 PM
>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>> 
>>> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>>> 
>>>> So I reformulate my question : 'how to be in the
>> initial set of
>>>> committers ?" too late ?
>>>> 
>>> 
>>> Just ask. As I posted previously, anyone who wants to
>> be listed as a committer I will add.
>> Oups I missed.
>> 
>> So I ask.
>> 
>>> 
>>>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>>>> 
>>>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
>> wrote:
>>>>> 
>>>>>> Hello,
>>>>>> Perso the license question doesn't matter
>> a lot as long we have a
>>>>>> compatible one with ASF.
>>>>>> Have a look at tomcat 7 or the cxf
>> distribs which contains ecj and/or
>>>>>> jetty so the Eclipse license is not a
>> trouble for ASF products (sure
>>>>>> at least for me).
>>>>>> My main point is more regarding the
>> governance model and the devs/pmcs
>>>>>> involved for those projects @eclipse.
>>>>>> If I look at the various proposals for
>> aether [1] and sisu [2], the
>>>>>> initial set of committers doesn't show a
>> diversity or a huge
>>>>>> community.
>>>>>> 
>>>>>> So even if probably I won't be a huge
>> committer, how will it be
>>>>>> possible to participate in the projects ?
>>>>> 
>>>>> The process is more or less identical to
>> Apache. The voting starts by a committer nominating someone
>> and the process is tracked in the portal where votes are
>> registered and tracked. Election of committers is the domain
>> of committers and the PMC has to approve the final vote. PMC
>> members are usually committers. As committers vote, they are
>> posted to the mailing list in question so people can see the
>> progress.
>>>>> 
>>>>>> And probably some others Maven folks have
>> the same question.
>>>>>> 
>>>>>> Thanks,
>>>>>> --
>>>>>> Olivier Lamy
>>>>>> Talend : http://talend.com
>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>> 
>>>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>>> 
>>>>>> 
>>>>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>>>>>> Jason, Brian, Benjamin or any other
>> person involved,
>>>>>>> 
>>>>>>> Before voting on this issue, I'd like
>> to get an idea what it means for us. So please allow me a
>> few questions:
>>>>>>> 
>>>>>>> a.) how can appache maven committers
>> anticipate on aether over at Eclipse? What if someone (like
>> me) likes to contribute, but wants to make sure that his
>> contributions are also possible to release separately under
>> ALv2?
>>>>>>> 
>>>>>>> b.) is it possible to operate aether
>> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
>> Is there any direct guice depending code in aether?
>>>>>>> 
>>>>>>> c.) will the package names remain
>> com.sonatype or will they get changed to org.eclipse.*? This
>> is important for us to know. If so, we can just cancel the
>> vote and wait for this stuff to be released at Eclipse.
>>>>>>> 
>>>>>>> d.) How long will it take to get the
>> first aether release done at Eclipse?
>>>>>>> 
>>>>>>> If there is a chilly way for maven
>> committers to get involved with that stuff over at Eclipse,
>> then this would be a big pro.
>>>>>>> 
>>>>>>> txs and LieGrue,
>>>>>>> strub
>>>>>>> 
>>>>>>> 
>>>>>>> --- On Thu, 8/18/11, Anders Hammar
>> <an...@hammar.net>
>> wrote:
>>>>>>> 
>>>>>>>> From: Anders Hammar <an...@hammar.net>
>>>>>>>> Subject: Re: [VOTE] Usage of
>> Aether and Sisu as dependencies of maven core with EPL
>> licenses - take 2
>>>>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>>>>> Date: Thursday, August 18, 2011,
>> 10:56 AM
>>>>>>>> +1 (non-binding)
>>>>>>>> 
>>>>>>>> /Anders
>>>>>>>> 
>>>>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>>>>> Hi all,
>>>>>>>>> 
>>>>>>>>>  Thus as decided with Mark
>> and Kristian I relaunch a
>>>>>>>> new vote with a better
>>>>>>>>> scope about what we are voting
>> for.
>>>>>>>>> 
>>>>>>>>>  Next releases of SISU and
>> Aether will be released at
>>>>>>>> Eclipse.org under EPL
>>>>>>>>> 1.0 license.
>>>>>>>>>  Before they were published
>> under ASL or dual ASL/EPL
>>>>>>>> licenses thus as
>>>>>>>>> defined in our policy [1] this
>> change put them in
>>>>>>>> Category B [2] and we need
>>>>>>>>> to validate this change by a
>> vote with a majority of
>>>>>>>> the PMC in favor (but
>>>>>>>>> the vote is open to
>> everybody).
>>>>>>>>>  I push only one vote for
>> both dependencies as for
>>>>>>>> now I see no reason to
>>>>>>>>> accept one and not the other.
>>>>>>>>>  This vote will be open for 6
>> days as we are in
>>>>>>>> august (If we have not
>>>>>>>>> enough votes at the end of
>> next wednesday will see if
>>>>>>>> we really need to
>>>>>>>>> extend it).
>>>>>>>>> 
>>>>>>>>>  The vote :
>>>>>>>>> 
>>>>>>>>>  [+1] I'm in favor to use as
>> Maven core dependencies
>>>>>>>> SISU and AETHER libraries
>>>>>>>>> published under EPL 1.0
>> License and released under
>>>>>>>> eclipse.org governance
>>>>>>>>>  [+0] No opinion, do what you
>> want.
>>>>>>>>>  [-1] I'm against because
>> .... (please elaborate)
>>>>>>>>> 
>>>>>>>>> Arnaud
>>>>>>>>> 
>>>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>> ---------------------------------------------------------------------
>>>>>>>> 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
>>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Jason
>>>>> 
>>>>> 
>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> 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
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Olivier Lamy
>>>> Talend : http://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
>>>> 
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> 
>> ----------------------------------------------------------
>>> Jason van Zyl
>>> 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
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> Olivier Lamy
>> Talend : http://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
>> 
>> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

You've all be added to the proposal:

http://eclipse.org/proposals/technology.aether/

On Aug 18, 2011, at 2:50 PM, John Casey wrote:

> And me, please.
> 
> On 8/18/11 1:01 PM, Brian Fox wrote:
>> I'd like to be added as well please.
>> 
>> On Thu, Aug 18, 2011 at 10:45 AM, Jason van Zyl<ja...@maven.org>  wrote:
>>> I'll get Wayne Beaton to add yourself and Olivier to the proposal.
>>> 
>>> On Aug 18, 2011, at 10:36 AM, Mark Struberg wrote:
>>> 
>>>> Me also, or should we ask on the eclipse aether list? (is there such a list already?)
>>>> 
>>>> LieGrue,
>>>> strub
>>>> 
>>>> --- On Thu, 8/18/11, Olivier Lamy<ol...@apache.org>  wrote:
>>>> 
>>>>> From: Olivier Lamy<ol...@apache.org>
>>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>>>> To: "Maven Developers List"<de...@maven.apache.org>
>>>>> Date: Thursday, August 18, 2011, 2:34 PM
>>>>> 2011/8/18 Jason van Zyl<ja...@maven.org>:
>>>>>> 
>>>>>> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>>>>>> 
>>>>>>> So I reformulate my question : 'how to be in the
>>>>> initial set of
>>>>>>> committers ?" too late ?
>>>>>>> 
>>>>>> 
>>>>>> Just ask. As I posted previously, anyone who wants to
>>>>> be listed as a committer I will add.
>>>>> Oups I missed.
>>>>> 
>>>>> So I ask.
>>>>> 
>>>>>> 
>>>>>>> 2011/8/18 Jason van Zyl<ja...@maven.org>:
>>>>>>>> 
>>>>>>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Hello,
>>>>>>>>> Perso the license question doesn't matter
>>>>> a lot as long we have a
>>>>>>>>> compatible one with ASF.
>>>>>>>>> Have a look at tomcat 7 or the cxf
>>>>> distribs which contains ecj and/or
>>>>>>>>> jetty so the Eclipse license is not a
>>>>> trouble for ASF products (sure
>>>>>>>>> at least for me).
>>>>>>>>> My main point is more regarding the
>>>>> governance model and the devs/pmcs
>>>>>>>>> involved for those projects @eclipse.
>>>>>>>>> If I look at the various proposals for
>>>>> aether [1] and sisu [2], the
>>>>>>>>> initial set of committers doesn't show a
>>>>> diversity or a huge
>>>>>>>>> community.
>>>>>>>>> 
>>>>>>>>> So even if probably I won't be a huge
>>>>> committer, how will it be
>>>>>>>>> possible to participate in the projects ?
>>>>>>>> 
>>>>>>>> The process is more or less identical to
>>>>> Apache. The voting starts by a committer nominating someone
>>>>> and the process is tracked in the portal where votes are
>>>>> registered and tracked. Election of committers is the domain
>>>>> of committers and the PMC has to approve the final vote. PMC
>>>>> members are usually committers. As committers vote, they are
>>>>> posted to the mailing list in question so people can see the
>>>>> progress.
>>>>>>>> 
>>>>>>>>> And probably some others Maven folks have
>>>>> the same question.
>>>>>>>>> 
>>>>>>>>> Thanks,
>>>>>>>>> --
>>>>>>>>> Olivier Lamy
>>>>>>>>> Talend : http://talend.com
>>>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>>>>> 
>>>>>>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>>>>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 2011/8/18 Mark Struberg<st...@yahoo.de>:
>>>>>>>>>> Jason, Brian, Benjamin or any other
>>>>> person involved,
>>>>>>>>>> 
>>>>>>>>>> Before voting on this issue, I'd like
>>>>> to get an idea what it means for us. So please allow me a
>>>>> few questions:
>>>>>>>>>> 
>>>>>>>>>> a.) how can appache maven committers
>>>>> anticipate on aether over at Eclipse? What if someone (like
>>>>> me) likes to contribute, but wants to make sure that his
>>>>> contributions are also possible to release separately under
>>>>> ALv2?
>>>>>>>>>> 
>>>>>>>>>> b.) is it possible to operate aether
>>>>> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
>>>>> Is there any direct guice depending code in aether?
>>>>>>>>>> 
>>>>>>>>>> c.) will the package names remain
>>>>> com.sonatype or will they get changed to org.eclipse.*? This
>>>>> is important for us to know. If so, we can just cancel the
>>>>> vote and wait for this stuff to be released at Eclipse.
>>>>>>>>>> 
>>>>>>>>>> d.) How long will it take to get the
>>>>> first aether release done at Eclipse?
>>>>>>>>>> 
>>>>>>>>>> If there is a chilly way for maven
>>>>> committers to get involved with that stuff over at Eclipse,
>>>>> then this would be a big pro.
>>>>>>>>>> 
>>>>>>>>>> txs and LieGrue,
>>>>>>>>>> strub
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --- On Thu, 8/18/11, Anders Hammar
>>>>> <an...@hammar.net>
>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> From: Anders Hammar<an...@hammar.net>
>>>>>>>>>>> Subject: Re: [VOTE] Usage of
>>>>> Aether and Sisu as dependencies of maven core with EPL
>>>>> licenses - take 2
>>>>>>>>>>> To: "Maven Developers List"<de...@maven.apache.org>
>>>>>>>>>>> Date: Thursday, August 18, 2011,
>>>>> 10:56 AM
>>>>>>>>>>> +1 (non-binding)
>>>>>>>>>>> 
>>>>>>>>>>> /Anders
>>>>>>>>>>> 
>>>>>>>>>>> 2011/8/18 Arnaud Héritier<ah...@gmail.com>:
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>> 
>>>>>>>>>>>>  Thus as decided with Mark
>>>>> and Kristian I relaunch a
>>>>>>>>>>> new vote with a better
>>>>>>>>>>>> scope about what we are voting
>>>>> for.
>>>>>>>>>>>> 
>>>>>>>>>>>>  Next releases of SISU and
>>>>> Aether will be released at
>>>>>>>>>>> Eclipse.org under EPL
>>>>>>>>>>>> 1.0 license.
>>>>>>>>>>>>  Before they were published
>>>>> under ASL or dual ASL/EPL
>>>>>>>>>>> licenses thus as
>>>>>>>>>>>> defined in our policy [1] this
>>>>> change put them in
>>>>>>>>>>> Category B [2] and we need
>>>>>>>>>>>> to validate this change by a
>>>>> vote with a majority of
>>>>>>>>>>> the PMC in favor (but
>>>>>>>>>>>> the vote is open to
>>>>> everybody).
>>>>>>>>>>>>  I push only one vote for
>>>>> both dependencies as for
>>>>>>>>>>> now I see no reason to
>>>>>>>>>>>> accept one and not the other.
>>>>>>>>>>>>  This vote will be open for 6
>>>>> days as we are in
>>>>>>>>>>> august (If we have not
>>>>>>>>>>>> enough votes at the end of
>>>>> next wednesday will see if
>>>>>>>>>>> we really need to
>>>>>>>>>>>> extend it).
>>>>>>>>>>>> 
>>>>>>>>>>>>  The vote :
>>>>>>>>>>>> 
>>>>>>>>>>>>  [+1] I'm in favor to use as
>>>>> Maven core dependencies
>>>>>>>>>>> SISU and AETHER libraries
>>>>>>>>>>>> published under EPL 1.0
>>>>> License and released under
>>>>>>>>>>> eclipse.org governance
>>>>>>>>>>>>  [+0] No opinion, do what you
>>>>> want.
>>>>>>>>>>>>  [-1] I'm against because
>>>>> .... (please elaborate)
>>>>>>>>>>>> 
>>>>>>>>>>>> Arnaud
>>>>>>>>>>>> 
>>>>>>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> 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
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> 
>>>>>>>> Jason
>>>>>>>> 
>>>>>>>> 
>>>>> ----------------------------------------------------------
>>>>>>>> Jason van Zyl
>>>>>>>> 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
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Olivier Lamy
>>>>>>> Talend : http://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
>>>>>>> 
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Jason
>>>>>> 
>>>>>> 
>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> 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
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Olivier Lamy
>>>>> Talend : http://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
>>>>> 
>>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> 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,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>> 
>>> To do two things at once is to do neither.
>>> 
>>>  -—Publilius Syrus, Roman slave, first century B.C.
>>> 
>>> 
>>> 
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
> 
> -- 
> John Casey
> Developer, PMC Chair - Apache Maven (http://maven.apache.org)
> Blog: http://www.johnofalltrades.name/
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

To do two things at once is to do neither.
 
 -—Publilius Syrus, Roman slave, first century B.C.

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by John Casey <jd...@commonjava.org>.

And me, please.

On 8/18/11 1:01 PM, Brian Fox wrote:
> I'd like to be added as well please.
>
> On Thu, Aug 18, 2011 at 10:45 AM, Jason van Zyl<ja...@maven.org>  wrote:
>> I'll get Wayne Beaton to add yourself and Olivier to the proposal.
>>
>> On Aug 18, 2011, at 10:36 AM, Mark Struberg wrote:
>>
>>> Me also, or should we ask on the eclipse aether list? (is there such a list already?)
>>>
>>> LieGrue,
>>> strub
>>>
>>> --- On Thu, 8/18/11, Olivier Lamy<ol...@apache.org>  wrote:
>>>
>>>> From: Olivier Lamy<ol...@apache.org>
>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>>> To: "Maven Developers List"<de...@maven.apache.org>
>>>> Date: Thursday, August 18, 2011, 2:34 PM
>>>> 2011/8/18 Jason van Zyl<ja...@maven.org>:
>>>>>
>>>>> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>>>>>
>>>>>> So I reformulate my question : 'how to be in the
>>>> initial set of
>>>>>> committers ?" too late ?
>>>>>>
>>>>>
>>>>> Just ask. As I posted previously, anyone who wants to
>>>> be listed as a committer I will add.
>>>> Oups I missed.
>>>>
>>>> So I ask.
>>>>
>>>>>
>>>>>> 2011/8/18 Jason van Zyl<ja...@maven.org>:
>>>>>>>
>>>>>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> Perso the license question doesn't matter
>>>> a lot as long we have a
>>>>>>>> compatible one with ASF.
>>>>>>>> Have a look at tomcat 7 or the cxf
>>>> distribs which contains ecj and/or
>>>>>>>> jetty so the Eclipse license is not a
>>>> trouble for ASF products (sure
>>>>>>>> at least for me).
>>>>>>>> My main point is more regarding the
>>>> governance model and the devs/pmcs
>>>>>>>> involved for those projects @eclipse.
>>>>>>>> If I look at the various proposals for
>>>> aether [1] and sisu [2], the
>>>>>>>> initial set of committers doesn't show a
>>>> diversity or a huge
>>>>>>>> community.
>>>>>>>>
>>>>>>>> So even if probably I won't be a huge
>>>> committer, how will it be
>>>>>>>> possible to participate in the projects ?
>>>>>>>
>>>>>>> The process is more or less identical to
>>>> Apache. The voting starts by a committer nominating someone
>>>> and the process is tracked in the portal where votes are
>>>> registered and tracked. Election of committers is the domain
>>>> of committers and the PMC has to approve the final vote. PMC
>>>> members are usually committers. As committers vote, they are
>>>> posted to the mailing list in question so people can see the
>>>> progress.
>>>>>>>
>>>>>>>> And probably some others Maven folks have
>>>> the same question.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> --
>>>>>>>> Olivier Lamy
>>>>>>>> Talend : http://talend.com
>>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>>>>
>>>>>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>>>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>>>>>
>>>>>>>>
>>>>>>>> 2011/8/18 Mark Struberg<st...@yahoo.de>:
>>>>>>>>> Jason, Brian, Benjamin or any other
>>>> person involved,
>>>>>>>>>
>>>>>>>>> Before voting on this issue, I'd like
>>>> to get an idea what it means for us. So please allow me a
>>>> few questions:
>>>>>>>>>
>>>>>>>>> a.) how can appache maven committers
>>>> anticipate on aether over at Eclipse? What if someone (like
>>>> me) likes to contribute, but wants to make sure that his
>>>> contributions are also possible to release separately under
>>>> ALv2?
>>>>>>>>>
>>>>>>>>> b.) is it possible to operate aether
>>>> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
>>>> Is there any direct guice depending code in aether?
>>>>>>>>>
>>>>>>>>> c.) will the package names remain
>>>> com.sonatype or will they get changed to org.eclipse.*? This
>>>> is important for us to know. If so, we can just cancel the
>>>> vote and wait for this stuff to be released at Eclipse.
>>>>>>>>>
>>>>>>>>> d.) How long will it take to get the
>>>> first aether release done at Eclipse?
>>>>>>>>>
>>>>>>>>> If there is a chilly way for maven
>>>> committers to get involved with that stuff over at Eclipse,
>>>> then this would be a big pro.
>>>>>>>>>
>>>>>>>>> txs and LieGrue,
>>>>>>>>> strub
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --- On Thu, 8/18/11, Anders Hammar
>>>> <an...@hammar.net>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> From: Anders Hammar<an...@hammar.net>
>>>>>>>>>> Subject: Re: [VOTE] Usage of
>>>> Aether and Sisu as dependencies of maven core with EPL
>>>> licenses - take 2
>>>>>>>>>> To: "Maven Developers List"<de...@maven.apache.org>
>>>>>>>>>> Date: Thursday, August 18, 2011,
>>>> 10:56 AM
>>>>>>>>>> +1 (non-binding)
>>>>>>>>>>
>>>>>>>>>> /Anders
>>>>>>>>>>
>>>>>>>>>> 2011/8/18 Arnaud Héritier<ah...@gmail.com>:
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>>   Thus as decided with Mark
>>>> and Kristian I relaunch a
>>>>>>>>>> new vote with a better
>>>>>>>>>>> scope about what we are voting
>>>> for.
>>>>>>>>>>>
>>>>>>>>>>>   Next releases of SISU and
>>>> Aether will be released at
>>>>>>>>>> Eclipse.org under EPL
>>>>>>>>>>> 1.0 license.
>>>>>>>>>>>   Before they were published
>>>> under ASL or dual ASL/EPL
>>>>>>>>>> licenses thus as
>>>>>>>>>>> defined in our policy [1] this
>>>> change put them in
>>>>>>>>>> Category B [2] and we need
>>>>>>>>>>> to validate this change by a
>>>> vote with a majority of
>>>>>>>>>> the PMC in favor (but
>>>>>>>>>>> the vote is open to
>>>> everybody).
>>>>>>>>>>>   I push only one vote for
>>>> both dependencies as for
>>>>>>>>>> now I see no reason to
>>>>>>>>>>> accept one and not the other.
>>>>>>>>>>>   This vote will be open for 6
>>>> days as we are in
>>>>>>>>>> august (If we have not
>>>>>>>>>>> enough votes at the end of
>>>> next wednesday will see if
>>>>>>>>>> we really need to
>>>>>>>>>>> extend it).
>>>>>>>>>>>
>>>>>>>>>>>   The vote :
>>>>>>>>>>>
>>>>>>>>>>>   [+1] I'm in favor to use as
>>>> Maven core dependencies
>>>>>>>>>> SISU and AETHER libraries
>>>>>>>>>>> published under EPL 1.0
>>>> License and released under
>>>>>>>>>> eclipse.org governance
>>>>>>>>>>>   [+0] No opinion, do what you
>>>> want.
>>>>>>>>>>>   [-1] I'm against because
>>>> .... (please elaborate)
>>>>>>>>>>>
>>>>>>>>>>> Arnaud
>>>>>>>>>>>
>>>>>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>>
>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Olivier Lamy
>>>>>> Talend : http://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
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>>
>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend : http://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
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> To do two things at once is to do neither.
>>
>>   -—Publilius Syrus, Roman slave, first century B.C.
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

-- 
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Brian Fox <br...@infinity.nu>.

I'd like to be added as well please.

On Thu, Aug 18, 2011 at 10:45 AM, Jason van Zyl <ja...@maven.org> wrote:
> I'll get Wayne Beaton to add yourself and Olivier to the proposal.
>
> On Aug 18, 2011, at 10:36 AM, Mark Struberg wrote:
>
>> Me also, or should we ask on the eclipse aether list? (is there such a list already?)
>>
>> LieGrue,
>> strub
>>
>> --- On Thu, 8/18/11, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> From: Olivier Lamy <ol...@apache.org>
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>> To: "Maven Developers List" <de...@maven.apache.org>
>>> Date: Thursday, August 18, 2011, 2:34 PM
>>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>>>
>>>> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>>>>
>>>>> So I reformulate my question : 'how to be in the
>>> initial set of
>>>>> committers ?" too late ?
>>>>>
>>>>
>>>> Just ask. As I posted previously, anyone who wants to
>>> be listed as a committer I will add.
>>> Oups I missed.
>>>
>>> So I ask.
>>>
>>>>
>>>>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>>>>>
>>>>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>> Perso the license question doesn't matter
>>> a lot as long we have a
>>>>>>> compatible one with ASF.
>>>>>>> Have a look at tomcat 7 or the cxf
>>> distribs which contains ecj and/or
>>>>>>> jetty so the Eclipse license is not a
>>> trouble for ASF products (sure
>>>>>>> at least for me).
>>>>>>> My main point is more regarding the
>>> governance model and the devs/pmcs
>>>>>>> involved for those projects @eclipse.
>>>>>>> If I look at the various proposals for
>>> aether [1] and sisu [2], the
>>>>>>> initial set of committers doesn't show a
>>> diversity or a huge
>>>>>>> community.
>>>>>>>
>>>>>>> So even if probably I won't be a huge
>>> committer, how will it be
>>>>>>> possible to participate in the projects ?
>>>>>>
>>>>>> The process is more or less identical to
>>> Apache. The voting starts by a committer nominating someone
>>> and the process is tracked in the portal where votes are
>>> registered and tracked. Election of committers is the domain
>>> of committers and the PMC has to approve the final vote. PMC
>>> members are usually committers. As committers vote, they are
>>> posted to the mailing list in question so people can see the
>>> progress.
>>>>>>
>>>>>>> And probably some others Maven folks have
>>> the same question.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> --
>>>>>>> Olivier Lamy
>>>>>>> Talend : http://talend.com
>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>>>
>>>>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>>>>
>>>>>>>
>>>>>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>>>>>>> Jason, Brian, Benjamin or any other
>>> person involved,
>>>>>>>>
>>>>>>>> Before voting on this issue, I'd like
>>> to get an idea what it means for us. So please allow me a
>>> few questions:
>>>>>>>>
>>>>>>>> a.) how can appache maven committers
>>> anticipate on aether over at Eclipse? What if someone (like
>>> me) likes to contribute, but wants to make sure that his
>>> contributions are also possible to release separately under
>>> ALv2?
>>>>>>>>
>>>>>>>> b.) is it possible to operate aether
>>> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
>>> Is there any direct guice depending code in aether?
>>>>>>>>
>>>>>>>> c.) will the package names remain
>>> com.sonatype or will they get changed to org.eclipse.*? This
>>> is important for us to know. If so, we can just cancel the
>>> vote and wait for this stuff to be released at Eclipse.
>>>>>>>>
>>>>>>>> d.) How long will it take to get the
>>> first aether release done at Eclipse?
>>>>>>>>
>>>>>>>> If there is a chilly way for maven
>>> committers to get involved with that stuff over at Eclipse,
>>> then this would be a big pro.
>>>>>>>>
>>>>>>>> txs and LieGrue,
>>>>>>>> strub
>>>>>>>>
>>>>>>>>
>>>>>>>> --- On Thu, 8/18/11, Anders Hammar
>>> <an...@hammar.net>
>>> wrote:
>>>>>>>>
>>>>>>>>> From: Anders Hammar <an...@hammar.net>
>>>>>>>>> Subject: Re: [VOTE] Usage of
>>> Aether and Sisu as dependencies of maven core with EPL
>>> licenses - take 2
>>>>>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>>>>>> Date: Thursday, August 18, 2011,
>>> 10:56 AM
>>>>>>>>> +1 (non-binding)
>>>>>>>>>
>>>>>>>>> /Anders
>>>>>>>>>
>>>>>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>>  Thus as decided with Mark
>>> and Kristian I relaunch a
>>>>>>>>> new vote with a better
>>>>>>>>>> scope about what we are voting
>>> for.
>>>>>>>>>>
>>>>>>>>>>  Next releases of SISU and
>>> Aether will be released at
>>>>>>>>> Eclipse.org under EPL
>>>>>>>>>> 1.0 license.
>>>>>>>>>>  Before they were published
>>> under ASL or dual ASL/EPL
>>>>>>>>> licenses thus as
>>>>>>>>>> defined in our policy [1] this
>>> change put them in
>>>>>>>>> Category B [2] and we need
>>>>>>>>>> to validate this change by a
>>> vote with a majority of
>>>>>>>>> the PMC in favor (but
>>>>>>>>>> the vote is open to
>>> everybody).
>>>>>>>>>>  I push only one vote for
>>> both dependencies as for
>>>>>>>>> now I see no reason to
>>>>>>>>>> accept one and not the other.
>>>>>>>>>>  This vote will be open for 6
>>> days as we are in
>>>>>>>>> august (If we have not
>>>>>>>>>> enough votes at the end of
>>> next wednesday will see if
>>>>>>>>> we really need to
>>>>>>>>>> extend it).
>>>>>>>>>>
>>>>>>>>>>  The vote :
>>>>>>>>>>
>>>>>>>>>>  [+1] I'm in favor to use as
>>> Maven core dependencies
>>>>>>>>> SISU and AETHER libraries
>>>>>>>>>> published under EPL 1.0
>>> License and released under
>>>>>>>>> eclipse.org governance
>>>>>>>>>>  [+0] No opinion, do what you
>>> want.
>>>>>>>>>>  [-1] I'm against because
>>> .... (please elaborate)
>>>>>>>>>>
>>>>>>>>>> Arnaud
>>>>>>>>>>
>>>>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>>>> 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
>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>>
>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> Talend : http://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
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>>
>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend : http://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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> To do two things at once is to do neither.
>
>  -—Publilius Syrus, Roman slave, first century B.C.
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

I'll get Wayne Beaton to add yourself and Olivier to the proposal.

On Aug 18, 2011, at 10:36 AM, Mark Struberg wrote:

> Me also, or should we ask on the eclipse aether list? (is there such a list already?)
> 
> LieGrue,
> strub
> 
> --- On Thu, 8/18/11, Olivier Lamy <ol...@apache.org> wrote:
> 
>> From: Olivier Lamy <ol...@apache.org>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 2:34 PM
>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>> 
>>> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>>> 
>>>> So I reformulate my question : 'how to be in the
>> initial set of
>>>> committers ?" too late ?
>>>> 
>>> 
>>> Just ask. As I posted previously, anyone who wants to
>> be listed as a committer I will add.
>> Oups I missed.
>> 
>> So I ask.
>> 
>>> 
>>>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>>>> 
>>>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
>> wrote:
>>>>> 
>>>>>> Hello,
>>>>>> Perso the license question doesn't matter
>> a lot as long we have a
>>>>>> compatible one with ASF.
>>>>>> Have a look at tomcat 7 or the cxf
>> distribs which contains ecj and/or
>>>>>> jetty so the Eclipse license is not a
>> trouble for ASF products (sure
>>>>>> at least for me).
>>>>>> My main point is more regarding the
>> governance model and the devs/pmcs
>>>>>> involved for those projects @eclipse.
>>>>>> If I look at the various proposals for
>> aether [1] and sisu [2], the
>>>>>> initial set of committers doesn't show a
>> diversity or a huge
>>>>>> community.
>>>>>> 
>>>>>> So even if probably I won't be a huge
>> committer, how will it be
>>>>>> possible to participate in the projects ?
>>>>> 
>>>>> The process is more or less identical to
>> Apache. The voting starts by a committer nominating someone
>> and the process is tracked in the portal where votes are
>> registered and tracked. Election of committers is the domain
>> of committers and the PMC has to approve the final vote. PMC
>> members are usually committers. As committers vote, they are
>> posted to the mailing list in question so people can see the
>> progress.
>>>>> 
>>>>>> And probably some others Maven folks have
>> the same question.
>>>>>> 
>>>>>> Thanks,
>>>>>> --
>>>>>> Olivier Lamy
>>>>>> Talend : http://talend.com
>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>> 
>>>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>>> 
>>>>>> 
>>>>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>>>>>> Jason, Brian, Benjamin or any other
>> person involved,
>>>>>>> 
>>>>>>> Before voting on this issue, I'd like
>> to get an idea what it means for us. So please allow me a
>> few questions:
>>>>>>> 
>>>>>>> a.) how can appache maven committers
>> anticipate on aether over at Eclipse? What if someone (like
>> me) likes to contribute, but wants to make sure that his
>> contributions are also possible to release separately under
>> ALv2?
>>>>>>> 
>>>>>>> b.) is it possible to operate aether
>> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
>> Is there any direct guice depending code in aether?
>>>>>>> 
>>>>>>> c.) will the package names remain
>> com.sonatype or will they get changed to org.eclipse.*? This
>> is important for us to know. If so, we can just cancel the
>> vote and wait for this stuff to be released at Eclipse.
>>>>>>> 
>>>>>>> d.) How long will it take to get the
>> first aether release done at Eclipse?
>>>>>>> 
>>>>>>> If there is a chilly way for maven
>> committers to get involved with that stuff over at Eclipse,
>> then this would be a big pro.
>>>>>>> 
>>>>>>> txs and LieGrue,
>>>>>>> strub
>>>>>>> 
>>>>>>> 
>>>>>>> --- On Thu, 8/18/11, Anders Hammar
>> <an...@hammar.net>
>> wrote:
>>>>>>> 
>>>>>>>> From: Anders Hammar <an...@hammar.net>
>>>>>>>> Subject: Re: [VOTE] Usage of
>> Aether and Sisu as dependencies of maven core with EPL
>> licenses - take 2
>>>>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>>>>> Date: Thursday, August 18, 2011,
>> 10:56 AM
>>>>>>>> +1 (non-binding)
>>>>>>>> 
>>>>>>>> /Anders
>>>>>>>> 
>>>>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>>>>> Hi all,
>>>>>>>>> 
>>>>>>>>>  Thus as decided with Mark
>> and Kristian I relaunch a
>>>>>>>> new vote with a better
>>>>>>>>> scope about what we are voting
>> for.
>>>>>>>>> 
>>>>>>>>>  Next releases of SISU and
>> Aether will be released at
>>>>>>>> Eclipse.org under EPL
>>>>>>>>> 1.0 license.
>>>>>>>>>  Before they were published
>> under ASL or dual ASL/EPL
>>>>>>>> licenses thus as
>>>>>>>>> defined in our policy [1] this
>> change put them in
>>>>>>>> Category B [2] and we need
>>>>>>>>> to validate this change by a
>> vote with a majority of
>>>>>>>> the PMC in favor (but
>>>>>>>>> the vote is open to
>> everybody).
>>>>>>>>>  I push only one vote for
>> both dependencies as for
>>>>>>>> now I see no reason to
>>>>>>>>> accept one and not the other.
>>>>>>>>>  This vote will be open for 6
>> days as we are in
>>>>>>>> august (If we have not
>>>>>>>>> enough votes at the end of
>> next wednesday will see if
>>>>>>>> we really need to
>>>>>>>>> extend it).
>>>>>>>>> 
>>>>>>>>>  The vote :
>>>>>>>>> 
>>>>>>>>>  [+1] I'm in favor to use as
>> Maven core dependencies
>>>>>>>> SISU and AETHER libraries
>>>>>>>>> published under EPL 1.0
>> License and released under
>>>>>>>> eclipse.org governance
>>>>>>>>>  [+0] No opinion, do what you
>> want.
>>>>>>>>>  [-1] I'm against because
>> .... (please elaborate)
>>>>>>>>> 
>>>>>>>>> Arnaud
>>>>>>>>> 
>>>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>> ---------------------------------------------------------------------
>>>>>>>> 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
>>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Jason
>>>>> 
>>>>> 
>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> 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
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Olivier Lamy
>>>> Talend : http://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
>>>> 
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> 
>> ----------------------------------------------------------
>>> Jason van Zyl
>>> 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
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> Olivier Lamy
>> Talend : http://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
>> 
>> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

To do two things at once is to do neither.
 
 -—Publilius Syrus, Roman slave, first century B.C.

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

Me also, or should we ask on the eclipse aether list? (is there such a list already?)

LieGrue,
strub

--- On Thu, 8/18/11, Olivier Lamy <ol...@apache.org> wrote:

> From: Olivier Lamy <ol...@apache.org>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 2:34 PM
> 2011/8/18 Jason van Zyl <ja...@maven.org>:
> >
> > On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
> >
> >> So I reformulate my question : 'how to be in the
> initial set of
> >> committers ?" too late ?
> >>
> >
> > Just ask. As I posted previously, anyone who wants to
> be listed as a committer I will add.
> Oups I missed.
> 
> So I ask.
> 
> >
> >> 2011/8/18 Jason van Zyl <ja...@maven.org>:
> >>>
> >>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy
> wrote:
> >>>
> >>>> Hello,
> >>>> Perso the license question doesn't matter
> a lot as long we have a
> >>>> compatible one with ASF.
> >>>> Have a look at tomcat 7 or the cxf
> distribs which contains ecj and/or
> >>>> jetty so the Eclipse license is not a
> trouble for ASF products (sure
> >>>> at least for me).
> >>>> My main point is more regarding the
> governance model and the devs/pmcs
> >>>> involved for those projects @eclipse.
> >>>> If I look at the various proposals for
> aether [1] and sisu [2], the
> >>>> initial set of committers doesn't show a
> diversity or a huge
> >>>> community.
> >>>>
> >>>> So even if probably I won't be a huge
> committer, how will it be
> >>>> possible to participate in the projects ?
> >>>
> >>> The process is more or less identical to
> Apache. The voting starts by a committer nominating someone
> and the process is tracked in the portal where votes are
> registered and tracked. Election of committers is the domain
> of committers and the PMC has to approve the final vote. PMC
> members are usually committers. As committers vote, they are
> posted to the mailing list in question so people can see the
> progress.
> >>>
> >>>> And probably some others Maven folks have
> the same question.
> >>>>
> >>>> Thanks,
> >>>> --
> >>>> Olivier Lamy
> >>>> Talend : http://talend.com
> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>>
> >>>> [1] http://www.eclipse.org/proposals/technology.aether/
> >>>> [2] http://www.eclipse.org/proposals/technology.sisu/
> >>>>
> >>>>
> >>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
> >>>>> Jason, Brian, Benjamin or any other
> person involved,
> >>>>>
> >>>>> Before voting on this issue, I'd like
> to get an idea what it means for us. So please allow me a
> few questions:
> >>>>>
> >>>>> a.) how can appache maven committers
> anticipate on aether over at Eclipse? What if someone (like
> me) likes to contribute, but wants to make sure that his
> contributions are also possible to release separately under
> ALv2?
> >>>>>
> >>>>> b.) is it possible to operate aether
> without sisu? Pure JSR-330 and/or plexus DI stuff is fine.
> Is there any direct guice depending code in aether?
> >>>>>
> >>>>> c.) will the package names remain
> com.sonatype or will they get changed to org.eclipse.*? This
> is important for us to know. If so, we can just cancel the
> vote and wait for this stuff to be released at Eclipse.
> >>>>>
> >>>>> d.) How long will it take to get the
> first aether release done at Eclipse?
> >>>>>
> >>>>> If there is a chilly way for maven
> committers to get involved with that stuff over at Eclipse,
> then this would be a big pro.
> >>>>>
> >>>>> txs and LieGrue,
> >>>>> strub
> >>>>>
> >>>>>
> >>>>> --- On Thu, 8/18/11, Anders Hammar
> <an...@hammar.net>
> wrote:
> >>>>>
> >>>>>> From: Anders Hammar <an...@hammar.net>
> >>>>>> Subject: Re: [VOTE] Usage of
> Aether and Sisu as dependencies of maven core with EPL
> licenses - take 2
> >>>>>> To: "Maven Developers List" <de...@maven.apache.org>
> >>>>>> Date: Thursday, August 18, 2011,
> 10:56 AM
> >>>>>> +1 (non-binding)
> >>>>>>
> >>>>>> /Anders
> >>>>>>
> >>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>>  Thus as decided with Mark
> and Kristian I relaunch a
> >>>>>> new vote with a better
> >>>>>>> scope about what we are voting
> for.
> >>>>>>>
> >>>>>>>  Next releases of SISU and
> Aether will be released at
> >>>>>> Eclipse.org under EPL
> >>>>>>> 1.0 license.
> >>>>>>>  Before they were published
> under ASL or dual ASL/EPL
> >>>>>> licenses thus as
> >>>>>>> defined in our policy [1] this
> change put them in
> >>>>>> Category B [2] and we need
> >>>>>>> to validate this change by a
> vote with a majority of
> >>>>>> the PMC in favor (but
> >>>>>>> the vote is open to
> everybody).
> >>>>>>>  I push only one vote for
> both dependencies as for
> >>>>>> now I see no reason to
> >>>>>>> accept one and not the other.
> >>>>>>>  This vote will be open for 6
> days as we are in
> >>>>>> august (If we have not
> >>>>>>> enough votes at the end of
> next wednesday will see if
> >>>>>> we really need to
> >>>>>>> extend it).
> >>>>>>>
> >>>>>>>  The vote :
> >>>>>>>
> >>>>>>>  [+1] I'm in favor to use as
> Maven core dependencies
> >>>>>> SISU and AETHER libraries
> >>>>>>> published under EPL 1.0
> License and released under
> >>>>>> eclipse.org governance
> >>>>>>>  [+0] No opinion, do what you
> want.
> >>>>>>>  [-1] I'm against because
> .... (please elaborate)
> >>>>>>>
> >>>>>>> Arnaud
> >>>>>>>
> >>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
> >>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
> >>>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> 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
> >>>>
> >>>
> >>> Thanks,
> >>>
> >>> Jason
> >>>
> >>>
> ----------------------------------------------------------
> >>> Jason van Zyl
> >>> 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
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Talend : http://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
> >>
> >
> > Thanks,
> >
> > Jason
> >
> >
> ----------------------------------------------------------
> > Jason van Zyl
> > 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
> >
> >
> >
> >
> 
> 
> 
> -- 
> Olivier Lamy
> Talend : http://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
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Olivier Lamy <ol...@apache.org>.

2011/8/18 Jason van Zyl <ja...@maven.org>:
>
> On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:
>
>> So I reformulate my question : 'how to be in the initial set of
>> committers ?" too late ?
>>
>
> Just ask. As I posted previously, anyone who wants to be listed as a committer I will add.
Oups I missed.

So I ask.

>
>> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>>>
>>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy wrote:
>>>
>>>> Hello,
>>>> Perso the license question doesn't matter a lot as long we have a
>>>> compatible one with ASF.
>>>> Have a look at tomcat 7 or the cxf distribs which contains ecj and/or
>>>> jetty so the Eclipse license is not a trouble for ASF products (sure
>>>> at least for me).
>>>> My main point is more regarding the governance model and the devs/pmcs
>>>> involved for those projects @eclipse.
>>>> If I look at the various proposals for aether [1] and sisu [2], the
>>>> initial set of committers doesn't show a diversity or a huge
>>>> community.
>>>>
>>>> So even if probably I won't be a huge committer, how will it be
>>>> possible to participate in the projects ?
>>>
>>> The process is more or less identical to Apache. The voting starts by a committer nominating someone and the process is tracked in the portal where votes are registered and tracked. Election of committers is the domain of committers and the PMC has to approve the final vote. PMC members are usually committers. As committers vote, they are posted to the mailing list in question so people can see the progress.
>>>
>>>> And probably some others Maven folks have the same question.
>>>>
>>>> Thanks,
>>>> --
>>>> Olivier Lamy
>>>> Talend : http://talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>>>
>>>>
>>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>>>> Jason, Brian, Benjamin or any other person involved,
>>>>>
>>>>> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>>>>>
>>>>> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>>>>>
>>>>> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>>>>>
>>>>> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>>>>>
>>>>> d.) How long will it take to get the first aether release done at Eclipse?
>>>>>
>>>>> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>>>>>
>>>>> txs and LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>>>>>
>>>>>> From: Anders Hammar <an...@hammar.net>
>>>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>>> Date: Thursday, August 18, 2011, 10:56 AM
>>>>>> +1 (non-binding)
>>>>>>
>>>>>> /Anders
>>>>>>
>>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>>> Hi all,
>>>>>>>
>>>>>>>  Thus as decided with Mark and Kristian I relaunch a
>>>>>> new vote with a better
>>>>>>> scope about what we are voting for.
>>>>>>>
>>>>>>>  Next releases of SISU and Aether will be released at
>>>>>> Eclipse.org under EPL
>>>>>>> 1.0 license.
>>>>>>>  Before they were published under ASL or dual ASL/EPL
>>>>>> licenses thus as
>>>>>>> defined in our policy [1] this change put them in
>>>>>> Category B [2] and we need
>>>>>>> to validate this change by a vote with a majority of
>>>>>> the PMC in favor (but
>>>>>>> the vote is open to everybody).
>>>>>>>  I push only one vote for both dependencies as for
>>>>>> now I see no reason to
>>>>>>> accept one and not the other.
>>>>>>>  This vote will be open for 6 days as we are in
>>>>>> august (If we have not
>>>>>>> enough votes at the end of next wednesday will see if
>>>>>> we really need to
>>>>>>> extend it).
>>>>>>>
>>>>>>>  The vote :
>>>>>>>
>>>>>>>  [+1] I'm in favor to use as Maven core dependencies
>>>>>> SISU and AETHER libraries
>>>>>>> published under EPL 1.0 License and released under
>>>>>> eclipse.org governance
>>>>>>>  [+0] No opinion, do what you want.
>>>>>>>  [-1] I'm against because .... (please elaborate)
>>>>>>>
>>>>>>> Arnaud
>>>>>>>
>>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> 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
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend : http://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
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> 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
>
>
>
>



-- 
Olivier Lamy
Talend : http://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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 10:27 AM, Olivier Lamy wrote:

> So I reformulate my question : 'how to be in the initial set of
> committers ?" too late ?
> 

Just ask. As I posted previously, anyone who wants to be listed as a committer I will add. 

> 2011/8/18 Jason van Zyl <ja...@maven.org>:
>> 
>> On Aug 18, 2011, at 9:51 AM, Olivier Lamy wrote:
>> 
>>> Hello,
>>> Perso the license question doesn't matter a lot as long we have a
>>> compatible one with ASF.
>>> Have a look at tomcat 7 or the cxf distribs which contains ecj and/or
>>> jetty so the Eclipse license is not a trouble for ASF products (sure
>>> at least for me).
>>> My main point is more regarding the governance model and the devs/pmcs
>>> involved for those projects @eclipse.
>>> If I look at the various proposals for aether [1] and sisu [2], the
>>> initial set of committers doesn't show a diversity or a huge
>>> community.
>>> 
>>> So even if probably I won't be a huge committer, how will it be
>>> possible to participate in the projects ?
>> 
>> The process is more or less identical to Apache. The voting starts by a committer nominating someone and the process is tracked in the portal where votes are registered and tracked. Election of committers is the domain of committers and the PMC has to approve the final vote. PMC members are usually committers. As committers vote, they are posted to the mailing list in question so people can see the progress.
>> 
>>> And probably some others Maven folks have the same question.
>>> 
>>> Thanks,
>>> --
>>> Olivier Lamy
>>> Talend : http://talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> 
>>> [1] http://www.eclipse.org/proposals/technology.aether/
>>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>> 
>>> 
>>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>>> Jason, Brian, Benjamin or any other person involved,
>>>> 
>>>> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>>>> 
>>>> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>>>> 
>>>> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>>>> 
>>>> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>>>> 
>>>> d.) How long will it take to get the first aether release done at Eclipse?
>>>> 
>>>> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>>>> 
>>>> txs and LieGrue,
>>>> strub
>>>> 
>>>> 
>>>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>>>> 
>>>>> From: Anders Hammar <an...@hammar.net>
>>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>> Date: Thursday, August 18, 2011, 10:56 AM
>>>>> +1 (non-binding)
>>>>> 
>>>>> /Anders
>>>>> 
>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>> Hi all,
>>>>>> 
>>>>>>  Thus as decided with Mark and Kristian I relaunch a
>>>>> new vote with a better
>>>>>> scope about what we are voting for.
>>>>>> 
>>>>>>  Next releases of SISU and Aether will be released at
>>>>> Eclipse.org under EPL
>>>>>> 1.0 license.
>>>>>>  Before they were published under ASL or dual ASL/EPL
>>>>> licenses thus as
>>>>>> defined in our policy [1] this change put them in
>>>>> Category B [2] and we need
>>>>>> to validate this change by a vote with a majority of
>>>>> the PMC in favor (but
>>>>>> the vote is open to everybody).
>>>>>>  I push only one vote for both dependencies as for
>>>>> now I see no reason to
>>>>>> accept one and not the other.
>>>>>>  This vote will be open for 6 days as we are in
>>>>> august (If we have not
>>>>>> enough votes at the end of next wednesday will see if
>>>>> we really need to
>>>>>> extend it).
>>>>>> 
>>>>>>  The vote :
>>>>>> 
>>>>>>  [+1] I'm in favor to use as Maven core dependencies
>>>>> SISU and AETHER libraries
>>>>>> published under EPL 1.0 License and released under
>>>>> eclipse.org governance
>>>>>>  [+0] No opinion, do what you want.
>>>>>>  [-1] I'm against because .... (please elaborate)
>>>>>> 
>>>>>> Arnaud
>>>>>> 
>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> 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
>> 
>> 
>> 
>> 
> 
> 
> 
> -- 
> Olivier Lamy
> Talend : http://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
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Olivier Lamy <ol...@apache.org>.

So I reformulate my question : 'how to be in the initial set of
committers ?" too late ?

2011/8/18 Jason van Zyl <ja...@maven.org>:
>
> On Aug 18, 2011, at 9:51 AM, Olivier Lamy wrote:
>
>> Hello,
>> Perso the license question doesn't matter a lot as long we have a
>> compatible one with ASF.
>> Have a look at tomcat 7 or the cxf distribs which contains ecj and/or
>> jetty so the Eclipse license is not a trouble for ASF products (sure
>> at least for me).
>> My main point is more regarding the governance model and the devs/pmcs
>> involved for those projects @eclipse.
>> If I look at the various proposals for aether [1] and sisu [2], the
>> initial set of committers doesn't show a diversity or a huge
>> community.
>>
>> So even if probably I won't be a huge committer, how will it be
>> possible to participate in the projects ?
>
> The process is more or less identical to Apache. The voting starts by a committer nominating someone and the process is tracked in the portal where votes are registered and tracked. Election of committers is the domain of committers and the PMC has to approve the final vote. PMC members are usually committers. As committers vote, they are posted to the mailing list in question so people can see the progress.
>
>> And probably some others Maven folks have the same question.
>>
>> Thanks,
>> --
>> Olivier Lamy
>> Talend : http://talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> [1] http://www.eclipse.org/proposals/technology.aether/
>> [2] http://www.eclipse.org/proposals/technology.sisu/
>>
>>
>> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>>> Jason, Brian, Benjamin or any other person involved,
>>>
>>> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>>>
>>> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>>>
>>> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>>>
>>> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>>>
>>> d.) How long will it take to get the first aether release done at Eclipse?
>>>
>>> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>>>
>>>> From: Anders Hammar <an...@hammar.net>
>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>> Date: Thursday, August 18, 2011, 10:56 AM
>>>> +1 (non-binding)
>>>>
>>>> /Anders
>>>>
>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>> Hi all,
>>>>>
>>>>>  Thus as decided with Mark and Kristian I relaunch a
>>>> new vote with a better
>>>>> scope about what we are voting for.
>>>>>
>>>>>  Next releases of SISU and Aether will be released at
>>>> Eclipse.org under EPL
>>>>> 1.0 license.
>>>>>  Before they were published under ASL or dual ASL/EPL
>>>> licenses thus as
>>>>> defined in our policy [1] this change put them in
>>>> Category B [2] and we need
>>>>> to validate this change by a vote with a majority of
>>>> the PMC in favor (but
>>>>> the vote is open to everybody).
>>>>>  I push only one vote for both dependencies as for
>>>> now I see no reason to
>>>>> accept one and not the other.
>>>>>  This vote will be open for 6 days as we are in
>>>> august (If we have not
>>>>> enough votes at the end of next wednesday will see if
>>>> we really need to
>>>>> extend it).
>>>>>
>>>>>  The vote :
>>>>>
>>>>>  [+1] I'm in favor to use as Maven core dependencies
>>>> SISU and AETHER libraries
>>>>> published under EPL 1.0 License and released under
>>>> eclipse.org governance
>>>>>  [+0] No opinion, do what you want.
>>>>>  [-1] I'm against because .... (please elaborate)
>>>>>
>>>>> Arnaud
>>>>>
>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> 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
>
>
>
>



-- 
Olivier Lamy
Talend : http://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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 9:51 AM, Olivier Lamy wrote:

> Hello,
> Perso the license question doesn't matter a lot as long we have a
> compatible one with ASF.
> Have a look at tomcat 7 or the cxf distribs which contains ecj and/or
> jetty so the Eclipse license is not a trouble for ASF products (sure
> at least for me).
> My main point is more regarding the governance model and the devs/pmcs
> involved for those projects @eclipse.
> If I look at the various proposals for aether [1] and sisu [2], the
> initial set of committers doesn't show a diversity or a huge
> community.
> 
> So even if probably I won't be a huge committer, how will it be
> possible to participate in the projects ?

The process is more or less identical to Apache. The voting starts by a committer nominating someone and the process is tracked in the portal where votes are registered and tracked. Election of committers is the domain of committers and the PMC has to approve the final vote. PMC members are usually committers. As committers vote, they are posted to the mailing list in question so people can see the progress.

> And probably some others Maven folks have the same question.
> 
> Thanks,
> -- 
> Olivier Lamy
> Talend : http://talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> [1] http://www.eclipse.org/proposals/technology.aether/
> [2] http://www.eclipse.org/proposals/technology.sisu/
> 
> 
> 2011/8/18 Mark Struberg <st...@yahoo.de>:
>> Jason, Brian, Benjamin or any other person involved,
>> 
>> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>> 
>> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>> 
>> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>> 
>> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>> 
>> d.) How long will it take to get the first aether release done at Eclipse?
>> 
>> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>> 
>> txs and LieGrue,
>> strub
>> 
>> 
>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>> 
>>> From: Anders Hammar <an...@hammar.net>
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>> To: "Maven Developers List" <de...@maven.apache.org>
>>> Date: Thursday, August 18, 2011, 10:56 AM
>>> +1 (non-binding)
>>> 
>>> /Anders
>>> 
>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>> Hi all,
>>>> 
>>>>  Thus as decided with Mark and Kristian I relaunch a
>>> new vote with a better
>>>> scope about what we are voting for.
>>>> 
>>>>  Next releases of SISU and Aether will be released at
>>> Eclipse.org under EPL
>>>> 1.0 license.
>>>>  Before they were published under ASL or dual ASL/EPL
>>> licenses thus as
>>>> defined in our policy [1] this change put them in
>>> Category B [2] and we need
>>>> to validate this change by a vote with a majority of
>>> the PMC in favor (but
>>>> the vote is open to everybody).
>>>>  I push only one vote for both dependencies as for
>>> now I see no reason to
>>>> accept one and not the other.
>>>>  This vote will be open for 6 days as we are in
>>> august (If we have not
>>>> enough votes at the end of next wednesday will see if
>>> we really need to
>>>> extend it).
>>>> 
>>>>  The vote :
>>>> 
>>>>  [+1] I'm in favor to use as Maven core dependencies
>>> SISU and AETHER libraries
>>>> published under EPL 1.0 License and released under
>>> eclipse.org governance
>>>>  [+0] No opinion, do what you want.
>>>>  [-1] I'm against because .... (please elaborate)
>>>> 
>>>> Arnaud
>>>> 
>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> 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
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Olivier Lamy <ol...@apache.org>.

Hello,
Perso the license question doesn't matter a lot as long we have a
compatible one with ASF.
Have a look at tomcat 7 or the cxf distribs which contains ecj and/or
jetty so the Eclipse license is not a trouble for ASF products (sure
at least for me).
My main point is more regarding the governance model and the devs/pmcs
involved for those projects @eclipse.
If I look at the various proposals for aether [1] and sisu [2], the
initial set of committers doesn't show a diversity or a huge
community.

So even if probably I won't be a huge committer, how will it be
possible to participate in the projects ?
And probably some others Maven folks have the same question.

Thanks,
-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

[1] http://www.eclipse.org/proposals/technology.aether/
[2] http://www.eclipse.org/proposals/technology.sisu/


2011/8/18 Mark Struberg <st...@yahoo.de>:
> Jason, Brian, Benjamin or any other person involved,
>
> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>
> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>
> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>
> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>
> d.) How long will it take to get the first aether release done at Eclipse?
>
> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>
> txs and LieGrue,
> strub
>
>
> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>
>> From: Anders Hammar <an...@hammar.net>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>>
>> /Anders
>>
>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>> > Hi all,
>> >
>> >  Thus as decided with Mark and Kristian I relaunch a
>> new vote with a better
>> > scope about what we are voting for.
>> >
>> >  Next releases of SISU and Aether will be released at
>> Eclipse.org under EPL
>> > 1.0 license.
>> >  Before they were published under ASL or dual ASL/EPL
>> licenses thus as
>> > defined in our policy [1] this change put them in
>> Category B [2] and we need
>> > to validate this change by a vote with a majority of
>> the PMC in favor (but
>> > the vote is open to everybody).
>> >  I push only one vote for both dependencies as for
>> now I see no reason to
>> > accept one and not the other.
>> >  This vote will be open for 6 days as we are in
>> august (If we have not
>> > enough votes at the end of next wednesday will see if
>> we really need to
>> > extend it).
>> >
>> >  The vote :
>> >
>> >  [+1] I'm in favor to use as Maven core dependencies
>> SISU and AETHER libraries
>> > published under EPL 1.0 License and released under
>> eclipse.org governance
>> >  [+0] No opinion, do what you want.
>> >  [-1] I'm against because .... (please elaborate)
>> >
>> > Arnaud
>> >
>> > [1] http://maven.apache.org/developers/dependency-policies.html
>> > [2] http://www.apache.org/legal/resolved.html#category-b
>> >
>>
>> ---------------------------------------------------------------------
>> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Daniel Kulp <dk...@apache.org>.

On Thursday, August 18, 2011 9:17:49 AM Benson Margulies wrote:
> Mark, Can it possibly matter what the java package names are? There
> are ton's of wierd historical package names floating around the
> universe. There is no requirement for incubating Apache projects to
> move package names just for the sake of moving them. I think that
> 'sonatype' in a package name is a herring of perfect redness.

Well, I guess the real question is will they change the package names or not?  
If yes, then it MAY be better to wait a few weeks to get the version with the 
new package names.  

For example, when Jetty moved to eclipse, all the package names changed from 
org.mortbay.jetty to org.eclipse.jetty and you and I spent quite a bit of time 
updating CXF to use the new package names (amongst the other changes).   If 
we're going to move forward with Aether/Sisu, I'd prefer to start off with the 
more stable names and such so an update to Aether/Sisu is really just a drop 
in update at that time.

Dan



> 
> On Thu, Aug 18, 2011 at 8:59 AM, Mark Struberg <st...@yahoo.de> wrote:
> > Jason, Brian, Benjamin or any other person involved,
> > 
> > Before voting on this issue, I'd like to get an idea what it means for
> > us. So please allow me a few questions:
> > 
> > a.) how can appache maven committers anticipate on aether over at
> > Eclipse? What if someone (like me) likes to contribute, but wants to
> > make sure that his contributions are also possible to release
> > separately under ALv2?
> > 
> > b.) is it possible to operate aether without sisu? Pure JSR-330 and/or
> > plexus DI stuff is fine. Is there any direct guice depending code in
> > aether?
> > 
> > c.) will the package names remain com.sonatype or will they get changed
> > to org.eclipse.*? This is important for us to know. If so, we can just
> > cancel the vote and wait for this stuff to be released at Eclipse.
> > 
> > d.) How long will it take to get the first aether release done at
> > Eclipse?
> > 
> > If there is a chilly way for maven committers to get involved with that
> > stuff over at Eclipse, then this would be a big pro.
> > 
> > txs and LieGrue,
> > strub
> > 
> > --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
> >> From: Anders Hammar <an...@hammar.net>
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven
> >> core with EPL licenses - take 2 To: "Maven Developers List"
> >> <de...@maven.apache.org>
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >> 
> >> /Anders
> >> 
> >> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> >> > Hi all,
> >> > 
> >> >  Thus as decided with Mark and Kristian I relaunch a
> >> 
> >> new vote with a better
> >> 
> >> > scope about what we are voting for.
> >> > 
> >> >  Next releases of SISU and Aether will be released at
> >> 
> >> Eclipse.org under EPL
> >> 
> >> > 1.0 license.
> >> >  Before they were published under ASL or dual ASL/EPL
> >> 
> >> licenses thus as
> >> 
> >> > defined in our policy [1] this change put them in
> >> 
> >> Category B [2] and we need
> >> 
> >> > to validate this change by a vote with a majority of
> >> 
> >> the PMC in favor (but
> >> 
> >> > the vote is open to everybody).
> >> >  I push only one vote for both dependencies as for
> >> 
> >> now I see no reason to
> >> 
> >> > accept one and not the other.
> >> >  This vote will be open for 6 days as we are in
> >> 
> >> august (If we have not
> >> 
> >> > enough votes at the end of next wednesday will see if
> >> 
> >> we really need to
> >> 
> >> > extend it).
> >> > 
> >> >  The vote :
> >> > 
> >> >  [+1] I'm in favor to use as Maven core dependencies
> >> 
> >> SISU and AETHER libraries
> >> 
> >> > published under EPL 1.0 License and released under
> >> 
> >> eclipse.org governance
> >> 
> >> >  [+0] No opinion, do what you want.
> >> >  [-1] I'm against because .... (please elaborate)
> >> > 
> >> > Arnaud
> >> > 
> >> > [1] http://maven.apache.org/developers/dependency-policies.html
> >> > [2] http://www.apache.org/legal/resolved.html#category-b
> >> 
> >> ---------------------------------------------------------------------
> >> 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
-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

Benson, I think you got this completely wrong. 

I don't care about the eclipse policies. But IF eclipse says they like to change the package names, then WE have to change all our aether imports and retest all that stuff...

If it stays com.sonatype, then otoh we don't need to do much...

LieGrue,
strub

--- On Thu, 8/18/11, Benson Margulies <bi...@gmail.com> wrote:

> From: Benson Margulies <bi...@gmail.com>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 1:17 PM
> Mark, Can it possibly matter what the
> java package names are? There
> are ton's of wierd historical package names floating around
> the
> universe. There is no requirement for incubating Apache
> projects to
> move package names just for the sake of moving them. I
> think that
> 'sonatype' in a package name is a herring of perfect
> redness.
> 
> 
> On Thu, Aug 18, 2011 at 8:59 AM, Mark Struberg <st...@yahoo.de>
> wrote:
> > Jason, Brian, Benjamin or any other person involved,
> >
> > Before voting on this issue, I'd like to get an idea
> what it means for us. So please allow me a few questions:
> >
> > a.) how can appache maven committers anticipate on
> aether over at Eclipse? What if someone (like me) likes to
> contribute, but wants to make sure that his contributions
> are also possible to release separately under ALv2?
> >
> > b.) is it possible to operate aether without sisu?
> Pure JSR-330 and/or plexus DI stuff is fine. Is there any
> direct guice depending code in aether?
> >
> > c.) will the package names remain com.sonatype or will
> they get changed to org.eclipse.*? This is important for us
> to know. If so, we can just cancel the vote and wait for
> this stuff to be released at Eclipse.
> >
> > d.) How long will it take to get the first aether
> release done at Eclipse?
> >
> > If there is a chilly way for maven committers to get
> involved with that stuff over at Eclipse, then this would be
> a big pro.
> >
> > txs and LieGrue,
> > strub
> >
> >
> > --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
> wrote:
> >
> >> From: Anders Hammar <an...@hammar.net>
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as
> dependencies of maven core with EPL licenses - take 2
> >> To: "Maven Developers List" <de...@maven.apache.org>
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >>
> >> /Anders
> >>
> >> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> >> > Hi all,
> >> >
> >> >  Thus as decided with Mark and Kristian I
> relaunch a
> >> new vote with a better
> >> > scope about what we are voting for.
> >> >
> >> >  Next releases of SISU and Aether will be
> released at
> >> Eclipse.org under EPL
> >> > 1.0 license.
> >> >  Before they were published under ASL or
> dual ASL/EPL
> >> licenses thus as
> >> > defined in our policy [1] this change put
> them in
> >> Category B [2] and we need
> >> > to validate this change by a vote with a
> majority of
> >> the PMC in favor (but
> >> > the vote is open to everybody).
> >> >  I push only one vote for both dependencies
> as for
> >> now I see no reason to
> >> > accept one and not the other.
> >> >  This vote will be open for 6 days as we are
> in
> >> august (If we have not
> >> > enough votes at the end of next wednesday
> will see if
> >> we really need to
> >> > extend it).
> >> >
> >> >  The vote :
> >> >
> >> >  [+1] I'm in favor to use as Maven core
> dependencies
> >> SISU and AETHER libraries
> >> > published under EPL 1.0 License and released
> under
> >> eclipse.org governance
> >> >  [+0] No opinion, do what you want.
> >> >  [-1] I'm against because .... (please
> elaborate)
> >> >
> >> > Arnaud
> >> >
> >> > [1] http://maven.apache.org/developers/dependency-policies.html
> >> > [2] http://www.apache.org/legal/resolved.html#category-b
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Benson Margulies <bi...@gmail.com>.

Mark, Can it possibly matter what the java package names are? There
are ton's of wierd historical package names floating around the
universe. There is no requirement for incubating Apache projects to
move package names just for the sake of moving them. I think that
'sonatype' in a package name is a herring of perfect redness.


On Thu, Aug 18, 2011 at 8:59 AM, Mark Struberg <st...@yahoo.de> wrote:
> Jason, Brian, Benjamin or any other person involved,
>
> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
>
> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
>
> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
>
> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>
> d.) How long will it take to get the first aether release done at Eclipse?
>
> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
>
> txs and LieGrue,
> strub
>
>
> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
>
>> From: Anders Hammar <an...@hammar.net>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>>
>> /Anders
>>
>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>> > Hi all,
>> >
>> >  Thus as decided with Mark and Kristian I relaunch a
>> new vote with a better
>> > scope about what we are voting for.
>> >
>> >  Next releases of SISU and Aether will be released at
>> Eclipse.org under EPL
>> > 1.0 license.
>> >  Before they were published under ASL or dual ASL/EPL
>> licenses thus as
>> > defined in our policy [1] this change put them in
>> Category B [2] and we need
>> > to validate this change by a vote with a majority of
>> the PMC in favor (but
>> > the vote is open to everybody).
>> >  I push only one vote for both dependencies as for
>> now I see no reason to
>> > accept one and not the other.
>> >  This vote will be open for 6 days as we are in
>> august (If we have not
>> > enough votes at the end of next wednesday will see if
>> we really need to
>> > extend it).
>> >
>> >  The vote :
>> >
>> >  [+1] I'm in favor to use as Maven core dependencies
>> SISU and AETHER libraries
>> > published under EPL 1.0 License and released under
>> eclipse.org governance
>> >  [+0] No opinion, do what you want.
>> >  [-1] I'm against because .... (please elaborate)
>> >
>> > Arnaud
>> >
>> > [1] http://maven.apache.org/developers/dependency-policies.html
>> > [2] http://www.apache.org/legal/resolved.html#category-b
>> >
>>
>> ---------------------------------------------------------------------
>> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 10:06 AM, Kristian Rosenvold wrote:

>> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
>> 
> Changing that should be like 20 minutes work, as long as they only
> change com.sonatype to org.eclipse and nothing else in the process. It's
> about 2 keypresses in idea to do maven core.
> 

That would not be the case, there are quite a few non-Maven consumers of Aether. It's something we can decide, I generally don't like breaking binary compatibility but it might be early enough to do so.

> Kristian
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

 -- Eric Hoffer, Reflections on the Human Condition

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

Oki Kristian, and you will go on and do all the release cascade stuff - thanks mate :D

Nah seriously, it will be a bit more work. The groupId will change too most probably, and we would need to dig into maven and mojo plugins too ...


@Jason: 
The difference between 'Hudson' and 'Sonatype' is huge. Hudson was a (questionable) Oracle trademark and they donated it to Eclipse. Guess you don't want to do this with 'Sonatype' :)


LieGrue,
strub

--- On Thu, 8/18/11, Kristian Rosenvold <kr...@gmail.com> wrote:

> From: Kristian Rosenvold <kr...@gmail.com>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 2:06 PM
> > c.) will the package names
> remain com.sonatype or will they get changed to
> org.eclipse.*? This is important for us to know. If so, we
> can just cancel the vote and wait for this stuff to be
> released at Eclipse.
> > 
> Changing that should be like 20 minutes work, as long as
> they only
> change com.sonatype to org.eclipse and nothing else in the
> process. It's
> about 2 keypresses in idea to do maven core.
> 
> Kristian
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Kristian Rosenvold <kr...@gmail.com>.

> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
> 
Changing that should be like 20 minutes work, as long as they only
change com.sonatype to org.eclipse and nothing else in the process. It's
about 2 keypresses in idea to do maven core.

Kristian






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

No worries mate, no reason to excuse :)

The question was good, I just didn't think about any ideological at all so I was a bit surprised as well :) 
I just try to figure out what aether@eclipse means to the Maven project in practice. What do we need to change over here, how to cope with changes we need to apply in aether to make future Maven needs possible, etc...

LieGrue,
strub

--- On Thu, 8/18/11, Benson Margulies <bi...@gmail.com> wrote:

> From: Benson Margulies <bi...@gmail.com>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 1:27 PM
> Sorry, all, I didn't realize you were
> asking about the *practical*
> issues with the package names. I perceived a nonexistent
> ideological
> dispute.
> 
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Benson Margulies <bi...@gmail.com>.

Sorry, all, I didn't realize you were asking about the *practical*
issues with the package names. I perceived a nonexistent ideological
dispute.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 9:41 AM, Arnaud Héritier wrote:

>> 
>> 
>> 
>>> Otoh it would require us to go through maven-core and all plugins to
>> change imports. So either way is ok, but we need to know the direction.
>>> 
>> 
>> I wouldn't make client code have to change anything.
>> 
> 
> For any thirdparty lib we are using in core, on Maven APIs
> (org.apache.maven) should be exposed and used by plugins and extensions...
> (or we have a problem ... IMHO)
> 

This has effectively been done with Aether, all but very few of the existing Artifact/Repository APIs were broken or removed. That said I think what's more important is that anything you choose to expose has a stable API. Aether is already available to plugin developers, it allows some very powerful features, and I personally don't feel like writing a huge set of wrappers. If someone else wants to that's fine, but the notion as someone suggested to cut off Aether's availability by blocking its visibility at the classloader level serves no real purpose. Even though we had the artifact/repository API people still found the need to use Wagon directly. I don't think blocking its use from the perspective of  a "purity of API" argument is a valid one.

> Arnaud

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole

 -- Christopher Alexander, A Pattern Language

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

>
>
>
> > Otoh it would require us to go through maven-core and all plugins to
> change imports. So either way is ok, but we need to know the direction.
> >
>
> I wouldn't make client code have to change anything.
>

For any thirdparty lib we are using in core, on Maven APIs
(org.apache.maven) should be exposed and used by plugins and extensions...
(or we have a problem ... IMHO)

Arnaud

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 9:38 AM, Jason van Zyl wrote:

> 
> On Aug 18, 2011, at 9:32 AM, Mark Struberg wrote:
> 
>> Hi Jason,
>> 
>> Txs 4 the answers.
>> 
>> Changing the package names would of course require some more work on both sides, but at the end it might even be better for the long run. For example using the sonatype name in a package might later cause your company troubles/discussions with Trademarks and stuff. 
>> 
> 
> Not an issue in package names. An exception was granted for the package namespace related to public facing APIs, so I'll ask today if the same reasoning can be applied to Aether. It's not hard to put adapters into place so that client code doesn't need to change, which is how it should be done, it's just tedious and not much fun.
> 

Sorry, here I meant to say an exception was granted for Hudson in this regard.

>> Otoh it would require us to go through maven-core and all plugins to change imports. So either way is ok, but we need to know the direction.
>> 
> 
> I wouldn't make client code have to change anything.
> 
>> LieGrue,
>> strub
>> 
>> --- On Thu, 8/18/11, Jason van Zyl <ja...@maven.org> wrote:
>> 
>>> From: Jason van Zyl <ja...@maven.org>
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>>> To: "Maven Developers List" <de...@maven.apache.org>
>>> Date: Thursday, August 18, 2011, 1:24 PM
>>> 
>>> On Aug 18, 2011, at 8:59 AM, Mark Struberg wrote:
>>> 
>>>> Jason, Brian, Benjamin or any other person involved,
>>>> 
>>>> Before voting on this issue, I'd like to get an idea
>>> what it means for us. So please allow me a few questions:
>>>> 
>>>> a.) how can appache maven committers anticipate on
>>> aether over at Eclipse? What if someone (like me) likes to
>>> contribute, but wants to make sure that his contributions
>>> are also possible to release separately under ALv2?
>>>> 
>>> 
>>> The copyright of the code entering Eclipse always remains
>>> that of the author. The code that is submitted to Eclipse
>>> must be under the EPL license, but as the copyright owner
>>> you can make your contributions available under any license
>>> you choose.
>>> 
>>>> b.) is it possible to operate aether without sisu?
>>> Pure JSR-330 and/or plexus DI stuff is fine. Is there any
>>> direct guice depending code in aether?
>>>> 
>>> 
>>> Aether requires no DI.
>>> 
>>>> c.) will the package names remain com.sonatype or will
>>> they get changed to org.eclipse.*? This is important for us
>>> to know. If so, we can just cancel the vote and wait for
>>> this stuff to be released at Eclipse.
>>>> 
>>> 
>>> I'm going to ask for an exception. I don't want to change
>>> the package names if I don't have to. It's just a pain in
>>> the ass.
>>> 
>>>> d.) How long will it take to get the first aether
>>> release done at Eclipse?
>>>> 
>>> 
>>> The creation review ends next Wednesday, it will take
>>> another week to provision the project. At that point if we
>>> don't have to change the package names we can do a release.
>>> If we have to change the package names then that will likely
>>> add at least another two weeks for proper testing.
>>> 
>>>> If there is a chilly way for maven committers to get
>>> involved with that stuff over at Eclipse, then this would be
>>> a big pro.
>>>> 
>>> 
>>> Sorry, I don't grok that sentence.
>>> 
>>>> txs and LieGrue,
>>>> strub
>>>> 
>>>> 
>>>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
>>> wrote:
>>>> 
>>>>> From: Anders Hammar <an...@hammar.net>
>>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as
>>> dependencies of maven core with EPL licenses - take 2
>>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>>> Date: Thursday, August 18, 2011, 10:56 AM
>>>>> +1 (non-binding)
>>>>> 
>>>>> /Anders
>>>>> 
>>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>>> Hi all,
>>>>>> 
>>>>>>  Thus as decided with Mark and Kristian I
>>> relaunch a
>>>>> new vote with a better
>>>>>> scope about what we are voting for.
>>>>>> 
>>>>>>  Next releases of SISU and Aether will be
>>> released at
>>>>> Eclipse.org under EPL
>>>>>> 1.0 license.
>>>>>>  Before they were published under ASL or
>>> dual ASL/EPL
>>>>> licenses thus as
>>>>>> defined in our policy [1] this change put them
>>> in
>>>>> Category B [2] and we need
>>>>>> to validate this change by a vote with a
>>> majority of
>>>>> the PMC in favor (but
>>>>>> the vote is open to everybody).
>>>>>>  I push only one vote for both
>>> dependencies as for
>>>>> now I see no reason to
>>>>>> accept one and not the other.
>>>>>>  This vote will be open for 6 days as we
>>> are in
>>>>> august (If we have not
>>>>>> enough votes at the end of next wednesday will
>>> see if
>>>>> we really need to
>>>>>> extend it).
>>>>>> 
>>>>>>  The vote :
>>>>>> 
>>>>>>  [+1] I'm in favor to use as Maven core
>>> dependencies
>>>>> SISU and AETHER libraries
>>>>>> published under EPL 1.0 License and released
>>> under
>>>>> eclipse.org governance
>>>>>>  [+0] No opinion, do what you want.
>>>>>>  [-1] I'm against because .... (please
>>> elaborate)
>>>>>> 
>>>>>> Arnaud
>>>>>> 
>>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>>> 
>>>>> 
>>>>> 
>>> ---------------------------------------------------------------------
>>>>> 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
>>>> 
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> 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
>>> 
>>> 
>>> 
>>> 
>> 
>> ---------------------------------------------------------------------
>> 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,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> 
> 
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We know what we are, but know not what we may be.

  -- Shakespeare

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 9:32 AM, Mark Struberg wrote:

> Hi Jason,
> 
> Txs 4 the answers.
> 
> Changing the package names would of course require some more work on both sides, but at the end it might even be better for the long run. For example using the sonatype name in a package might later cause your company troubles/discussions with Trademarks and stuff. 
> 

Not an issue in package names. An exception was granted for the package namespace related to public facing APIs, so I'll ask today if the same reasoning can be applied to Aether. It's not hard to put adapters into place so that client code doesn't need to change, which is how it should be done, it's just tedious and not much fun.

> Otoh it would require us to go through maven-core and all plugins to change imports. So either way is ok, but we need to know the direction.
> 

I wouldn't make client code have to change anything.

> LieGrue,
> strub
> 
> --- On Thu, 8/18/11, Jason van Zyl <ja...@maven.org> wrote:
> 
>> From: Jason van Zyl <ja...@maven.org>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 1:24 PM
>> 
>> On Aug 18, 2011, at 8:59 AM, Mark Struberg wrote:
>> 
>>> Jason, Brian, Benjamin or any other person involved,
>>> 
>>> Before voting on this issue, I'd like to get an idea
>> what it means for us. So please allow me a few questions:
>>> 
>>> a.) how can appache maven committers anticipate on
>> aether over at Eclipse? What if someone (like me) likes to
>> contribute, but wants to make sure that his contributions
>> are also possible to release separately under ALv2?
>>> 
>> 
>> The copyright of the code entering Eclipse always remains
>> that of the author. The code that is submitted to Eclipse
>> must be under the EPL license, but as the copyright owner
>> you can make your contributions available under any license
>> you choose.
>> 
>>> b.) is it possible to operate aether without sisu?
>> Pure JSR-330 and/or plexus DI stuff is fine. Is there any
>> direct guice depending code in aether?
>>> 
>> 
>> Aether requires no DI.
>> 
>>> c.) will the package names remain com.sonatype or will
>> they get changed to org.eclipse.*? This is important for us
>> to know. If so, we can just cancel the vote and wait for
>> this stuff to be released at Eclipse.
>>> 
>> 
>> I'm going to ask for an exception. I don't want to change
>> the package names if I don't have to. It's just a pain in
>> the ass.
>> 
>>> d.) How long will it take to get the first aether
>> release done at Eclipse?
>>> 
>> 
>> The creation review ends next Wednesday, it will take
>> another week to provision the project. At that point if we
>> don't have to change the package names we can do a release.
>> If we have to change the package names then that will likely
>> add at least another two weeks for proper testing.
>> 
>>> If there is a chilly way for maven committers to get
>> involved with that stuff over at Eclipse, then this would be
>> a big pro.
>>> 
>> 
>> Sorry, I don't grok that sentence.
>> 
>>> txs and LieGrue,
>>> strub
>>> 
>>> 
>>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
>> wrote:
>>> 
>>>> From: Anders Hammar <an...@hammar.net>
>>>> Subject: Re: [VOTE] Usage of Aether and Sisu as
>> dependencies of maven core with EPL licenses - take 2
>>>> To: "Maven Developers List" <de...@maven.apache.org>
>>>> Date: Thursday, August 18, 2011, 10:56 AM
>>>> +1 (non-binding)
>>>> 
>>>> /Anders
>>>> 
>>>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>>>> Hi all,
>>>>> 
>>>>>   Thus as decided with Mark and Kristian I
>> relaunch a
>>>> new vote with a better
>>>>> scope about what we are voting for.
>>>>> 
>>>>>   Next releases of SISU and Aether will be
>> released at
>>>> Eclipse.org under EPL
>>>>> 1.0 license.
>>>>>   Before they were published under ASL or
>> dual ASL/EPL
>>>> licenses thus as
>>>>> defined in our policy [1] this change put them
>> in
>>>> Category B [2] and we need
>>>>> to validate this change by a vote with a
>> majority of
>>>> the PMC in favor (but
>>>>> the vote is open to everybody).
>>>>>   I push only one vote for both
>> dependencies as for
>>>> now I see no reason to
>>>>> accept one and not the other.
>>>>>   This vote will be open for 6 days as we
>> are in
>>>> august (If we have not
>>>>> enough votes at the end of next wednesday will
>> see if
>>>> we really need to
>>>>> extend it).
>>>>> 
>>>>>   The vote :
>>>>> 
>>>>>   [+1] I'm in favor to use as Maven core
>> dependencies
>>>> SISU and AETHER libraries
>>>>> published under EPL 1.0 License and released
>> under
>>>> eclipse.org governance
>>>>>   [+0] No opinion, do what you want.
>>>>>   [-1] I'm against because .... (please
>> elaborate)
>>>>> 
>>>>> Arnaud
>>>>> 
>>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>> 
>>>> 
>>>> 
>> ---------------------------------------------------------------------
>>>> 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
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> 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
>> 
>> 
>> 
>> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

Hi Jason,

Txs 4 the answers.

Changing the package names would of course require some more work on both sides, but at the end it might even be better for the long run. For example using the sonatype name in a package might later cause your company troubles/discussions with Trademarks and stuff. 

Otoh it would require us to go through maven-core and all plugins to change imports. So either way is ok, but we need to know the direction.

LieGrue,
strub

--- On Thu, 8/18/11, Jason van Zyl <ja...@maven.org> wrote:

> From: Jason van Zyl <ja...@maven.org>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 1:24 PM
> 
> On Aug 18, 2011, at 8:59 AM, Mark Struberg wrote:
> 
> > Jason, Brian, Benjamin or any other person involved,
> > 
> > Before voting on this issue, I'd like to get an idea
> what it means for us. So please allow me a few questions:
> > 
> > a.) how can appache maven committers anticipate on
> aether over at Eclipse? What if someone (like me) likes to
> contribute, but wants to make sure that his contributions
> are also possible to release separately under ALv2?
> > 
> 
> The copyright of the code entering Eclipse always remains
> that of the author. The code that is submitted to Eclipse
> must be under the EPL license, but as the copyright owner
> you can make your contributions available under any license
> you choose.
> 
> > b.) is it possible to operate aether without sisu?
> Pure JSR-330 and/or plexus DI stuff is fine. Is there any
> direct guice depending code in aether?
> > 
> 
> Aether requires no DI.
> 
> > c.) will the package names remain com.sonatype or will
> they get changed to org.eclipse.*? This is important for us
> to know. If so, we can just cancel the vote and wait for
> this stuff to be released at Eclipse.
> > 
> 
> I'm going to ask for an exception. I don't want to change
> the package names if I don't have to. It's just a pain in
> the ass.
> 
> > d.) How long will it take to get the first aether
> release done at Eclipse?
> > 
> 
> The creation review ends next Wednesday, it will take
> another week to provision the project. At that point if we
> don't have to change the package names we can do a release.
> If we have to change the package names then that will likely
> add at least another two weeks for proper testing.
> 
> > If there is a chilly way for maven committers to get
> involved with that stuff over at Eclipse, then this would be
> a big pro.
> > 
> 
> Sorry, I don't grok that sentence.
> 
> > txs and LieGrue,
> > strub
> > 
> > 
> > --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
> wrote:
> > 
> >> From: Anders Hammar <an...@hammar.net>
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as
> dependencies of maven core with EPL licenses - take 2
> >> To: "Maven Developers List" <de...@maven.apache.org>
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >> 
> >> /Anders
> >> 
> >> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> >>> Hi all,
> >>> 
> >>>  Thus as decided with Mark and Kristian I
> relaunch a
> >> new vote with a better
> >>> scope about what we are voting for.
> >>> 
> >>>  Next releases of SISU and Aether will be
> released at
> >> Eclipse.org under EPL
> >>> 1.0 license.
> >>>  Before they were published under ASL or
> dual ASL/EPL
> >> licenses thus as
> >>> defined in our policy [1] this change put them
> in
> >> Category B [2] and we need
> >>> to validate this change by a vote with a
> majority of
> >> the PMC in favor (but
> >>> the vote is open to everybody).
> >>>  I push only one vote for both
> dependencies as for
> >> now I see no reason to
> >>> accept one and not the other.
> >>>  This vote will be open for 6 days as we
> are in
> >> august (If we have not
> >>> enough votes at the end of next wednesday will
> see if
> >> we really need to
> >>> extend it).
> >>> 
> >>>  The vote :
> >>> 
> >>>  [+1] I'm in favor to use as Maven core
> dependencies
> >> SISU and AETHER libraries
> >>> published under EPL 1.0 License and released
> under
> >> eclipse.org governance
> >>>  [+0] No opinion, do what you want.
> >>>  [-1] I'm against because .... (please
> elaborate)
> >>> 
> >>> Arnaud
> >>> 
> >>> [1] http://maven.apache.org/developers/dependency-policies.html
> >>> [2] http://www.apache.org/legal/resolved.html#category-b
> >>> 
> >> 
> >>
> ---------------------------------------------------------------------
> >> 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
> > 
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> 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
> 
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 18, 2011, at 8:59 AM, Mark Struberg wrote:

> Jason, Brian, Benjamin or any other person involved,
> 
> Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:
> 
> a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?
> 

The copyright of the code entering Eclipse always remains that of the author. The code that is submitted to Eclipse must be under the EPL license, but as the copyright owner you can make your contributions available under any license you choose.

> b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?
> 

Aether requires no DI.

> c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.
> 

I'm going to ask for an exception. I don't want to change the package names if I don't have to. It's just a pain in the ass.

> d.) How long will it take to get the first aether release done at Eclipse?
> 

The creation review ends next Wednesday, it will take another week to provision the project. At that point if we don't have to change the package names we can do a release. If we have to change the package names then that will likely add at least another two weeks for proper testing.

> If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.
> 

Sorry, I don't grok that sentence.

> txs and LieGrue,
> strub
> 
> 
> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:
> 
>> From: Anders Hammar <an...@hammar.net>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>> 
>> /Anders
>> 
>> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>>> Hi all,
>>> 
>>>  Thus as decided with Mark and Kristian I relaunch a
>> new vote with a better
>>> scope about what we are voting for.
>>> 
>>>  Next releases of SISU and Aether will be released at
>> Eclipse.org under EPL
>>> 1.0 license.
>>>  Before they were published under ASL or dual ASL/EPL
>> licenses thus as
>>> defined in our policy [1] this change put them in
>> Category B [2] and we need
>>> to validate this change by a vote with a majority of
>> the PMC in favor (but
>>> the vote is open to everybody).
>>>  I push only one vote for both dependencies as for
>> now I see no reason to
>>> accept one and not the other.
>>>  This vote will be open for 6 days as we are in
>> august (If we have not
>>> enough votes at the end of next wednesday will see if
>> we really need to
>>> extend it).
>>> 
>>>  The vote :
>>> 
>>>  [+1] I'm in favor to use as Maven core dependencies
>> SISU and AETHER libraries
>>> published under EPL 1.0 License and released under
>> eclipse.org governance
>>>  [+0] No opinion, do what you want.
>>>  [-1] I'm against because .... (please elaborate)
>>> 
>>> Arnaud
>>> 
>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>> 
>> 
>> ---------------------------------------------------------------------
>> 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
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@apache.org>.

+1 (binding)

-Stephen

On 19 August 2011 10:32, Mark Struberg <st...@yahoo.de> wrote:
> +1 for the upgrade in principal. It's not the best solution, but the best solution quickly available.
>
> Maven should nontheless introduce an own simplified SPI for that stuff and use it in maven-core. All aether stuff should really only be handled in the maven-aether-provider and we should change this part to be pluggable.
>
> LieGrue,
> strub
>
>
> --- On Thu, 8/18/11, Mark Struberg <st...@yahoo.de> wrote:
>
>> From: Mark Struberg <st...@yahoo.de>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 12:59 PM
>> Jason, Brian, Benjamin or any other
>> person involved,
>>
>> Before voting on this issue, I'd like to get an idea what
>> it means for us. So please allow me a few questions:
>>
>> a.) how can appache maven committers anticipate on aether
>> over at Eclipse? What if someone (like me) likes to
>> contribute, but wants to make sure that his contributions
>> are also possible to release separately under ALv2?
>>
>> b.) is it possible to operate aether without sisu? Pure
>> JSR-330 and/or plexus DI stuff is fine. Is there any direct
>> guice depending code in aether?
>>
>> c.) will the package names remain com.sonatype or will they
>> get changed to org.eclipse.*? This is important for us to
>> know. If so, we can just cancel the vote and wait for this
>> stuff to be released at Eclipse.
>>
>> d.) How long will it take to get the first aether release
>> done at Eclipse?
>>
>> If there is a chilly way for maven committers to get
>> involved with that stuff over at Eclipse, then this would be
>> a big pro.
>>
>> txs and LieGrue,
>> strub
>>
>>
>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
>> wrote:
>>
>> > From: Anders Hammar <an...@hammar.net>
>> > Subject: Re: [VOTE] Usage of Aether and Sisu as
>> dependencies of maven core with EPL licenses - take 2
>> > To: "Maven Developers List" <de...@maven.apache.org>
>> > Date: Thursday, August 18, 2011, 10:56 AM
>> > +1 (non-binding)
>> >
>> > /Anders
>> >
>> > 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>> > > Hi all,
>> > >
>> > >  Thus as decided with Mark and Kristian I
>> relaunch a
>> > new vote with a better
>> > > scope about what we are voting for.
>> > >
>> > >  Next releases of SISU and Aether will be
>> released at
>> > Eclipse.org under EPL
>> > > 1.0 license.
>> > >  Before they were published under ASL or dual
>> ASL/EPL
>> > licenses thus as
>> > > defined in our policy [1] this change put them
>> in
>> > Category B [2] and we need
>> > > to validate this change by a vote with a majority
>> of
>> > the PMC in favor (but
>> > > the vote is open to everybody).
>> > >  I push only one vote for both dependencies as
>> for
>> > now I see no reason to
>> > > accept one and not the other.
>> > >  This vote will be open for 6 days as we are in
>> > august (If we have not
>> > > enough votes at the end of next wednesday will
>> see if
>> > we really need to
>> > > extend it).
>> > >
>> > >  The vote :
>> > >
>> > >  [+1] I'm in favor to use as Maven core
>> dependencies
>> > SISU and AETHER libraries
>> > > published under EPL 1.0 License and released
>> under
>> > eclipse.org governance
>> > >  [+0] No opinion, do what you want.
>> > >  [-1] I'm against because .... (please
>> elaborate)
>> > >
>> > > Arnaud
>> > >
>> > > [1] http://maven.apache.org/developers/dependency-policies.html
>> > > [2] http://www.apache.org/legal/resolved.html#category-b
>> > >
>> >
>> >
>> ---------------------------------------------------------------------
>> > 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Derricutt <ma...@talios.com>.

+1 Would vote again ;-)

Glad to see things can once again move on.

I look forward to seeing this release go out.

Maveno!
Mark

On 29/08/2011, at 12:10 AM, Arnaud Héritier wrote:

> Thus with Olivier and Stéphane votes we have the majority (12/22) of PMCs
> voting in favor to use as Maven core dependencies SISU and AETHER
> libraries published under EPL 1.0 License and released under eclipse.org
> governance.

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

Thus with Olivier and Stéphane votes we have the majority (12/22) of PMCs
voting in favor to use as Maven core dependencies SISU and AETHER
libraries published under EPL 1.0 License and released under eclipse.org
 governance.

Voters were :
Arnaud,Kristian,Ralph,Hervé,Dennis,Wayne,John,Stephen,Barrie,Mark S,Olivier,
Stéphane

We can now go forward and prepare a new release as soon as these libraries
will be published from eclipse under these terms.

Cheers,

Arnaud

On Sat, Aug 27, 2011 at 2:05 PM, Olivier Lamy <ol...@apache.org> wrote:

> +1 for the vote and for the mark proposal (not have anymore external
> stuff part of our public api).
>
> 2011/8/19 Mark Struberg <st...@yahoo.de>:
> > +1 for the upgrade in principal. It's not the best solution, but the best
> solution quickly available.
> >
> > Maven should nontheless introduce an own simplified SPI for that stuff
> and use it in maven-core. All aether stuff should really only be handled in
> the maven-aether-provider and we should change this part to be pluggable.
> >
> > LieGrue,
> > strub
> >
> >
> > --- On Thu, 8/18/11, Mark Struberg <st...@yahoo.de> wrote:
> >
> >> From: Mark Struberg <st...@yahoo.de>
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven
> core with EPL licenses - take 2
> >> To: "Maven Developers List" <de...@maven.apache.org>
> >> Date: Thursday, August 18, 2011, 12:59 PM
> >> Jason, Brian, Benjamin or any other
> >> person involved,
> >>
> >> Before voting on this issue, I'd like to get an idea what
> >> it means for us. So please allow me a few questions:
> >>
> >> a.) how can appache maven committers anticipate on aether
> >> over at Eclipse? What if someone (like me) likes to
> >> contribute, but wants to make sure that his contributions
> >> are also possible to release separately under ALv2?
> >>
> >> b.) is it possible to operate aether without sisu? Pure
> >> JSR-330 and/or plexus DI stuff is fine. Is there any direct
> >> guice depending code in aether?
> >>
> >> c.) will the package names remain com.sonatype or will they
> >> get changed to org.eclipse.*? This is important for us to
> >> know. If so, we can just cancel the vote and wait for this
> >> stuff to be released at Eclipse.
> >>
> >> d.) How long will it take to get the first aether release
> >> done at Eclipse?
> >>
> >> If there is a chilly way for maven committers to get
> >> involved with that stuff over at Eclipse, then this would be
> >> a big pro.
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
> >> wrote:
> >>
> >> > From: Anders Hammar <an...@hammar.net>
> >> > Subject: Re: [VOTE] Usage of Aether and Sisu as
> >> dependencies of maven core with EPL licenses - take 2
> >> > To: "Maven Developers List" <de...@maven.apache.org>
> >> > Date: Thursday, August 18, 2011, 10:56 AM
> >> > +1 (non-binding)
> >> >
> >> > /Anders
> >> >
> >> > 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> >> > > Hi all,
> >> > >
> >> > >  Thus as decided with Mark and Kristian I
> >> relaunch a
> >> > new vote with a better
> >> > > scope about what we are voting for.
> >> > >
> >> > >  Next releases of SISU and Aether will be
> >> released at
> >> > Eclipse.org under EPL
> >> > > 1.0 license.
> >> > >  Before they were published under ASL or dual
> >> ASL/EPL
> >> > licenses thus as
> >> > > defined in our policy [1] this change put them
> >> in
> >> > Category B [2] and we need
> >> > > to validate this change by a vote with a majority
> >> of
> >> > the PMC in favor (but
> >> > > the vote is open to everybody).
> >> > >  I push only one vote for both dependencies as
> >> for
> >> > now I see no reason to
> >> > > accept one and not the other.
> >> > >  This vote will be open for 6 days as we are in
> >> > august (If we have not
> >> > > enough votes at the end of next wednesday will
> >> see if
> >> > we really need to
> >> > > extend it).
> >> > >
> >> > >  The vote :
> >> > >
> >> > >  [+1] I'm in favor to use as Maven core
> >> dependencies
> >> > SISU and AETHER libraries
> >> > > published under EPL 1.0 License and released
> >> under
> >> > eclipse.org governance
> >> > >  [+0] No opinion, do what you want.
> >> > >  [-1] I'm against because .... (please
> >> elaborate)
> >> > >
> >> > > Arnaud
> >> > >
> >> > > [1] http://maven.apache.org/developers/dependency-policies.html
> >> > > [2] http://www.apache.org/legal/resolved.html#category-b
> >> > >
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > 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
> >
> >
>
>
>
> --
> Olivier Lamy
> Talend : http://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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Olivier Lamy <ol...@apache.org>.

+1 for the vote and for the mark proposal (not have anymore external
stuff part of our public api).

2011/8/19 Mark Struberg <st...@yahoo.de>:
> +1 for the upgrade in principal. It's not the best solution, but the best solution quickly available.
>
> Maven should nontheless introduce an own simplified SPI for that stuff and use it in maven-core. All aether stuff should really only be handled in the maven-aether-provider and we should change this part to be pluggable.
>
> LieGrue,
> strub
>
>
> --- On Thu, 8/18/11, Mark Struberg <st...@yahoo.de> wrote:
>
>> From: Mark Struberg <st...@yahoo.de>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 12:59 PM
>> Jason, Brian, Benjamin or any other
>> person involved,
>>
>> Before voting on this issue, I'd like to get an idea what
>> it means for us. So please allow me a few questions:
>>
>> a.) how can appache maven committers anticipate on aether
>> over at Eclipse? What if someone (like me) likes to
>> contribute, but wants to make sure that his contributions
>> are also possible to release separately under ALv2?
>>
>> b.) is it possible to operate aether without sisu? Pure
>> JSR-330 and/or plexus DI stuff is fine. Is there any direct
>> guice depending code in aether?
>>
>> c.) will the package names remain com.sonatype or will they
>> get changed to org.eclipse.*? This is important for us to
>> know. If so, we can just cancel the vote and wait for this
>> stuff to be released at Eclipse.
>>
>> d.) How long will it take to get the first aether release
>> done at Eclipse?
>>
>> If there is a chilly way for maven committers to get
>> involved with that stuff over at Eclipse, then this would be
>> a big pro.
>>
>> txs and LieGrue,
>> strub
>>
>>
>> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
>> wrote:
>>
>> > From: Anders Hammar <an...@hammar.net>
>> > Subject: Re: [VOTE] Usage of Aether and Sisu as
>> dependencies of maven core with EPL licenses - take 2
>> > To: "Maven Developers List" <de...@maven.apache.org>
>> > Date: Thursday, August 18, 2011, 10:56 AM
>> > +1 (non-binding)
>> >
>> > /Anders
>> >
>> > 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
>> > > Hi all,
>> > >
>> > >  Thus as decided with Mark and Kristian I
>> relaunch a
>> > new vote with a better
>> > > scope about what we are voting for.
>> > >
>> > >  Next releases of SISU and Aether will be
>> released at
>> > Eclipse.org under EPL
>> > > 1.0 license.
>> > >  Before they were published under ASL or dual
>> ASL/EPL
>> > licenses thus as
>> > > defined in our policy [1] this change put them
>> in
>> > Category B [2] and we need
>> > > to validate this change by a vote with a majority
>> of
>> > the PMC in favor (but
>> > > the vote is open to everybody).
>> > >  I push only one vote for both dependencies as
>> for
>> > now I see no reason to
>> > > accept one and not the other.
>> > >  This vote will be open for 6 days as we are in
>> > august (If we have not
>> > > enough votes at the end of next wednesday will
>> see if
>> > we really need to
>> > > extend it).
>> > >
>> > >  The vote :
>> > >
>> > >  [+1] I'm in favor to use as Maven core
>> dependencies
>> > SISU and AETHER libraries
>> > > published under EPL 1.0 License and released
>> under
>> > eclipse.org governance
>> > >  [+0] No opinion, do what you want.
>> > >  [-1] I'm against because .... (please
>> elaborate)
>> > >
>> > > Arnaud
>> > >
>> > > [1] http://maven.apache.org/developers/dependency-policies.html
>> > > [2] http://www.apache.org/legal/resolved.html#category-b
>> > >
>> >
>> >
>> ---------------------------------------------------------------------
>> > 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
>
>



-- 
Olivier Lamy
Talend : http://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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by John Casey <jd...@commonjava.org>.


On 8/19/11 5:32 AM, Mark Struberg wrote:
> +1 for the upgrade in principal. It's not the best solution, but the best solution quickly available.
>
> Maven should nontheless introduce an own simplified SPI for that stuff and use it in maven-core. All aether stuff should really only be handled in the maven-aether-provider and we should change this part to be pluggable.

+1, I agree completely.

>
> LieGrue,
> strub
>
>
> --- On Thu, 8/18/11, Mark Struberg<st...@yahoo.de>  wrote:
>
>> From: Mark Struberg<st...@yahoo.de>
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
>> To: "Maven Developers List"<de...@maven.apache.org>
>> Date: Thursday, August 18, 2011, 12:59 PM
>> Jason, Brian, Benjamin or any other
>> person involved,
>>
>> Before voting on this issue, I'd like to get an idea what
>> it means for us. So please allow me a few questions:
>>
>> a.) how can appache maven committers anticipate on aether
>> over at Eclipse? What if someone (like me) likes to
>> contribute, but wants to make sure that his contributions
>> are also possible to release separately under ALv2?
>>
>> b.) is it possible to operate aether without sisu? Pure
>> JSR-330 and/or plexus DI stuff is fine. Is there any direct
>> guice depending code in aether?
>>
>> c.) will the package names remain com.sonatype or will they
>> get changed to org.eclipse.*? This is important for us to
>> know. If so, we can just cancel the vote and wait for this
>> stuff to be released at Eclipse.
>>
>> d.) How long will it take to get the first aether release
>> done at Eclipse?
>>
>> If there is a chilly way for maven committers to get
>> involved with that stuff over at Eclipse, then this would be
>> a big pro.
>>
>> txs and LieGrue,
>> strub
>>
>>
>> --- On Thu, 8/18/11, Anders Hammar<an...@hammar.net>
>> wrote:
>>
>>> From: Anders Hammar<an...@hammar.net>
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as
>> dependencies of maven core with EPL licenses - take 2
>>> To: "Maven Developers List"<de...@maven.apache.org>
>>> Date: Thursday, August 18, 2011, 10:56 AM
>>> +1 (non-binding)
>>>
>>> /Anders
>>>
>>> 2011/8/18 Arnaud Héritier<ah...@gmail.com>:
>>>> Hi all,
>>>>
>>>>   Thus as decided with Mark and Kristian I
>> relaunch a
>>> new vote with a better
>>>> scope about what we are voting for.
>>>>
>>>>   Next releases of SISU and Aether will be
>> released at
>>> Eclipse.org under EPL
>>>> 1.0 license.
>>>>   Before they were published under ASL or dual
>> ASL/EPL
>>> licenses thus as
>>>> defined in our policy [1] this change put them
>> in
>>> Category B [2] and we need
>>>> to validate this change by a vote with a majority
>> of
>>> the PMC in favor (but
>>>> the vote is open to everybody).
>>>>   I push only one vote for both dependencies as
>> for
>>> now I see no reason to
>>>> accept one and not the other.
>>>>   This vote will be open for 6 days as we are in
>>> august (If we have not
>>>> enough votes at the end of next wednesday will
>> see if
>>> we really need to
>>>> extend it).
>>>>
>>>>   The vote :
>>>>
>>>>   [+1] I'm in favor to use as Maven core
>> dependencies
>>> SISU and AETHER libraries
>>>> published under EPL 1.0 License and released
>> under
>>> eclipse.org governance
>>>>   [+0] No opinion, do what you want.
>>>>   [-1] I'm against because .... (please
>> elaborate)
>>>>
>>>> Arnaud
>>>>
>>>> [1] http://maven.apache.org/developers/dependency-policies.html
>>>> [2] http://www.apache.org/legal/resolved.html#category-b
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>>> 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
>

-- 
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

+1 for the upgrade in principal. It's not the best solution, but the best solution quickly available.

Maven should nontheless introduce an own simplified SPI for that stuff and use it in maven-core. All aether stuff should really only be handled in the maven-aether-provider and we should change this part to be pluggable.

LieGrue,
strub


--- On Thu, 8/18/11, Mark Struberg <st...@yahoo.de> wrote:

> From: Mark Struberg <st...@yahoo.de>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 12:59 PM
> Jason, Brian, Benjamin or any other
> person involved,
> 
> Before voting on this issue, I'd like to get an idea what
> it means for us. So please allow me a few questions:
> 
> a.) how can appache maven committers anticipate on aether
> over at Eclipse? What if someone (like me) likes to
> contribute, but wants to make sure that his contributions
> are also possible to release separately under ALv2?
> 
> b.) is it possible to operate aether without sisu? Pure
> JSR-330 and/or plexus DI stuff is fine. Is there any direct
> guice depending code in aether?
> 
> c.) will the package names remain com.sonatype or will they
> get changed to org.eclipse.*? This is important for us to
> know. If so, we can just cancel the vote and wait for this
> stuff to be released at Eclipse.
> 
> d.) How long will it take to get the first aether release
> done at Eclipse?
> 
> If there is a chilly way for maven committers to get
> involved with that stuff over at Eclipse, then this would be
> a big pro.
> 
> txs and LieGrue,
> strub
> 
> 
> --- On Thu, 8/18/11, Anders Hammar <an...@hammar.net>
> wrote:
> 
> > From: Anders Hammar <an...@hammar.net>
> > Subject: Re: [VOTE] Usage of Aether and Sisu as
> dependencies of maven core with EPL licenses - take 2
> > To: "Maven Developers List" <de...@maven.apache.org>
> > Date: Thursday, August 18, 2011, 10:56 AM
> > +1 (non-binding)
> > 
> > /Anders
> > 
> > 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> > > Hi all,
> > >
> > >  Thus as decided with Mark and Kristian I
> relaunch a
> > new vote with a better
> > > scope about what we are voting for.
> > >
> > >  Next releases of SISU and Aether will be
> released at
> > Eclipse.org under EPL
> > > 1.0 license.
> > >  Before they were published under ASL or dual
> ASL/EPL
> > licenses thus as
> > > defined in our policy [1] this change put them
> in
> > Category B [2] and we need
> > > to validate this change by a vote with a majority
> of
> > the PMC in favor (but
> > > the vote is open to everybody).
> > >  I push only one vote for both dependencies as
> for
> > now I see no reason to
> > > accept one and not the other.
> > >  This vote will be open for 6 days as we are in
> > august (If we have not
> > > enough votes at the end of next wednesday will
> see if
> > we really need to
> > > extend it).
> > >
> > >  The vote :
> > >
> > >  [+1] I'm in favor to use as Maven core
> dependencies
> > SISU and AETHER libraries
> > > published under EPL 1.0 License and released
> under
> > eclipse.org governance
> > >  [+0] No opinion, do what you want.
> > >  [-1] I'm against because .... (please
> elaborate)
> > >
> > > Arnaud
> > >
> > > [1] http://maven.apache.org/developers/dependency-policies.html
> > > [2] http://www.apache.org/legal/resolved.html#category-b
> > >
> > 
> >
> ---------------------------------------------------------------------
> > 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Struberg <st...@yahoo.de>.

Jason, Brian, Benjamin or any other person involved,

Before voting on this issue, I'd like to get an idea what it means for us. So please allow me a few questions:

a.) how can appache maven committers anticipate on aether over at Eclipse? What if someone (like me) likes to contribute, but wants to make sure that his contributions are also possible to release separately under ALv2?

b.) is it possible to operate aether without sisu? Pure JSR-330 and/or plexus DI stuff is fine. Is there any direct guice depending code in aether?

c.) will the package names remain com.sonatype or will they get changed to org.eclipse.*? This is important for us to know. If so, we can just cancel the vote and wait for this stuff to be released at Eclipse.

d.) How long will it take to get the first aether release done at Eclipse?

If there is a chilly way for maven committers to get involved with that stuff over at Eclipse, then this would be a big pro.

txs and LieGrue,
strub

--- On Thu, 8/18/11, Anders Hammar <an...@hammar.net> wrote:

> From: Anders Hammar <an...@hammar.net>
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Thursday, August 18, 2011, 10:56 AM
> +1 (non-binding)
> 
> /Anders
> 
> 2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> > Hi all,
> >
> >  Thus as decided with Mark and Kristian I relaunch a
> new vote with a better
> > scope about what we are voting for.
> >
> >  Next releases of SISU and Aether will be released at
> Eclipse.org under EPL
> > 1.0 license.
> >  Before they were published under ASL or dual ASL/EPL
> licenses thus as
> > defined in our policy [1] this change put them in
> Category B [2] and we need
> > to validate this change by a vote with a majority of
> the PMC in favor (but
> > the vote is open to everybody).
> >  I push only one vote for both dependencies as for
> now I see no reason to
> > accept one and not the other.
> >  This vote will be open for 6 days as we are in
> august (If we have not
> > enough votes at the end of next wednesday will see if
> we really need to
> > extend it).
> >
> >  The vote :
> >
> >  [+1] I'm in favor to use as Maven core dependencies
> SISU and AETHER libraries
> > published under EPL 1.0 License and released under
> eclipse.org governance
> >  [+0] No opinion, do what you want.
> >  [-1] I'm against because .... (please elaborate)
> >
> > Arnaud
> >
> > [1] http://maven.apache.org/developers/dependency-policies.html
> > [2] http://www.apache.org/legal/resolved.html#category-b
> >
> 
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Anders Hammar <an...@hammar.net>.

+1 (non-binding)

/Anders

2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> Hi all,
>
>  Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
>
>  Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
>  Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
>  I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>  This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
>
>  The vote :
>
>  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance
>  [+0] No opinion, do what you want.
>  [-1] I'm against because .... (please elaborate)
>
> Arnaud
>
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Barrie Treloar <ba...@gmail.com>.

On Sat, Aug 20, 2011 at 5:03 AM, Wayne Fay <wa...@gmail.com> wrote:
> +1 binding for the upgrade
>
> I echo Mark's comments about SPI and maven-aether-plugin.

+1 binding

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Wayne Fay <wa...@gmail.com>.

+1 binding for the upgrade

I echo Mark's comments about SPI and maven-aether-plugin.

Wayne

2011/8/18 Arnaud Héritier <ah...@gmail.com>:
> Hi all,
>
>  Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
>
>  Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
>  Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
>  I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>  This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
>
>  The vote :
>
>  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance
>  [+0] No opinion, do what you want.
>  [-1] I'm against because .... (please elaborate)
>
> Arnaud
>
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Hervé BOUTEMY <he...@free.fr>.

+1 binding

Hervé

Le jeudi 18 août 2011, Arnaud Héritier a écrit :
> Hi all,
> 
>   Thus as decided with Mark and Kristian I relaunch a new vote with a
> better scope about what we are voting for.
> 
>   Next releases of SISU and Aether will be released at Eclipse.org under
> EPL 1.0 license.
>   Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we
> need to validate this change by a vote with a majority of the PMC in favor
> (but the vote is open to everybody).
>   I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>   This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
> 
>   The vote :
> 
>   [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
> libraries published under EPL 1.0 License and released under eclipse.org
> governance [+0] No opinion, do what you want.
>   [-1] I'm against because .... (please elaborate)
> 
> Arnaud
> 
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Manfred Moser <ma...@mosabuam.com>.

+1 (non binding)

Manfred

On Thu, August 18, 2011 7:08 am, Ralph Goers wrote:
> +1 (binding)
>
> Ralph
>
> On Aug 18, 2011, at 2:23 AM, Arnaud Héritier wrote:
>
>> Hi all,
>>
>>  Thus as decided with Mark and Kristian I relaunch a new vote with a
>> better
>> scope about what we are voting for.
>>
>>  Next releases of SISU and Aether will be released at Eclipse.org under
>> EPL
>> 1.0 license.
>>  Before they were published under ASL or dual ASL/EPL licenses thus as
>> defined in our policy [1] this change put them in Category B [2] and we
>> need
>> to validate this change by a vote with a majority of the PMC in favor
>> (but
>> the vote is open to everybody).
>>  I push only one vote for both dependencies as for now I see no reason
>> to
>> accept one and not the other.
>>  This vote will be open for 6 days as we are in august (If we have not
>> enough votes at the end of next wednesday will see if we really need to
>> extend it).
>>
>>  The vote :
>>
>>  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
>> libraries
>> published under EPL 1.0 License and released under eclipse.org
>> governance
>>  [+0] No opinion, do what you want.
>>  [-1] I'm against because .... (please elaborate)
>>
>> Arnaud
>>
>> [1] http://maven.apache.org/developers/dependency-policies.html
>> [2] http://www.apache.org/legal/resolved.html#category-b
>
>
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Ralph Goers <ra...@dslextreme.com>.

+1 (binding)

Ralph

On Aug 18, 2011, at 2:23 AM, Arnaud Héritier wrote:

> Hi all,
> 
>  Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
> 
>  Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
>  Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
>  I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
>  This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
> 
>  The vote :
> 
>  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance
>  [+0] No opinion, do what you want.
>  [-1] I'm against because .... (please elaborate)
> 
> Arnaud
> 
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stéphane Nicoll <st...@gmail.com>.

I have no particular reason not to vote at this point.

+1

Sent from my iPhone

On 27 Aug 2011, at 11:31, "Arnaud Héritier" <ah...@gmail.com> wrote:

> Hi all
>
>  Re-reading the thread I saw I forgot to vote for it. Thus it has my +1
>  For now we have 9 binding votes
> (Arnaud,Kristian,Ralph,Hervé,Dennis,Wayne,John,Stephen,Barrie) and 4 non
> binding votes (Anders,Baptiste,Manfred,Mark) in favor to use as Maven core
> dependencies SISU and AETHER libraries published under EPL 1.0 License and
> released under eclipse.org governance
>  Thus I said that the vote ended last wednesday but for now we have not
> enough binding votes as we are 22 PMCs ([1]).
>  <<< We need 3 more PMCs votes to have a majority of PMCs([2]) >>>
>
>  Otherwise, Jason and other committers on these projects on Eclipse side,
> do you have some news/delays to give to have new releases of Sisu and Aether
> under the Eclipse umbrella ?
>
>  Cheers,
>
> Arnaud
>
> [1] http://people.apache.org/committers-by-project.html#maven-pmc
> [2] http://maven.apache.org/developers/dependency-policies.html
>
> On Sat, Aug 20, 2011 at 8:33 AM, Mark Derricutt <ma...@talios.com> wrote:
>
>> +1 Non Binding.
>>
>> On 18/08/2011, at 9:23 PM, Arnaud Héritier wrote:
>>
>>> [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
>> libraries
>>> published under EPL 1.0 License and released under eclipse.orggovernance
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

I'm waiting for my CEO to sort out the CLA stuff

On 17 September 2011 17:19, Hervé BOUTEMY <he...@free.fr> wrote:
> I don't have a view on the way things happen nor how much steps are still
> pending, but FYI, things are on their way: there is now a project page [1]
> (even if empty), and CLAs are on their way: I was asked for it a week ago (i
> suppose it's the same for others) and replied a few days ago, I'm now waiting
> for my account creation.
>
> We knew it would take some time.
> I'm using this time to enhance the documentation [2]: help wanted :)
>
> Regards,
>
> Hervé
>
> [1]
> http://www.eclipse.org/projects/project_summary.php?projectid=technology.aether
>
> [2] http://maven.apache.org/ref/3.0.4-SNAPSHOT/maven-model-builder/
>
> Le samedi 17 septembre 2011, Jason van Zyl a écrit :
>> The latest is always available here:
>>
>> http://eclipse.org/proposals/technology.aether/
>>
>> We still have to refactor the package names as well which we are going to
>> do next week. We've released Aether 1.13 and Sisu 2.3.0 so we can use
>> those as well if we want. If you want to stick with the proper Eclipse
>> releases then it comes when it comes.
>>
>> I believe last week the Eclipse IT folks were installing new hardware and
>> pre-emptively taking security measures because of the security
>> vulnerability in Apache HTTPD and kernel.org hack. There is also a list of
>> projects waiting to provisioned so we're in line with everyone else. If
>> folks are in a rush use Aether 1.13 and Sisu 2.3.0, if not then just be
>> patient. Sometimes projects get provisioned the day the request goes in,
>> sometimes it's 2-3 weeks. Just depends what else is going on. It's only
>> been 8 days so far since I made the provisioning request.
>>
>> On Sep 17, 2011, at 11:25 AM, Arnaud Héritier wrote:
>> > Hi Jason (and others aether/sisu commiters)
>> >
>> > Do you have some news ( am I the only one to cross users waiting for new
>> > releases to show that our project is always alive?)
>> >
>> > Is the eclipse infrastructure so slow to create new projects ? I may
>> > understand that these little libraries aren't critical (nowadays) for the
>> > eclipse ecosystem but for us it is ...
>> >
>> > Cheers
>> >
>> > Arnaud
>> >
>> > On Thursday, September 8, 2011, Jason van Zyl <ja...@maven.org> wrote:
>> >> The creation review has gone through for both Aether and Sisu. I have
>> >> also
>> >
>> > just submitted the project provisioning requests.
>> >
>> >> I'll work with Denis at Eclipse to get the provisioning done as quickly
>> >> as
>> >
>> > possible so we can do the necessary work to run out releases of Sisu and
>> > Aether and therefore Maven 3.0.4.
>> >
>> >> On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:
>> >>> The creation reviews for Sisu and Aether have been started:
>> >>>
>> >>> http://eclipse.org/proposals/technology.aether/
>> >>> http://eclipse.org/proposals/technology.sisu/
>> >>>
>> >>> They will both finish on September 7th.
>> >>>
>> >>> When finished we'll turn out a release ASAP.
>> >>>
>> >>> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
>> >>>>> Janet just finished the trademark review and everything is clear.
>> >>>>> Wayne Beaton and I both forgot about starting the trademark review
>> >>>>> and it's required before the project creation review can start. The
>> >>>>> project
>> >
>> > creation
>> >
>> >>>>> review will start next week.
>> >>>>
>> >>>> Ok, thus the ball is on your side now.
>> >>>>
>> >>>> Thx
>> >>>>
>> >>>> Arnaud
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Jason
>> >>>
>> >>> ----------------------------------------------------------
>> >>> Jason van Zyl
>> >>> Founder,  Apache Maven
>> >>> http://twitter.com/jvanzyl
>> >>> ---------------------------------------------------------
>> >>>
>> >>> What matters is not ideas, but the people who have them. Good people
>> >>> can
>> >
>> > fix bad ideas, but good ideas can't save bad people.
>> >
>> >>> -- Paul Graham
>> >>
>> >> Thanks,
>> >>
>> >> Jason
>> >>
>> >> ----------------------------------------------------------
>> >> Jason van Zyl
>> >> Founder,  Apache Maven
>> >> http://twitter.com/jvanzyl
>> >> ---------------------------------------------------------
>> >>
>> >> We all have problems. How we deal with them is a measure of our worth.
>> >>
>> >> -- Unknown
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> Our achievements speak for themselves. What we have to keep track
>> of are our failures, discouragements and doubts. We tend to forget
>> the past difficulties, the many false starts, and the painful
>> groping. We see our past achievements as the end result of a
>> clean forward thrust, and our present difficulties as
>> signs of decline and decay.
>>
>>  -- Eric Hoffer, Reflections on the Human Condition
>
>
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Hervé BOUTEMY <he...@free.fr>.

I don't have a view on the way things happen nor how much steps are still 
pending, but FYI, things are on their way: there is now a project page [1] 
(even if empty), and CLAs are on their way: I was asked for it a week ago (i 
suppose it's the same for others) and replied a few days ago, I'm now waiting 
for my account creation.

We knew it would take some time.
I'm using this time to enhance the documentation [2]: help wanted :)

Regards,

Hervé

[1] 
http://www.eclipse.org/projects/project_summary.php?projectid=technology.aether

[2] http://maven.apache.org/ref/3.0.4-SNAPSHOT/maven-model-builder/

Le samedi 17 septembre 2011, Jason van Zyl a écrit :
> The latest is always available here:
> 
> http://eclipse.org/proposals/technology.aether/
> 
> We still have to refactor the package names as well which we are going to
> do next week. We've released Aether 1.13 and Sisu 2.3.0 so we can use
> those as well if we want. If you want to stick with the proper Eclipse
> releases then it comes when it comes.
> 
> I believe last week the Eclipse IT folks were installing new hardware and
> pre-emptively taking security measures because of the security
> vulnerability in Apache HTTPD and kernel.org hack. There is also a list of
> projects waiting to provisioned so we're in line with everyone else. If
> folks are in a rush use Aether 1.13 and Sisu 2.3.0, if not then just be
> patient. Sometimes projects get provisioned the day the request goes in,
> sometimes it's 2-3 weeks. Just depends what else is going on. It's only
> been 8 days so far since I made the provisioning request.
> 
> On Sep 17, 2011, at 11:25 AM, Arnaud Héritier wrote:
> > Hi Jason (and others aether/sisu commiters)
> > 
> > Do you have some news ( am I the only one to cross users waiting for new
> > releases to show that our project is always alive?)
> > 
> > Is the eclipse infrastructure so slow to create new projects ? I may
> > understand that these little libraries aren't critical (nowadays) for the
> > eclipse ecosystem but for us it is ...
> > 
> > Cheers
> > 
> > Arnaud
> > 
> > On Thursday, September 8, 2011, Jason van Zyl <ja...@maven.org> wrote:
> >> The creation review has gone through for both Aether and Sisu. I have
> >> also
> > 
> > just submitted the project provisioning requests.
> > 
> >> I'll work with Denis at Eclipse to get the provisioning done as quickly
> >> as
> > 
> > possible so we can do the necessary work to run out releases of Sisu and
> > Aether and therefore Maven 3.0.4.
> > 
> >> On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:
> >>> The creation reviews for Sisu and Aether have been started:
> >>> 
> >>> http://eclipse.org/proposals/technology.aether/
> >>> http://eclipse.org/proposals/technology.sisu/
> >>> 
> >>> They will both finish on September 7th.
> >>> 
> >>> When finished we'll turn out a release ASAP.
> >>> 
> >>> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
> >>>>> Janet just finished the trademark review and everything is clear.
> >>>>> Wayne Beaton and I both forgot about starting the trademark review
> >>>>> and it's required before the project creation review can start. The
> >>>>> project
> > 
> > creation
> > 
> >>>>> review will start next week.
> >>>> 
> >>>> Ok, thus the ball is on your side now.
> >>>> 
> >>>> Thx
> >>>> 
> >>>> Arnaud
> >>> 
> >>> Thanks,
> >>> 
> >>> Jason
> >>> 
> >>> ----------------------------------------------------------
> >>> Jason van Zyl
> >>> Founder,  Apache Maven
> >>> http://twitter.com/jvanzyl
> >>> ---------------------------------------------------------
> >>> 
> >>> What matters is not ideas, but the people who have them. Good people
> >>> can
> > 
> > fix bad ideas, but good ideas can't save bad people.
> > 
> >>> -- Paul Graham
> >> 
> >> Thanks,
> >> 
> >> Jason
> >> 
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >> 
> >> We all have problems. How we deal with them is a measure of our worth.
> >> 
> >> -- Unknown
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> Our achievements speak for themselves. What we have to keep track
> of are our failures, discouragements and doubts. We tend to forget
> the past difficulties, the many false starts, and the painful
> groping. We see our past achievements as the end result of a
> clean forward thrust, and our present difficulties as
> signs of decline and decay.
> 
>  -- Eric Hoffer, Reflections on the Human Condition


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Derricutt <ma...@talios.com>.

I was just discussing this at lunch with coworkers and was about to post
the very same question.  Would be great to see movement on this.

-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Fri, Nov 4, 2011 at 12:42 PM, David Jencks <da...@yahoo.com>wrote:

> Another month went by.... any progress?
>
> david jencks
>
> On Sep 30, 2011, at 3:50 AM, Stephen Connolly wrote:
>
> > To clarify... I last checked yesterday, and the PMC in question is some
> > eclipse PMC but it is unclear to me, only having just got my eclipse
> account
> > set up, exactly which
> >
> > On 30 September 2011 11:48, Stephen Connolly <
> > stephen.alan.connolly@gmail.com> wrote:
> >
> >> When I last checked, the code import is still waiting for PMC
> approval... I
> >> suspect that until the code has been imported there cannot be a release
> ;-)
> >>
> >>
> >> On 30 September 2011 10:05, Mark Derricutt <ma...@talios.com> wrote:
> >>
> >>> Jason - is there any further news on the Aether/Sisu front?  Really
> >>> starting
> >>> to get an itch for a 3.0.4 release - my manager this morning was having
> >>> strange resolution issues that I traced to same issues I've been seeing
> >>> with
> >>> the currently shipped aether.
> >>>
> >>> Would be good to get a 3.0.4 release out with some updated plugin
> versions
> >>> set as well ( the new wagon, archetype come to mind ).
> >>>
> >>> Mark
> >>>
> >>>
> >>> --
> >>> "Great artists are extremely selfish and arrogant things" — Steven
> Wilson,
> >>> Porcupine Tree
> >>>
> >>>
> >>> On Wed, Sep 21, 2011 at 12:17 AM, Baptiste MATHUS <ml...@batmat.net>
> wrote:
> >>>
> >>>> To be sure, are you talking about renaming Aether packages to
> something
> >>>> like
> >>>> org.eclipse.aether?
> >>>>
> >>>
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

no reason at all other than no committer has reasked for the dependency
change. i am hoping benjamin can make a release of aether cut from the
eclipse git repo or some other public repo clone of the eclipse one, and
then asks to use that dep...

alternatively if somebody wants to propose what they will release as an
aether patch release and have the pmc vote for that dep change up front

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 8 Nov 2011 08:15, "Brett Porter" <br...@apache.org> wrote:

>
> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>
> > You guys decided you wanted to wait so let's just wait. I didn't think
> it would take this long to get through either but it is what it is. So
> realistically we're looking at 3.0.4 in 4 weeks.
>
> But it could also be longer.
>
> I don't see why we should treat the existing EPL release any differently
> than if it were to be released from Eclipse at this point. Going to Eclipse
> is a positive step from now, there will be better transparency and
> governance, but arriving there is not the end of the road. It's going to be
> even longer that it is more diverse, graduates the incubator there, and
> becomes just consumable as a dependency.
>
> If someone wants to do a 3.0.4 release, they should do it, whether that
> doesn't include this fix, or delivers it as a patch on the version we're
> using, or uses the EPL version from Github. If nobody is prepared to do a
> release now, that's fine too, but they shouldn't have to sit around
> waiting. The whole reason I was concerned about Aether in the first place
> was because we'd get stuck not being able to ship a fix to Maven without
> getting around another project - we can't let ourselves get into that
> position.
>
> In my ideal world, Benjamin would cherry-pick the fix he's already made
> for the issue Mark is concerned about, release 1.11.1, and we upgrade and
> someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the
> direction everything is going, and let everyone get on with it.
>
> Is there a reason we shouldn't do that?
>
> Cheers,
> Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@tesla.io>.

Yes, it all works fine and the tests pass.

On Nov 10, 2011, at 10:38 AM, Olivier Lamy wrote:

> Ok I will start a vote for both aether and sisu upgrade.
> 
> Just tested today both. Just need a simple change to have unit tests passed.
> 
> 
> 2011/11/10 Jason van Zyl <ja...@tesla.io>:
>> Sure, I'll let someone the PMC call the vote. Happy to do the work once that's taken care of.
>> 
>> On Nov 10, 2011, at 9:08 AM, Stephen Connolly wrote:
>> 
>>> I'm fine, but process says you should call a vote to change the
>>> dependency from the ASL version to the EPL licensed version. Yes there
>>> was a vote before, but the circumstances have changed, and hence there
>>> is strong likelyhood (IMHO) that a re-vote might result in a different
>>> answer
>>> 
>>> -Stephen
>>> 
>>> On 10 November 2011 13:50, Jason van Zyl <ja...@tesla.io> wrote:
>>>> So are people fine with using Aether 1.13. I've already got the necessary changes if we want to go ahead with that.
>>>> 
>>>> On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote:
>>>> 
>>>>> 
>>>>> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:
>>>>> 
>>>>>> 
>>>>>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>>>>>> 
>>>>>>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
>>>>>> 
>>>>>> But it could also be longer.
>>>>>> 
>>>>> 
>>>>> Yes, but that's the decision you made.
>>>>> 
>>>>>> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.
>>>>> 
>>>>> Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.
>>>>> 
>>>>>> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
>>>>>> 
>>>>>> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
>>>>>> 
>>>>>> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
>>>>>> 
>>>>>> Is there a reason we shouldn't do that?
>>>>>> 
>>>>> 
>>>>> Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.
>>>>> 
>>>>>> Cheers,
>>>>>> Brett
>>>>>> 
>>>>>> --
>>>>>> Brett Porter
>>>>>> brett@apache.org
>>>>>> http://brettporter.wordpress.com/
>>>>>> 
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> 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,  Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>> 
>>>>> Our achievements speak for themselves. What we have to keep track
>>>>> of are our failures, discouragements and doubts. We tend to forget
>>>>> the past difficulties, the many false starts, and the painful
>>>>> groping. We see our past achievements as the end result of a
>>>>> clean forward thrust, and our present difficulties as
>>>>> signs of decline and decay.
>>>>> 
>>>>> -- Eric Hoffer, Reflections on the Human Condition
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> Thanks,
>>>> 
>>>> Jason
>>>> 
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder,  Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>> 
>>>> We all have problems. How we deal with them is a measure of our worth.
>>>> 
>>>>  -- Unknown
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> 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,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> 
> -- 
> 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
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.

  -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Olivier Lamy <ol...@apache.org>.

Ok I will start a vote for both aether and sisu upgrade.

Just tested today both. Just need a simple change to have unit tests passed.


2011/11/10 Jason van Zyl <ja...@tesla.io>:
> Sure, I'll let someone the PMC call the vote. Happy to do the work once that's taken care of.
>
> On Nov 10, 2011, at 9:08 AM, Stephen Connolly wrote:
>
>> I'm fine, but process says you should call a vote to change the
>> dependency from the ASL version to the EPL licensed version. Yes there
>> was a vote before, but the circumstances have changed, and hence there
>> is strong likelyhood (IMHO) that a re-vote might result in a different
>> answer
>>
>> -Stephen
>>
>> On 10 November 2011 13:50, Jason van Zyl <ja...@tesla.io> wrote:
>>> So are people fine with using Aether 1.13. I've already got the necessary changes if we want to go ahead with that.
>>>
>>> On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote:
>>>
>>>>
>>>> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:
>>>>
>>>>>
>>>>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>>>>>
>>>>>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
>>>>>
>>>>> But it could also be longer.
>>>>>
>>>>
>>>> Yes, but that's the decision you made.
>>>>
>>>>> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.
>>>>
>>>> Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.
>>>>
>>>>> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
>>>>>
>>>>> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
>>>>>
>>>>> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
>>>>>
>>>>> Is there a reason we shouldn't do that?
>>>>>
>>>>
>>>> Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.
>>>>
>>>>> Cheers,
>>>>> Brett
>>>>>
>>>>> --
>>>>> Brett Porter
>>>>> brett@apache.org
>>>>> http://brettporter.wordpress.com/
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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,  Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> Our achievements speak for themselves. What we have to keep track
>>>> of are our failures, discouragements and doubts. We tend to forget
>>>> the past difficulties, the many false starts, and the painful
>>>> groping. We see our past achievements as the end result of a
>>>> clean forward thrust, and our present difficulties as
>>>> signs of decline and decay.
>>>>
>>>> -- Eric Hoffer, Reflections on the Human Condition
>>>>
>>>>
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> We all have problems. How we deal with them is a measure of our worth.
>>>
>>>  -- Unknown
>>>
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>



-- 
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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@tesla.io>.

Sure, I'll let someone the PMC call the vote. Happy to do the work once that's taken care of.

On Nov 10, 2011, at 9:08 AM, Stephen Connolly wrote:

> I'm fine, but process says you should call a vote to change the
> dependency from the ASL version to the EPL licensed version. Yes there
> was a vote before, but the circumstances have changed, and hence there
> is strong likelyhood (IMHO) that a re-vote might result in a different
> answer
> 
> -Stephen
> 
> On 10 November 2011 13:50, Jason van Zyl <ja...@tesla.io> wrote:
>> So are people fine with using Aether 1.13. I've already got the necessary changes if we want to go ahead with that.
>> 
>> On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote:
>> 
>>> 
>>> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:
>>> 
>>>> 
>>>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>>>> 
>>>>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
>>>> 
>>>> But it could also be longer.
>>>> 
>>> 
>>> Yes, but that's the decision you made.
>>> 
>>>> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.
>>> 
>>> Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.
>>> 
>>>> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
>>>> 
>>>> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
>>>> 
>>>> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
>>>> 
>>>> Is there a reason we shouldn't do that?
>>>> 
>>> 
>>> Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.
>>> 
>>>> Cheers,
>>>> Brett
>>>> 
>>>> --
>>>> Brett Porter
>>>> brett@apache.org
>>>> http://brettporter.wordpress.com/
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> 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,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>> 
>>> Our achievements speak for themselves. What we have to keep track
>>> of are our failures, discouragements and doubts. We tend to forget
>>> the past difficulties, the many false starts, and the painful
>>> groping. We see our past achievements as the end result of a
>>> clean forward thrust, and our present difficulties as
>>> signs of decline and decay.
>>> 
>>> -- Eric Hoffer, Reflections on the Human Condition
>>> 
>>> 
>>> 
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> We all have problems. How we deal with them is a measure of our worth.
>> 
>>  -- Unknown
>> 
>> 
>> 
>> 
>> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

I'm fine, but process says you should call a vote to change the
dependency from the ASL version to the EPL licensed version. Yes there
was a vote before, but the circumstances have changed, and hence there
is strong likelyhood (IMHO) that a re-vote might result in a different
answer

-Stephen

On 10 November 2011 13:50, Jason van Zyl <ja...@tesla.io> wrote:
> So are people fine with using Aether 1.13. I've already got the necessary changes if we want to go ahead with that.
>
> On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote:
>
>>
>> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:
>>
>>>
>>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>>>
>>>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
>>>
>>> But it could also be longer.
>>>
>>
>> Yes, but that's the decision you made.
>>
>>> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.
>>
>> Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.
>>
>>> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
>>>
>>> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
>>>
>>> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
>>>
>>> Is there a reason we shouldn't do that?
>>>
>>
>> Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.
>>
>>> Cheers,
>>> Brett
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://brettporter.wordpress.com/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> Our achievements speak for themselves. What we have to keep track
>> of are our failures, discouragements and doubts. We tend to forget
>> the past difficulties, the many false starts, and the painful
>> groping. We see our past achievements as the end result of a
>> clean forward thrust, and our present difficulties as
>> signs of decline and decay.
>>
>> -- Eric Hoffer, Reflections on the Human Condition
>>
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> We all have problems. How we deal with them is a measure of our worth.
>
>  -- Unknown
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@tesla.io>.

So are people fine with using Aether 1.13. I've already got the necessary changes if we want to go ahead with that.

On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote:

> 
> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:
> 
>> 
>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
>> 
>>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
>> 
>> But it could also be longer.
>> 
> 
> Yes, but that's the decision you made.
> 
>> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.
> 
> Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.
> 
>> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
>> 
>> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
>> 
>> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
>> 
>> Is there a reason we shouldn't do that?
>> 
> 
> Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.
> 
>> Cheers,
>> Brett
>> 
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> 
>> 
>> ---------------------------------------------------------------------
>> 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,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> Our achievements speak for themselves. What we have to keep track
> of are our failures, discouragements and doubts. We tend to forget
> the past difficulties, the many false starts, and the painful
> groping. We see our past achievements as the end result of a
> clean forward thrust, and our present difficulties as
> signs of decline and decay.
> 
> -- Eric Hoffer, Reflections on the Human Condition
> 
> 
> 
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@tesla.io>.

On Nov 8, 2011, at 12:15 AM, Brett Porter wrote:

> 
> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:
> 
>> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.
> 
> But it could also be longer.
> 

Yes, but that's the decision you made.

> I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point.

Yes, I tried to explain this a month ago. The code is all Sonatype copyright, and EPL. Wherever the code is that fact remains the same.

> Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.
> 
> If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.
> 
> In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.
> 
> Is there a reason we shouldn't do that?
> 

Because it's far more work than necessary, use Aether 1.13 that is EPL and is released. I can update it and start the release process tomorrow.

> Cheers,
> Brett
> 
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> 
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

 -- Eric Hoffer, Reflections on the Human Condition

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Brett Porter <br...@apache.org>.

On 07/11/2011, at 8:43 AM, Jason van Zyl wrote:

> You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.

But it could also be longer.

I don't see why we should treat the existing EPL release any differently than if it were to be released from Eclipse at this point. Going to Eclipse is a positive step from now, there will be better transparency and governance, but arriving there is not the end of the road. It's going to be even longer that it is more diverse, graduates the incubator there, and becomes just consumable as a dependency.

If someone wants to do a 3.0.4 release, they should do it, whether that doesn't include this fix, or delivers it as a patch on the version we're using, or uses the EPL version from Github. If nobody is prepared to do a release now, that's fine too, but they shouldn't have to sit around waiting. The whole reason I was concerned about Aether in the first place was because we'd get stuck not being able to ship a fix to Maven without getting around another project - we can't let ourselves get into that position.

In my ideal world, Benjamin would cherry-pick the fix he's already made for the issue Mark is concerned about, release 1.11.1, and we upgrade and someone releases Maven 3.0.4. That wouldn't take long, wouldn't change the direction everything is going, and let everyone get on with it.

Is there a reason we shouldn't do that?

Cheers,
Brett

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@tesla.io>.

You guys decided you wanted to wait so let's just wait. I didn't think it would take this long to get through either but it is what it is. So realistically we're looking at 3.0.4 in 4 weeks.

On Nov 7, 2011, at 9:24 AM, John Casey wrote:

> On 11/4/11 7:28 AM, Alexander Kurtakov wrote:
>> On 13:04:06 Friday 04 November 2011 Stephen Connolly wrote:
>>> On 4 November 2011 10:22, Benjamin Bentmann <be...@udo.edu> 
>> wrote:
>>>> David Jencks wrote:
>>>>> Another month went by.... any progress?
>>>> 
>>>> The sources were checked into git according to parallel IP, awaiting full
>>>> legal approval. Some dependencies still await review [0], too.
>>> 
>>> Any idea what's needed to prod the process along... never having been
>>> involved at eclipse before, this seems like a rather long process with
>>> no visibility (as far as I can see) as to what is taking place and
>>> where the blockers are
>> 
>> Eclipse IP team is going through every single dependency (even test ones) and 
>> checks that they have proper license and so on. And Maven projects tend to 
>> have so many dependencies that this is only slowing the process. Note that
>> different version of e.g. plexus-utils have to be examined separately because 
>> something can sneak in. And a number of plexus artifacts are missing license 
>> information in a number of places (just an example). 
>> Please note that this is a problem not only for Eclipse but for others too. We 
>> (Fedora) have opened a number of issues to get licencing clarified in so many 
>> places that I can't count them only for maven+plugins dependencies. 
>> Another thing is the usage of outdated and obsoleted versions in a number of 
>> artifacts which have to reviewed separately despite them being dead for long 
>> time. Btw, this is part of the usual complain that Maven downloads the 
>> Internet because for certain artifacats usual "clean install" downloads more 
>> than 5 versions with all of their dependencies. This is certainly a burden for 
>> every IP clearance review.
> 
> If only the review could be distributed, and the dependencies be
> published with some sort of signature pre-certifying them. But I guess
> that would amount to Eclipse (and others...Fedora?) trusting the
> certifications coming from an outside entity.
> 
> It seems a tad wasteful to have multiple entities doing the same thing
> in parallel, and it's definitely sub-optimal to have this sort of
> bottleneck develop just before a release happens.
> 
>> 
>> Alexander Kurtakov
>> 
>>> 
>>>> Benjamin
>>>> 
>>>> 
>>>> [0]
>>>> http://www.eclipse.org/projects/ip_log.php?projectid=technology.aether
>>>> 
>>>> ---------------------------------------------------------------------
>>>> 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
>> 
> 
> 
> -- 
> John Casey
> Developer, PMC Chair - Apache Maven (http://maven.apache.org)
> Blog: http://www.johnofalltrades.name/
> 
> ---------------------------------------------------------------------
> 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,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by John Casey <jd...@commonjava.org>.

On 11/4/11 7:28 AM, Alexander Kurtakov wrote:
> On 13:04:06 Friday 04 November 2011 Stephen Connolly wrote:
>> On 4 November 2011 10:22, Benjamin Bentmann <be...@udo.edu> 
> wrote:
>>> David Jencks wrote:
>>>> Another month went by.... any progress?
>>>
>>> The sources were checked into git according to parallel IP, awaiting full
>>> legal approval. Some dependencies still await review [0], too.
>>
>> Any idea what's needed to prod the process along... never having been
>> involved at eclipse before, this seems like a rather long process with
>> no visibility (as far as I can see) as to what is taking place and
>> where the blockers are
> 
> Eclipse IP team is going through every single dependency (even test ones) and 
> checks that they have proper license and so on. And Maven projects tend to 
> have so many dependencies that this is only slowing the process. Note that
> different version of e.g. plexus-utils have to be examined separately because 
> something can sneak in. And a number of plexus artifacts are missing license 
> information in a number of places (just an example). 
> Please note that this is a problem not only for Eclipse but for others too. We 
> (Fedora) have opened a number of issues to get licencing clarified in so many 
> places that I can't count them only for maven+plugins dependencies. 
> Another thing is the usage of outdated and obsoleted versions in a number of 
> artifacts which have to reviewed separately despite them being dead for long 
> time. Btw, this is part of the usual complain that Maven downloads the 
> Internet because for certain artifacats usual "clean install" downloads more 
> than 5 versions with all of their dependencies. This is certainly a burden for 
> every IP clearance review.

If only the review could be distributed, and the dependencies be
published with some sort of signature pre-certifying them. But I guess
that would amount to Eclipse (and others...Fedora?) trusting the
certifications coming from an outside entity.

It seems a tad wasteful to have multiple entities doing the same thing
in parallel, and it's definitely sub-optimal to have this sort of
bottleneck develop just before a release happens.

> 
> Alexander Kurtakov
> 
>>
>>> Benjamin
>>>
>>>
>>> [0]
>>> http://www.eclipse.org/projects/ip_log.php?projectid=technology.aether
>>>
>>> ---------------------------------------------------------------------
>>> 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
> 


-- 
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Alexander Kurtakov <ak...@redhat.com>.

On 13:04:06 Friday 04 November 2011 Stephen Connolly wrote:
> On 4 November 2011 10:22, Benjamin Bentmann <be...@udo.edu> 
wrote:
> > David Jencks wrote:
> >> Another month went by.... any progress?
> > 
> > The sources were checked into git according to parallel IP, awaiting full
> > legal approval. Some dependencies still await review [0], too.
> 
> Any idea what's needed to prod the process along... never having been
> involved at eclipse before, this seems like a rather long process with
> no visibility (as far as I can see) as to what is taking place and
> where the blockers are

Eclipse IP team is going through every single dependency (even test ones) and 
checks that they have proper license and so on. And Maven projects tend to 
have so many dependencies that this is only slowing the process. Note that 
different version of e.g. plexus-utils have to be examined separately because 
something can sneak in. And a number of plexus artifacts are missing license 
information in a number of places (just an example). 
Please note that this is a problem not only for Eclipse but for others too. We 
(Fedora) have opened a number of issues to get licencing clarified in so many 
places that I can't count them only for maven+plugins dependencies. 
Another thing is the usage of outdated and obsoleted versions in a number of 
artifacts which have to reviewed separately despite them being dead for long 
time. Btw, this is part of the usual complain that Maven downloads the 
Internet because for certain artifacats usual "clean install" downloads more 
than 5 versions with all of their dependencies. This is certainly a burden for 
every IP clearance review.

Alexander Kurtakov

> 
> > Benjamin
> > 
> > 
> > [0]
> > http://www.eclipse.org/projects/ip_log.php?projectid=technology.aether
> > 
> > ---------------------------------------------------------------------
> > 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

On 4 November 2011 13:41, Alexander Kurtakov <ak...@redhat.com> wrote:
> On 15:35:35 Friday 04 November 2011 Jesse McConnell wrote:
>> Perhaps they don't have to make a formal eclipse release, but so long
>> as they have parallel ip in place they should be able make a milestone
>> or release candidate release.  The formal eclipse 'release' isn't what
>> we in maven lands consider a release really, they consider a release
>> something that can be 'conditioned' with their pack process and signed
>> by the official eclipse key, etc.  It also has to have had release
>> docuware created, a static iplog (which is the hold up here) and then
>> gone though the release review process (which is generally a couple of
>> weeks after its been called for).
>>
>> I suspect they should be able to make an RC that you could put into
>> central and release maven against though...it would just have to
>> contain something like 1.0.0.RC0 as the version to adhere to the
>> spirit of the law.  We release jetty rc's into maven central before
>> formal 'release' and in some cases its actually encouraged as they
>> look for published milestone or rc releases during the release review
>> process as a gauge of release maturity (at least I think that is it,
>> its been mentioned a couple of times in the last few years)
>
> Well, Probably I misunderstand the discussion but IIRC there was a vote that
> decided that Aether and Sisu will be fine once there is an Eclipse.org release.
> There might really be such difference in what everyone understand as a release
> but an unofficial release on maven central won't be any different than the latest
> sonatype releases on maven central.

Actually, I think as long as the release is pushed to central via the
approved route for artifacts belonging to groupId org.eclipse.*, is
signed by at least one of the eclipse committers of the project and as
long as the source for that release is in the eclipse.org SCM, then I
personally see that as being fine.

The source was only loaded into the eclipse SCM 9 days ago... and I
only saw that today...

>
> Alex
>
>>
>> cheers,
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@gmail.com
>>
>> On Fri, Nov 4, 2011 at 06:37, Alexander Kurtakov <ak...@redhat.com>
> wrote:
>> > On 13:30:12 Friday 04 November 2011 Stephen Connolly wrote:
>> >> On 4 November 2011 11:04, Mark Derricutt <ma...@talios.com> wrote:
>> >> > If its stuck at the bottom of the pile for an unknown amount of time -
>> >> > I'd REALLY love to see 3.0.4. ship out with the current non-eclipse
>> >> > Aether.
>> >> >
>> >> > Leaving a broken Maven out in the wild for what appears to be politics
>> >> > more than anything just continues to hurt the Maven name.
>> >> >
>> >> > I was under the impression that the "move to Eclipse" was only going
>> >> > to take 2-3 weeks, whats it been now - 2-3 months almost?
>> >>
>> >> This is what we were lead to believe, i.e. that it would be released @
>> >> eclipse within a couple of weeks....
>> >>
>> >> If it really is going to take much longer then all somebody needs to
>> >> do is propose a vote to release with the new one, and then the PMC can
>> >> decide on that vote... at the time of the last vote we were told it
>> >> would be at eclipse soon... not that a first release from eclipse
>> >> would be a long time away...
>> >
>> > I doubt that someone can promise a date.  Eclipse releases can happen
>> > only after IP clearance is finished and if issues are identified moving
>> > to new dependencies or new versions with fixed legal issues might be
>> > needed and this might need some effort in different upstreams. One can
>> > argue whether such deep reviews should be performed but this seems to be
>> > the only way to be at least partly sure that you don't have any obvious
>> > legal issues. With my Fedora hat on I can ensure you that we have
>> > identified tons of issues during the Package review process.
>> >
>> > Alexander Kurtakov
>> >
>> >> So if there is a committer willing to step up and ask to use the newer
>> >> dependency... please do
>> >>
>> >> -Stephen
>> >>
>> >> > Mark
>> >> >
>> >> > --
>> >> > "Great artists are extremely selfish and arrogant things" — Steven
>> >> > Wilson, Porcupine Tree
>> >> >
>> >> >
>> >> > On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
>> >> >
>> >> > benjamin.bentmann@udo.edu> wrote:
>> >> >> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
>> >> >> committer, I see currently around 180 open CQs that the IP team needs
>> >> >> to deal with, Aether just being one among many projects.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Alexander Kurtakov <ak...@redhat.com>.

On 15:35:35 Friday 04 November 2011 Jesse McConnell wrote:
> Perhaps they don't have to make a formal eclipse release, but so long
> as they have parallel ip in place they should be able make a milestone
> or release candidate release.  The formal eclipse 'release' isn't what
> we in maven lands consider a release really, they consider a release
> something that can be 'conditioned' with their pack process and signed
> by the official eclipse key, etc.  It also has to have had release
> docuware created, a static iplog (which is the hold up here) and then
> gone though the release review process (which is generally a couple of
> weeks after its been called for).
> 
> I suspect they should be able to make an RC that you could put into
> central and release maven against though...it would just have to
> contain something like 1.0.0.RC0 as the version to adhere to the
> spirit of the law.  We release jetty rc's into maven central before
> formal 'release' and in some cases its actually encouraged as they
> look for published milestone or rc releases during the release review
> process as a gauge of release maturity (at least I think that is it,
> its been mentioned a couple of times in the last few years)

Well, Probably I misunderstand the discussion but IIRC there was a vote that 
decided that Aether and Sisu will be fine once there is an Eclipse.org release. 
There might really be such difference in what everyone understand as a release 
but an unofficial release on maven central won't be any different than the latest 
sonatype releases on maven central.

Alex

> 
> cheers,
> jesse
> 
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
> 
> On Fri, Nov 4, 2011 at 06:37, Alexander Kurtakov <ak...@redhat.com> 
wrote:
> > On 13:30:12 Friday 04 November 2011 Stephen Connolly wrote:
> >> On 4 November 2011 11:04, Mark Derricutt <ma...@talios.com> wrote:
> >> > If its stuck at the bottom of the pile for an unknown amount of time -
> >> > I'd REALLY love to see 3.0.4. ship out with the current non-eclipse
> >> > Aether.
> >> > 
> >> > Leaving a broken Maven out in the wild for what appears to be politics
> >> > more than anything just continues to hurt the Maven name.
> >> > 
> >> > I was under the impression that the "move to Eclipse" was only going
> >> > to take 2-3 weeks, whats it been now - 2-3 months almost?
> >> 
> >> This is what we were lead to believe, i.e. that it would be released @
> >> eclipse within a couple of weeks....
> >> 
> >> If it really is going to take much longer then all somebody needs to
> >> do is propose a vote to release with the new one, and then the PMC can
> >> decide on that vote... at the time of the last vote we were told it
> >> would be at eclipse soon... not that a first release from eclipse
> >> would be a long time away...
> > 
> > I doubt that someone can promise a date.  Eclipse releases can happen
> > only after IP clearance is finished and if issues are identified moving
> > to new dependencies or new versions with fixed legal issues might be
> > needed and this might need some effort in different upstreams. One can
> > argue whether such deep reviews should be performed but this seems to be
> > the only way to be at least partly sure that you don't have any obvious
> > legal issues. With my Fedora hat on I can ensure you that we have
> > identified tons of issues during the Package review process.
> > 
> > Alexander Kurtakov
> > 
> >> So if there is a committer willing to step up and ask to use the newer
> >> dependency... please do
> >> 
> >> -Stephen
> >> 
> >> > Mark
> >> > 
> >> > --
> >> > "Great artists are extremely selfish and arrogant things" — Steven
> >> > Wilson, Porcupine Tree
> >> > 
> >> > 
> >> > On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
> >> > 
> >> > benjamin.bentmann@udo.edu> wrote:
> >> >> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
> >> >> committer, I see currently around 180 open CQs that the IP team needs
> >> >> to deal with, Aether just being one among many projects.
> >> 
> >> ---------------------------------------------------------------------
> >> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jesse McConnell <je...@gmail.com>.

Perhaps they don't have to make a formal eclipse release, but so long
as they have parallel ip in place they should be able make a milestone
or release candidate release.  The formal eclipse 'release' isn't what
we in maven lands consider a release really, they consider a release
something that can be 'conditioned' with their pack process and signed
by the official eclipse key, etc.  It also has to have had release
docuware created, a static iplog (which is the hold up here) and then
gone though the release review process (which is generally a couple of
weeks after its been called for).

I suspect they should be able to make an RC that you could put into
central and release maven against though...it would just have to
contain something like 1.0.0.RC0 as the version to adhere to the
spirit of the law.  We release jetty rc's into maven central before
formal 'release' and in some cases its actually encouraged as they
look for published milestone or rc releases during the release review
process as a gauge of release maturity (at least I think that is it,
its been mentioned a couple of times in the last few years)

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@gmail.com



On Fri, Nov 4, 2011 at 06:37, Alexander Kurtakov <ak...@redhat.com> wrote:
> On 13:30:12 Friday 04 November 2011 Stephen Connolly wrote:
>> On 4 November 2011 11:04, Mark Derricutt <ma...@talios.com> wrote:
>> > If its stuck at the bottom of the pile for an unknown amount of time -
>> > I'd REALLY love to see 3.0.4. ship out with the current non-eclipse
>> > Aether.
>> >
>> > Leaving a broken Maven out in the wild for what appears to be politics
>> > more than anything just continues to hurt the Maven name.
>> >
>> > I was under the impression that the "move to Eclipse" was only going to
>> > take 2-3 weeks, whats it been now - 2-3 months almost?
>>
>> This is what we were lead to believe, i.e. that it would be released @
>> eclipse within a couple of weeks....
>>
>> If it really is going to take much longer then all somebody needs to
>> do is propose a vote to release with the new one, and then the PMC can
>> decide on that vote... at the time of the last vote we were told it
>> would be at eclipse soon... not that a first release from eclipse
>> would be a long time away...
>
> I doubt that someone can promise a date.  Eclipse releases can happen only
> after IP clearance is finished and if issues are identified moving to new
> dependencies or new versions with fixed legal issues might be needed and this
> might need some effort in different upstreams. One can argue whether such deep
> reviews should be performed but this seems to be the only way to be at least
> partly sure that you don't have any obvious legal issues. With my Fedora hat
> on I can ensure you that we have identified tons of issues during the Package
> review process.
>
> Alexander Kurtakov
>
>
>
>>
>> So if there is a committer willing to step up and ask to use the newer
>> dependency... please do
>>
>> -Stephen
>>
>> > Mark
>> >
>> > --
>> > "Great artists are extremely selfish and arrogant things" — Steven
>> > Wilson, Porcupine Tree
>> >
>> >
>> > On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
>> >
>> > benjamin.bentmann@udo.edu> wrote:
>> >> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
>> >> committer, I see currently around 180 open CQs that the IP team needs to
>> >> deal with, Aether just being one among many projects.
>>
>> ---------------------------------------------------------------------
>> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Alexander Kurtakov <ak...@redhat.com>.

On 13:30:12 Friday 04 November 2011 Stephen Connolly wrote:
> On 4 November 2011 11:04, Mark Derricutt <ma...@talios.com> wrote:
> > If its stuck at the bottom of the pile for an unknown amount of time -
> > I'd REALLY love to see 3.0.4. ship out with the current non-eclipse
> > Aether.
> > 
> > Leaving a broken Maven out in the wild for what appears to be politics
> > more than anything just continues to hurt the Maven name.
> > 
> > I was under the impression that the "move to Eclipse" was only going to
> > take 2-3 weeks, whats it been now - 2-3 months almost?
> 
> This is what we were lead to believe, i.e. that it would be released @
> eclipse within a couple of weeks....
> 
> If it really is going to take much longer then all somebody needs to
> do is propose a vote to release with the new one, and then the PMC can
> decide on that vote... at the time of the last vote we were told it
> would be at eclipse soon... not that a first release from eclipse
> would be a long time away...

I doubt that someone can promise a date.  Eclipse releases can happen only 
after IP clearance is finished and if issues are identified moving to new 
dependencies or new versions with fixed legal issues might be needed and this 
might need some effort in different upstreams. One can argue whether such deep 
reviews should be performed but this seems to be the only way to be at least 
partly sure that you don't have any obvious legal issues. With my Fedora hat 
on I can ensure you that we have identified tons of issues during the Package 
review process.

Alexander Kurtakov



> 
> So if there is a committer willing to step up and ask to use the newer
> dependency... please do
> 
> -Stephen
> 
> > Mark
> > 
> > --
> > "Great artists are extremely selfish and arrogant things" — Steven
> > Wilson, Porcupine Tree
> > 
> > 
> > On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
> > 
> > benjamin.bentmann@udo.edu> wrote:
> >> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
> >> committer, I see currently around 180 open CQs that the IP team needs to
> >> deal with, Aether just being one among many projects.
> 
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

On 4 November 2011 11:04, Mark Derricutt <ma...@talios.com> wrote:
> If its stuck at the bottom of the pile for an unknown amount of time - I'd
> REALLY love to see 3.0.4. ship out with the current non-eclipse Aether.
>
> Leaving a broken Maven out in the wild for what appears to be politics more
> than anything just continues to hurt the Maven name.
>
> I was under the impression that the "move to Eclipse" was only going to
> take 2-3 weeks, whats it been now - 2-3 months almost?
>

This is what we were lead to believe, i.e. that it would be released @
eclipse within a couple of weeks....

If it really is going to take much longer then all somebody needs to
do is propose a vote to release with the new one, and then the PMC can
decide on that vote... at the time of the last vote we were told it
would be at eclipse soon... not that a first release from eclipse
would be a long time away...

So if there is a committer willing to step up and ask to use the newer
dependency... please do

-Stephen

> Mark
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
>
> On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> wrote:
>
>> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
>> committer, I see currently around 180 open CQs that the IP team needs to
>> deal with, Aether just being one among many projects.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Derricutt <ma...@talios.com>.

If its stuck at the bottom of the pile for an unknown amount of time - I'd
REALLY love to see 3.0.4. ship out with the current non-eclipse Aether.

Leaving a broken Maven out in the wild for what appears to be politics more
than anything just continues to hurt the Maven name.

I was under the impression that the "move to Eclipse" was only going to
take 2-3 weeks, whats it been now - 2-3 months almost?

Mark

-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Fri, Nov 4, 2011 at 11:55 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:

> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
> committer, I see currently around 180 open CQs that the IP team needs to
> deal with, Aether just being one among many projects.

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

On 4 November 2011 10:55, Benjamin Bentmann <be...@udo.edu> wrote:
> Stephen Connolly wrote:
>
>> Any idea what's needed to prod the process along... never having been
>> involved at eclipse before, this seems like a rather long process with
>> no visibility (as far as I can see) as to what is taking place and
>> where the blockers are
>
> Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse
> committer, I see currently around 180 open CQs that the IP team needs to
> deal with, Aether just being one among many projects.
>
> I don't know the details of the inner CQ processing either, so can only
> suggest you directly contact the IP team to get exact answers on the
> progress.
>
> On a personal note, I find it odd that the Maven PMC rejects to use
> (Sonatype) Aether 1.12/1.13 but is apparently very eager to consume Eclipse
> Aether, which basically offers the same functionality and uses the same
> license, EPL.
>

Please let's not start all that again....

>
> Benjamin
>
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Benjamin Bentmann <be...@udo.edu>.

Stephen Connolly wrote:

> Any idea what's needed to prod the process along... never having been
> involved at eclipse before, this seems like a rather long process with
> no visibility (as far as I can see) as to what is taking place and
> where the blockers are

Looking at Eclipse' IPZilla, which btw is accessible to any Eclipse 
committer, I see currently around 180 open CQs that the IP team needs to 
deal with, Aether just being one among many projects.

I don't know the details of the inner CQ processing either, so can only 
suggest you directly contact the IP team to get exact answers on the 
progress.

On a personal note, I find it odd that the Maven PMC rejects to use 
(Sonatype) Aether 1.12/1.13 but is apparently very eager to consume 
Eclipse Aether, which basically offers the same functionality and uses 
the same license, EPL.

Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

On 4 November 2011 10:22, Benjamin Bentmann <be...@udo.edu> wrote:
> David Jencks wrote:
>
>> Another month went by.... any progress?
>
> The sources were checked into git according to parallel IP, awaiting full
> legal approval. Some dependencies still await review [0], too.
>

Any idea what's needed to prod the process along... never having been
involved at eclipse before, this seems like a rather long process with
no visibility (as far as I can see) as to what is taking place and
where the blockers are

>
> Benjamin
>
>
> [0] http://www.eclipse.org/projects/ip_log.php?projectid=technology.aether
>
> ---------------------------------------------------------------------
> 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: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Benjamin Bentmann <be...@udo.edu>.

David Jencks wrote:

> Another month went by.... any progress?

The sources were checked into git according to parallel IP, awaiting 
full legal approval. Some dependencies still await review [0], too.


Benjamin


[0] http://www.eclipse.org/projects/ip_log.php?projectid=technology.aether

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by David Jencks <da...@yahoo.com>.

Another month went by.... any progress?

david jencks

On Sep 30, 2011, at 3:50 AM, Stephen Connolly wrote:

> To clarify... I last checked yesterday, and the PMC in question is some
> eclipse PMC but it is unclear to me, only having just got my eclipse account
> set up, exactly which
> 
> On 30 September 2011 11:48, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
> 
>> When I last checked, the code import is still waiting for PMC approval... I
>> suspect that until the code has been imported there cannot be a release ;-)
>> 
>> 
>> On 30 September 2011 10:05, Mark Derricutt <ma...@talios.com> wrote:
>> 
>>> Jason - is there any further news on the Aether/Sisu front?  Really
>>> starting
>>> to get an itch for a 3.0.4 release - my manager this morning was having
>>> strange resolution issues that I traced to same issues I've been seeing
>>> with
>>> the currently shipped aether.
>>> 
>>> Would be good to get a 3.0.4 release out with some updated plugin versions
>>> set as well ( the new wagon, archetype come to mind ).
>>> 
>>> Mark
>>> 
>>> 
>>> --
>>> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
>>> Porcupine Tree
>>> 
>>> 
>>> On Wed, Sep 21, 2011 at 12:17 AM, Baptiste MATHUS <ml...@batmat.net> wrote:
>>> 
>>>> To be sure, are you talking about renaming Aether packages to something
>>>> like
>>>> org.eclipse.aether?
>>>> 
>>> 
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

To clarify... I last checked yesterday, and the PMC in question is some
eclipse PMC but it is unclear to me, only having just got my eclipse account
set up, exactly which

On 30 September 2011 11:48, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:

> When I last checked, the code import is still waiting for PMC approval... I
> suspect that until the code has been imported there cannot be a release ;-)
>
>
> On 30 September 2011 10:05, Mark Derricutt <ma...@talios.com> wrote:
>
>> Jason - is there any further news on the Aether/Sisu front?  Really
>> starting
>> to get an itch for a 3.0.4 release - my manager this morning was having
>> strange resolution issues that I traced to same issues I've been seeing
>> with
>> the currently shipped aether.
>>
>> Would be good to get a 3.0.4 release out with some updated plugin versions
>> set as well ( the new wagon, archetype come to mind ).
>>
>> Mark
>>
>>
>> --
>> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
>> Porcupine Tree
>>
>>
>> On Wed, Sep 21, 2011 at 12:17 AM, Baptiste MATHUS <ml...@batmat.net> wrote:
>>
>> > To be sure, are you talking about renaming Aether packages to something
>> > like
>> > org.eclipse.aether?
>> >
>>
>
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Stephen Connolly <st...@gmail.com>.

When I last checked, the code import is still waiting for PMC approval... I
suspect that until the code has been imported there cannot be a release ;-)

On 30 September 2011 10:05, Mark Derricutt <ma...@talios.com> wrote:

> Jason - is there any further news on the Aether/Sisu front?  Really
> starting
> to get an itch for a 3.0.4 release - my manager this morning was having
> strange resolution issues that I traced to same issues I've been seeing
> with
> the currently shipped aether.
>
> Would be good to get a 3.0.4 release out with some updated plugin versions
> set as well ( the new wagon, archetype come to mind ).
>
> Mark
>
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
>
> On Wed, Sep 21, 2011 at 12:17 AM, Baptiste MATHUS <ml...@batmat.net> wrote:
>
> > To be sure, are you talking about renaming Aether packages to something
> > like
> > org.eclipse.aether?
> >
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Derricutt <ma...@talios.com>.

Jason - is there any further news on the Aether/Sisu front?  Really starting
to get an itch for a 3.0.4 release - my manager this morning was having
strange resolution issues that I traced to same issues I've been seeing with
the currently shipped aether.

Would be good to get a 3.0.4 release out with some updated plugin versions
set as well ( the new wagon, archetype come to mind ).

Mark

-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Wed, Sep 21, 2011 at 12:17 AM, Baptiste MATHUS <ml...@batmat.net> wrote:

> To be sure, are you talking about renaming Aether packages to something
> like
> org.eclipse.aether?
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Baptiste MATHUS <ml...@batmat.net>.

Le 17 sept. 2011 17:54, "Jason van Zyl" <ja...@maven.org> a écrit :
>
> The latest is always available here:
>
> http://eclipse.org/proposals/technology.aether/
>
> We still have to refactor the package names as well which we are going to
do next week.

To be sure, are you talking about renaming Aether packages to something like
org.eclipse.aether?

That would be the opposite of what some days ago you said you think would be
possible: keep package names as-is.

So, this hasn't been possible?

Cheers.

-- 
Baptiste

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

Ok. Thanks for this update.
We 'll be patient ....

Arnaud

Le 17 sept. 2011 à 17:53, Jason van Zyl <ja...@maven.org> a écrit :

> The latest is always available here:
>
> http://eclipse.org/proposals/technology.aether/
>
> We still have to refactor the package names as well which we are going to do next week. We've released Aether 1.13 and Sisu 2.3.0 so we can use those as well if we want. If you want to stick with the proper Eclipse releases then it comes when it comes.
>
> I believe last week the Eclipse IT folks were installing new hardware and pre-emptively taking security measures because of the security vulnerability in Apache HTTPD and kernel.org hack. There is also a list of projects waiting to provisioned so we're in line with everyone else. If folks are in a rush use Aether 1.13 and Sisu 2.3.0, if not then just be patient. Sometimes projects get provisioned the day the request goes in, sometimes it's 2-3 weeks. Just depends what else is going on. It's only been 8 days so far since I made the provisioning request.
>
> On Sep 17, 2011, at 11:25 AM, Arnaud Héritier wrote:
>
>> Hi Jason (and others aether/sisu commiters)
>>
>> Do you have some news ( am I the only one to cross users waiting for new
>> releases to show that our project is always alive?)
>>
>> Is the eclipse infrastructure so slow to create new projects ? I may
>> understand that these little libraries aren't critical (nowadays) for the
>> eclipse ecosystem but for us it is ...
>>
>> Cheers
>>
>> Arnaud
>>
>> On Thursday, September 8, 2011, Jason van Zyl <ja...@maven.org> wrote:
>>> The creation review has gone through for both Aether and Sisu. I have also
>> just submitted the project provisioning requests.
>>>
>>> I'll work with Denis at Eclipse to get the provisioning done as quickly as
>> possible so we can do the necessary work to run out releases of Sisu and
>> Aether and therefore Maven 3.0.4.
>>>
>>> On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:
>>>
>>>> The creation reviews for Sisu and Aether have been started:
>>>>
>>>> http://eclipse.org/proposals/technology.aether/
>>>> http://eclipse.org/proposals/technology.sisu/
>>>>
>>>> They will both finish on September 7th.
>>>>
>>>> When finished we'll turn out a release ASAP.
>>>>
>>>> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Janet just finished the trademark review and everything is clear. Wayne
>>>>>> Beaton and I both forgot about starting the trademark review and it's
>>>>>> required before the project creation review can start. The project
>> creation
>>>>>> review will start next week.
>>>>>>
>>>>>
>>>>> Ok, thus the ball is on your side now.
>>>>>
>>>>> Thx
>>>>>
>>>>> Arnaud
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder,  Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> What matters is not ideas, but the people who have them. Good people can
>> fix bad ideas, but good ideas can't save bad people.
>>>>
>>>> -- Paul Graham
>>>>
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> We all have problems. How we deal with them is a measure of our worth.
>>>
>>> -- Unknown
>>>
>>>
>>>
>>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> Our achievements speak for themselves. What we have to keep track
> of are our failures, discouragements and doubts. We tend to forget
> the past difficulties, the many false starts, and the painful
> groping. We see our past achievements as the end result of a
> clean forward thrust, and our present difficulties as
> signs of decline and decay.
>
> -- Eric Hoffer, Reflections on the Human Condition
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

The latest is always available here: 

http://eclipse.org/proposals/technology.aether/

We still have to refactor the package names as well which we are going to do next week. We've released Aether 1.13 and Sisu 2.3.0 so we can use those as well if we want. If you want to stick with the proper Eclipse releases then it comes when it comes. 

I believe last week the Eclipse IT folks were installing new hardware and pre-emptively taking security measures because of the security vulnerability in Apache HTTPD and kernel.org hack. There is also a list of projects waiting to provisioned so we're in line with everyone else. If folks are in a rush use Aether 1.13 and Sisu 2.3.0, if not then just be patient. Sometimes projects get provisioned the day the request goes in, sometimes it's 2-3 weeks. Just depends what else is going on. It's only been 8 days so far since I made the provisioning request.

On Sep 17, 2011, at 11:25 AM, Arnaud Héritier wrote:

> Hi Jason (and others aether/sisu commiters)
> 
> Do you have some news ( am I the only one to cross users waiting for new
> releases to show that our project is always alive?)
> 
> Is the eclipse infrastructure so slow to create new projects ? I may
> understand that these little libraries aren't critical (nowadays) for the
> eclipse ecosystem but for us it is ...
> 
> Cheers
> 
> Arnaud
> 
> On Thursday, September 8, 2011, Jason van Zyl <ja...@maven.org> wrote:
>> The creation review has gone through for both Aether and Sisu. I have also
> just submitted the project provisioning requests.
>> 
>> I'll work with Denis at Eclipse to get the provisioning done as quickly as
> possible so we can do the necessary work to run out releases of Sisu and
> Aether and therefore Maven 3.0.4.
>> 
>> On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:
>> 
>>> The creation reviews for Sisu and Aether have been started:
>>> 
>>> http://eclipse.org/proposals/technology.aether/
>>> http://eclipse.org/proposals/technology.sisu/
>>> 
>>> They will both finish on September 7th.
>>> 
>>> When finished we'll turn out a release ASAP.
>>> 
>>> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Janet just finished the trademark review and everything is clear. Wayne
>>>>> Beaton and I both forgot about starting the trademark review and it's
>>>>> required before the project creation review can start. The project
> creation
>>>>> review will start next week.
>>>>> 
>>>> 
>>>> Ok, thus the ball is on your side now.
>>>> 
>>>> Thx
>>>> 
>>>> Arnaud
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>> 
>>> What matters is not ideas, but the people who have them. Good people can
> fix bad ideas, but good ideas can't save bad people.
>>> 
>>> -- Paul Graham
>>> 
>>> 
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> We all have problems. How we deal with them is a measure of our worth.
>> 
>> -- Unknown
>> 
>> 
>> 
>> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

 -- Eric Hoffer, Reflections on the Human Condition

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

Hi Jason (and others aether/sisu commiters)

 Do you have some news ( am I the only one to cross users waiting for new
releases to show that our project is always alive?)

 Is the eclipse infrastructure so slow to create new projects ? I may
understand that these little libraries aren't critical (nowadays) for the
eclipse ecosystem but for us it is ...

Cheers

Arnaud

On Thursday, September 8, 2011, Jason van Zyl <ja...@maven.org> wrote:
> The creation review has gone through for both Aether and Sisu. I have also
just submitted the project provisioning requests.
>
> I'll work with Denis at Eclipse to get the provisioning done as quickly as
possible so we can do the necessary work to run out releases of Sisu and
Aether and therefore Maven 3.0.4.
>
> On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:
>
>> The creation reviews for Sisu and Aether have been started:
>>
>> http://eclipse.org/proposals/technology.aether/
>> http://eclipse.org/proposals/technology.sisu/
>>
>> They will both finish on September 7th.
>>
>> When finished we'll turn out a release ASAP.
>>
>> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
>>
>>>>
>>>>
>>>>
>>>> Janet just finished the trademark review and everything is clear. Wayne
>>>> Beaton and I both forgot about starting the trademark review and it's
>>>> required before the project creation review can start. The project
creation
>>>> review will start next week.
>>>>
>>>
>>> Ok, thus the ball is on your side now.
>>>
>>> Thx
>>>
>>> Arnaud
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.
>>
>> -- Paul Graham
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> We all have problems. How we deal with them is a measure of our worth.
>
>  -- Unknown
>
>
>
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

The creation review has gone through for both Aether and Sisu. I have also just submitted the project provisioning requests.

I'll work with Denis at Eclipse to get the provisioning done as quickly as possible so we can do the necessary work to run out releases of Sisu and Aether and therefore Maven 3.0.4.

On Aug 31, 2011, at 10:23 AM, Jason van Zyl wrote:

> The creation reviews for Sisu and Aether have been started:
> 
> http://eclipse.org/proposals/technology.aether/
> http://eclipse.org/proposals/technology.sisu/
> 
> They will both finish on September 7th.
> 
> When finished we'll turn out a release ASAP.
> 
> On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:
> 
>>> 
>>> 
>>> 
>>> Janet just finished the trademark review and everything is clear. Wayne
>>> Beaton and I both forgot about starting the trademark review and it's
>>> required before the project creation review can start. The project creation
>>> review will start next week.
>>> 
>> 
>> Ok, thus the ball is on your side now.
>> 
>> Thx
>> 
>> Arnaud
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. 
> 
> -- Paul Graham
> 
> 
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

The creation reviews for Sisu and Aether have been started:

http://eclipse.org/proposals/technology.aether/
http://eclipse.org/proposals/technology.sisu/

They will both finish on September 7th.

When finished we'll turn out a release ASAP.

On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:

>> 
>> 
>> 
>> Janet just finished the trademark review and everything is clear. Wayne
>> Beaton and I both forgot about starting the trademark review and it's
>> required before the project creation review can start. The project creation
>> review will start next week.
>> 
> 
> Ok, thus the ball is on your side now.
> 
> Thx
> 
> Arnaud

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. 

 -- Paul Graham

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 28, 2011, at 8:11 AM, Arnaud Héritier wrote:

>> 
>> 
>> 
>> Janet just finished the trademark review and everything is clear. Wayne
>> Beaton and I both forgot about starting the trademark review and it's
>> required before the project creation review can start. The project creation
>> review will start next week.
>> 
> 
> Ok, thus the ball is on your side now.
> 

I'll keep you posted on the creation review process, historically it's never taken longer than a week. 

Thanks for driving this to completion Arnaud.

> Thx
> 
> Arnaud

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.

 -- Buddha

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

>
>
>
> Janet just finished the trademark review and everything is clear. Wayne
> Beaton and I both forgot about starting the trademark review and it's
> required before the project creation review can start. The project creation
> review will start next week.
>

Ok, thus the ball is on your side now.

Thx

Arnaud

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Jason van Zyl <ja...@maven.org>.

On Aug 27, 2011, at 5:30 AM, Arnaud Héritier wrote:

> Hi all
> 
>  Re-reading the thread I saw I forgot to vote for it. Thus it has my +1
>  For now we have 9 binding votes
> (Arnaud,Kristian,Ralph,Hervé,Dennis,Wayne,John,Stephen,Barrie) and 4 non
> binding votes (Anders,Baptiste,Manfred,Mark) in favor to use as Maven core
> dependencies SISU and AETHER libraries published under EPL 1.0 License and
> released under eclipse.org governance
>  Thus I said that the vote ended last wednesday but for now we have not
> enough binding votes as we are 22 PMCs ([1]).
>  <<< We need 3 more PMCs votes to have a majority of PMCs([2]) >>>
> 
>  Otherwise, Jason and other committers on these projects on Eclipse side,
> do you have some news/delays to give to have new releases of Sisu and Aether
> under the Eclipse umbrella ?
> 

Janet just finished the trademark review and everything is clear. Wayne Beaton and I both forgot about starting the trademark review and it's required before the project creation review can start. The project creation review will start next week.

>  Cheers,
> 
> Arnaud
> 
> [1] http://people.apache.org/committers-by-project.html#maven-pmc
> [2] http://maven.apache.org/developers/dependency-policies.html
> 
> On Sat, Aug 20, 2011 at 8:33 AM, Mark Derricutt <ma...@talios.com> wrote:
> 
>> +1 Non Binding.
>> 
>> On 18/08/2011, at 9:23 PM, Arnaud Héritier wrote:
>> 
>>> [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
>> libraries
>>> published under EPL 1.0 License and released under eclipse.orggovernance
>> 
>> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

{script:nopre:"/Users/jvanzyl/signature/signature.sh"}

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Arnaud Héritier <ah...@gmail.com>.

Hi all

  Re-reading the thread I saw I forgot to vote for it. Thus it has my +1
  For now we have 9 binding votes
(Arnaud,Kristian,Ralph,Hervé,Dennis,Wayne,John,Stephen,Barrie) and 4 non
binding votes (Anders,Baptiste,Manfred,Mark) in favor to use as Maven core
dependencies SISU and AETHER libraries published under EPL 1.0 License and
released under eclipse.org governance
  Thus I said that the vote ended last wednesday but for now we have not
enough binding votes as we are 22 PMCs ([1]).
  <<< We need 3 more PMCs votes to have a majority of PMCs([2]) >>>

  Otherwise, Jason and other committers on these projects on Eclipse side,
do you have some news/delays to give to have new releases of Sisu and Aether
under the Eclipse umbrella ?

  Cheers,

Arnaud

[1] http://people.apache.org/committers-by-project.html#maven-pmc
[2] http://maven.apache.org/developers/dependency-policies.html

On Sat, Aug 20, 2011 at 8:33 AM, Mark Derricutt <ma...@talios.com> wrote:

> +1 Non Binding.
>
> On 18/08/2011, at 9:23 PM, Arnaud Héritier wrote:
>
> >  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
> libraries
> > published under EPL 1.0 License and released under eclipse.orggovernance
>
>

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Mark Derricutt <ma...@talios.com>.

+1 Non Binding.

On 18/08/2011, at 9:23 PM, Arnaud Héritier wrote:

>  [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries
> published under EPL 1.0 License and released under eclipse.org governance

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

Posted by Baptiste MATHUS <ml...@batmat.net>.

+1 (non-binding).

-- 
Baptiste
Le 18 août 2011 11:25, "Arnaud Héritier" <ah...@gmail.com> a écrit :
> Hi all,
>
> Thus as decided with Mark and Kristian I relaunch a new vote with a better
> scope about what we are voting for.
>
> Next releases of SISU and Aether will be released at Eclipse.org under EPL
> 1.0 license.
> Before they were published under ASL or dual ASL/EPL licenses thus as
> defined in our policy [1] this change put them in Category B [2] and we
need
> to validate this change by a vote with a majority of the PMC in favor (but
> the vote is open to everybody).
> I push only one vote for both dependencies as for now I see no reason to
> accept one and not the other.
> This vote will be open for 6 days as we are in august (If we have not
> enough votes at the end of next wednesday will see if we really need to
> extend it).
>
> The vote :
>
> [+1] I'm in favor to use as Maven core dependencies SISU and AETHER
libraries
> published under EPL 1.0 License and released under eclipse.org governance
> [+0] No opinion, do what you want.
> [-1] I'm against because .... (please elaborate)
>
> Arnaud
>
> [1] http://maven.apache.org/developers/dependency-policies.html
> [2] http://www.apache.org/legal/resolved.html#category-b