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

[Kristian Rosenvold]

Den 17.08.2011 16:19, skrev Arnaud HERITIER:

Hi all,

   Next releases of SISU and Aether will be done 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 1 week 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.
   [+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



Arnaud,

I would really appreciate it if you cancelled this vote and rescheduled 
a vote
that specifically requires eclipse.org governance of SISU and Aether, 
not just epl.


Kristian


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

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

[Arnaud Héritier]

ok, you're right that it wasn't clear in vote options but I said it in the
first sentence.
It is effectively what I had in mind (EPL at Eclipse.org)
Others are agree to restart ?


On Thu, Aug 18, 2011 at 10:22 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:

> Den 17.08.2011 16:19, skrev Arnaud HERITIER:
>
>  Hi all,
>>
>>   Next releases of SISU and Aether will be done 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 1 week 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.
>>   [+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
>>
>>
> Arnaud,
>
> I would really appreciate it if you cancelled this vote and rescheduled a
> vote
> that specifically requires eclipse.org governance of SISU and Aether, not
> just epl.
>
> Kristian
>
>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

[Mark Struberg]

yes, please restart with the clarified phrasing (as we already voted explicitly 
against this very topic).

LieGrue,
strub 

--- On Thu, 8/18/11, Arnaud Héritier  wrote:

> From: Arnaud Héritier 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011, 8:49 AM
> ok, you're right that it wasn't clear
> in vote options but I said it in the
> first sentence.
> It is effectively what I had in mind (EPL at Eclipse.org)
> Others are agree to restart ?
> 
> 
> On Thu, Aug 18, 2011 at 10:22 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com>
> wrote:
> 
> > Den 17.08.2011 16:19, skrev Arnaud HERITIER:
> >
> >  Hi all,
> >>
> >>   Next releases of SISU and Aether
> will be done 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 1 week
> 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.
> >>   [+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
> >>
> >>
> > Arnaud,
> >
> > I would really appreciate it if you cancelled this
> vote and rescheduled a
> > vote
> > that specifically requires eclipse.org governance of
> SISU and Aether, not
> > just epl.
> >
> > Kristian
> >
> >
> >
> >
> --**--**-
> > To unsubscribe, e-mail: 
> > dev-unsubscribe@maven.apache.**org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

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

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

[Arnaud Héritier]

ok thus the vote is cancelled
I with relaunch it with the good options.
Nothing else to improve in it otherwise ( to not restart 4 times) ?

Arnaud

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

> yes, please restart with the clarified phrasing (as we already voted
> explicitly against this very topic).
>
> LieGrue,
> strub
>
> --- On Thu, 8/18/11, Arnaud Héritier  wrote:
>
> > From: Arnaud Héritier 
> > Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven
> core with EPL licenses
> > To: "Maven Developers List" 
> > Date: Thursday, August 18, 2011, 8:49 AM
> > ok, you're right that it wasn't clear
> > in vote options but I said it in the
> > first sentence.
> > It is effectively what I had in mind (EPL at Eclipse.org)
> > Others are agree to restart ?
> >
> >
> > On Thu, Aug 18, 2011 at 10:22 AM, Kristian Rosenvold <
> > kristian.rosenv...@gmail.com>
> > wrote:
> >
> > > Den 17.08.2011 16:19, skrev Arnaud HERITIER:
> > >
> > >  Hi all,
> > >>
> > >>   Next releases of SISU and Aether
> > will be done 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 1 week
> > 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.
> > >>   [+0] No opinion, do what you
> > want.
> > >>   [-1] I'm against because 
> > (please elaborate)
> > >>
> > >> Arnaud
> > >>
> > >> [1] http://maven.apache.org/**developers/dependency-**policies.html<
> http://maven.apache.org/developers/dependency-policies.html>
> > >> [2] http://www.apache.org/legal/**resolved.html#category-b<
> http://www.apache.org/legal/resolved.html#category-b>
> > >>
> > >>
> > > Arnaud,
> > >
> > > I would really appreciate it if you cancelled this
> > vote and rescheduled a
> > > vote
> > > that specifically requires eclipse.org governance of
> > SISU and Aether, not
> > > just epl.
> > >
> > > Kristian
> > >
> > >
> > >
> > >
> > --**--**-
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> dev-unsubscr...@maven.apache.org>
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

[PATCH] Maven PMD Plugin / MPMD-127 - Report cannot correctly handle external PMD ruleset as exported by Sonar QA Dashboard

[Tjerk Stroband]

Hi all,

We're using the Maven Site to generate and publish to our intranet. The PMD 
report provides valuable intel on project and code health and we've been using 
it quite successfully for a long time. Recently we decided to introduce Sonar 
to provide additional metrics, trend insight, etc. Sonar lets us 'manage' 
violations in a central repository and publishes the PMD rules-config on a url. 
Unfortunately this results in a temporary filename that contains illegal 
characters.

http://jira.codehaus.org/browse/MPMD-127

I've created a patch that replaces these characters with underscores and 
includes a unit-test to verify correct file naming. It's attached to the issue 
(and this email).

Can anyone integrate the patch into 2.6-SNAPSHOT? I would gladly commit it 
myself but I am not a listed developer on the project.
It's not the most popular issue, nor is it blocking but it would make 3 voters 
and 4 watchers very happy...

Thank you in advance,
Best regards,

Tjerk Stroband



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

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

[Kristian Rosenvold]

Nah; with the change I think this is a nice vote, and it's about time we 
have it!


Kristian

Den 18.08.2011 11:01, skrev Arnaud Héritier:

ok thus the vote is cancelled
I with relaunch it with the good options.
Nothing else to improve in it otherwise ( to not restart 4 times) ?

Arnaud

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


yes, please restart with the clarified phrasing (as we already voted
explicitly against this very topic).

LieGrue,
strub

--- On Thu, 8/18/11, Arnaud Héritier  wrote:


From: Arnaud Héritier
Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven

core with EPL licenses

To: "Maven Developers List"
Date: Thursday, August 18, 2011, 8:49 AM
ok, you're right that it wasn't clear
in vote options but I said it in the
first sentence.
It is effectively what I had in mind (EPL at Eclipse.org)
Others are agree to restart ?


On Thu, Aug 18, 2011 at 10:22 AM, Kristian Rosenvold<
kristian.rosenv...@gmail.com>
wrote:


Den 17.08.2011 16:19, skrev Arnaud HERITIER:

  Hi all,

   Next releases of SISU and Aether

will be done 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 1 week

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.
   [+0] No opinion, do what you

want.

   [-1] I'm against because 

(please elaborate)

Arnaud

[1] http://maven.apache.org/**developers/dependency-**policies.html<

http://maven.apache.org/developers/dependency-policies.html>

[2] http://www.apache.org/legal/**resolved.html#category-b<

http://www.apache.org/legal/resolved.html#category-b>



Arnaud,

I would really appreciate it if you cancelled this

vote and rescheduled a

vote
that specifically requires eclipse.org governance of

SISU and Aether, not

just epl.

Kristian





--**--**-

To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<

dev-unsubscr...@maven.apache.org>

For additional commands, e-mail: dev-h...@maven.apache.org



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





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

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

[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

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

[Kristian Rosenvold]

+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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [PATCH] Maven PMD Plugin / MPMD-127 - Report cannot correctly handle external PMD ruleset as exported by Sonar QA Dashboard

[Olivier Lamy]

Hello,
Done.

Thanks for the patch !
-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

2011/8/18 Tjerk Stroband :
> Hi all,
>
>
>
> We’re using the Maven Site to generate and publish to our intranet. The PMD
> report provides valuable intel on project and code health and we’ve been
> using it quite successfully for a long time. Recently we decided to
> introduce Sonar to provide additional metrics, trend insight, etc. Sonar
> lets us ‘manage’ violations in a central repository and publishes the PMD
> rules-config on a url. Unfortunately this results in a temporary filename
> that contains illegal characters.
>
>
>
> http://jira.codehaus.org/browse/MPMD-127
>
>
>
> I’ve created a patch that replaces these characters with underscores and
> includes a unit-test to verify correct file naming. It’s attached to the
> issue (and this email).
>
>
>
> Can anyone integrate the patch into 2.6-SNAPSHOT? I would gladly commit it
> myself but I am not a listed developer on the project.
>
> It’s not the most popular issue, nor is it blocking but it would make 3
> voters and 4 watchers very happy…
>
>
>
> Thank you in advance,
>
> Best regards,
>
>
>
> Tjerk Stroband
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

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

RE: [PATCH] Maven PMD Plugin / MPMD-127 - Report cannot correctly handle external PMD ruleset as exported by Sonar QA Dashboard

[Tjerk Stroband]

Many many thanks!!!

-Oorspronkelijk bericht-
Van: Olivier Lamy [mailto:ol...@apache.org] 
Verzonden: donderdag 18 augustus 2011 12:32
Aan: Maven Developers List
Onderwerp: Re: [PATCH] Maven PMD Plugin / MPMD-127 - Report cannot correctly 
handle external PMD ruleset as exported by Sonar QA Dashboard

Hello,
Done.

Thanks for the patch !
-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

2011/8/18 Tjerk Stroband :
> Hi all,
>
>
>
> We're using the Maven Site to generate and publish to our intranet. The PMD
> report provides valuable intel on project and code health and we've been
> using it quite successfully for a long time. Recently we decided to
> introduce Sonar to provide additional metrics, trend insight, etc. Sonar
> lets us 'manage' violations in a central repository and publishes the PMD
> rules-config on a url. Unfortunately this results in a temporary filename
> that contains illegal characters.
>
>
>
> http://jira.codehaus.org/browse/MPMD-127
>
>
>
> I've created a patch that replaces these characters with underscores and
> includes a unit-test to verify correct file naming. It's attached to the
> issue (and this email).
>
>
>
> Can anyone integrate the patch into 2.6-SNAPSHOT? I would gladly commit it
> myself but I am not a listed developer on the project.
>
> It's not the most popular issue, nor is it blocking but it would make 3
> voters and 4 watchers very happy...
>
>
>
> Thank you in advance,
>
> Best regards,
>
>
>
> Tjerk Stroband
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

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


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

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

[Anders Hammar]

+1 (non-binding)

/Anders

2011/8/18 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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: svn commit: r1158917 - in /maven/indexer/trunk/indexer-core/src: main/java/org/apache/maven/index/DefaultSearchEngine.java test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java

[Tamás Cservenák]

Hi Olivier,

the change
http://svn.apache.org/viewvc?view=revision&revision=1158917

while properly fixing the stuff mentioned in commit log, sneaks in
another change that is wrong.

The "searchFlat can return empty results with multiple index if the
first used returns empty result" fix is okay, and I agree with it
(removal of "return 0").

But, what is sneaked in wrt "duplicates" is wrong, and would violate
and even prevent some existing use cases. The passed in parameter
Collection is already a Set with proper Comparator that
is user selectable. In short, you set ArtifactInfo.VERSION_COMPARATOR
always, but that's maybe not what user wants.

To demonstrate, along with fix for your rev1158917 (it undoes that
solution with a Set) I committed an extensive UT demonstrating what
your fix was breaking (just re-implement your change wrt "duplicates"
and run the UT, will fail).

Never forget that Maven Indexer is not used in MRMs only, things like
IDE integrations are using it too, and those use cases are wildly
different from those used in MRMs.


The change is r1159159
http://svn.apache.org/viewvc?view=revision&revision=1159159


Thanks,
~t~


On Wed, Aug 17, 2011 at 11:16 PM,   wrote:
> Author: olamy
> Date: Wed Aug 17 21:16:25 2011
> New Revision: 1158917
>
> URL: http://svn.apache.org/viewvc?rev=1158917&view=rev
> Log:
> [MINDEXER-38] searchFlat can return empty results with multiple index if the 
> first used returns empty result
>
> Modified:
>    
> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>    
> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>
> Modified: 
> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
> URL: 
> http://svn.apache.org/viewvc/maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java?rev=1158917&r1=1158916&r2=1158917&view=diff
> ==
> --- 
> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>  (original)
> +++ 
> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>  Wed Aug 17 21:16:25 2011
> @@ -164,17 +164,27 @@ public class DefaultSearchEngine
>     {
>         int hitCount = 0;
>
> +        Set nonDuplicateResults = new TreeSet( 
> ArtifactInfo.VERSION_COMPARATOR );
> +
> +
>         for ( IndexingContext context : participatingContexts )
>         {
>             final TopScoreDocCollector collector = doSearchWithCeiling( req, 
> context.getIndexSearcher(), query );
>
> +            // olamy if the first context used doesn't find the other are 
> not used for search
> +            // so the result can probably returns duplicate as artifactInfo 
> doesn't implements hashCode/equals
> +            // so implements this in nonDuplicateResults
> +            /*
>             if ( collector.getTotalHits() == 0 )
>             {
>                 return 0;
>             }
> +            */
>
>             ScoreDoc[] scoreDocs = collector.topDocs().scoreDocs;
>
> +            // uhm btw hitCount contains dups
> +
>             hitCount += collector.getTotalHits();
>
>             int start = 0; // from == FlatSearchRequest.UNDEFINED ? 0 : from;
> @@ -192,11 +202,14 @@ public class DefaultSearchEngine
>
>                     artifactInfo.context = context.getId();
>
> -                    result.add( artifactInfo );
> +                    nonDuplicateResults.add( artifactInfo );
> +
>                 }
>             }
>         }
>
> +        result.addAll( nonDuplicateResults );
> +
>         return hitCount;
>     }
>
>
> Modified: 
> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
> URL: 
> http://svn.apache.org/viewvc/maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java?rev=1158917&r1=1158916&r2=1158917&view=diff
> ==
> --- 
> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>  (original)
> +++ 
> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>  Wed Aug 17 21:16:25 2011
> @@ -31,6 +31,7 @@ import org.codehaus.plexus.util.FileUtil
>
>  import java.io.File;
>  import java.util.ArrayList;
> +import java.util.Arrays;
>  import java.util.List;
>
>  /**
> @@ -70,10 +71,9 @@ public class SearchWithAnEmptyIndexTest
>         }
>     }
>
> -    public void testWithTwoContextWithOneEmpty()
> +    public void testWithTwoContextWithOneEmptyFirstInContextsListSearchFlat()
>         throws Exception
>     {
> -        createIndex( "src/test/repo-with-osgi", 
> "target/test/repo-with-osgi/", INDEX_ID1 );
>
>         String repoPath = "target/test/empty-repo-for-search

Re: svn commit: r1158917 - in /maven/indexer/trunk/indexer-core/src: main/java/org/apache/maven/index/DefaultSearchEngine.java test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java

[Olivier Lamy]

Hello,
Thanks for the review, the use cases and the explanation !

1 beer for you ! :-)

2011/8/18 Tamás Cservenák :
> Hi Olivier,
>
> the change
> http://svn.apache.org/viewvc?view=revision&revision=1158917
>
> while properly fixing the stuff mentioned in commit log, sneaks in
> another change that is wrong.
>
> The "searchFlat can return empty results with multiple index if the
> first used returns empty result" fix is okay, and I agree with it
> (removal of "return 0").
>
> But, what is sneaked in wrt "duplicates" is wrong, and would violate
> and even prevent some existing use cases. The passed in parameter
> Collection is already a Set with proper Comparator that
> is user selectable. In short, you set ArtifactInfo.VERSION_COMPARATOR
> always, but that's maybe not what user wants.
>
> To demonstrate, along with fix for your rev1158917 (it undoes that
> solution with a Set) I committed an extensive UT demonstrating what
> your fix was breaking (just re-implement your change wrt "duplicates"
> and run the UT, will fail).
>
> Never forget that Maven Indexer is not used in MRMs only, things like
> IDE integrations are using it too, and those use cases are wildly
> different from those used in MRMs.
>
>
> The change is r1159159
> http://svn.apache.org/viewvc?view=revision&revision=1159159
>
>
> Thanks,
> ~t~
>
>
> On Wed, Aug 17, 2011 at 11:16 PM,   wrote:
>> Author: olamy
>> Date: Wed Aug 17 21:16:25 2011
>> New Revision: 1158917
>>
>> URL: http://svn.apache.org/viewvc?rev=1158917&view=rev
>> Log:
>> [MINDEXER-38] searchFlat can return empty results with multiple index if the 
>> first used returns empty result
>>
>> Modified:
>>    
>> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>>    
>> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>>
>> Modified: 
>> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java?rev=1158917&r1=1158916&r2=1158917&view=diff
>> ==
>> --- 
>> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>>  (original)
>> +++ 
>> maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/DefaultSearchEngine.java
>>  Wed Aug 17 21:16:25 2011
>> @@ -164,17 +164,27 @@ public class DefaultSearchEngine
>>     {
>>         int hitCount = 0;
>>
>> +        Set nonDuplicateResults = new TreeSet( 
>> ArtifactInfo.VERSION_COMPARATOR );
>> +
>> +
>>         for ( IndexingContext context : participatingContexts )
>>         {
>>             final TopScoreDocCollector collector = doSearchWithCeiling( req, 
>> context.getIndexSearcher(), query );
>>
>> +            // olamy if the first context used doesn't find the other are 
>> not used for search
>> +            // so the result can probably returns duplicate as artifactInfo 
>> doesn't implements hashCode/equals
>> +            // so implements this in nonDuplicateResults
>> +            /*
>>             if ( collector.getTotalHits() == 0 )
>>             {
>>                 return 0;
>>             }
>> +            */
>>
>>             ScoreDoc[] scoreDocs = collector.topDocs().scoreDocs;
>>
>> +            // uhm btw hitCount contains dups
>> +
>>             hitCount += collector.getTotalHits();
>>
>>             int start = 0; // from == FlatSearchRequest.UNDEFINED ? 0 : from;
>> @@ -192,11 +202,14 @@ public class DefaultSearchEngine
>>
>>                     artifactInfo.context = context.getId();
>>
>> -                    result.add( artifactInfo );
>> +                    nonDuplicateResults.add( artifactInfo );
>> +
>>                 }
>>             }
>>         }
>>
>> +        result.addAll( nonDuplicateResults );
>> +
>>         return hitCount;
>>     }
>>
>>
>> Modified: 
>> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java?rev=1158917&r1=1158916&r2=1158917&view=diff
>> ==
>> --- 
>> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>>  (original)
>> +++ 
>> maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/SearchWithAnEmptyIndexTest.java
>>  Wed Aug 17 21:16:25 2011
>> @@ -31,6 +31,7 @@ import org.codehaus.plexus.util.FileUtil
>>
>>  import java.io.File;
>>  import java.util.ArrayList;
>> +import java.util.Arrays;
>>  import java.util.List;
>>
>>  /**
>> @@ -70,10 +71,9 @@ public class SearchWithAnEmptyIndexTest
>>         }
>>     }
>>
>> -    public void testWithTwoContextWithOneEmpty()

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

[Mark Struberg]

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  wrote:

> From: Anders Hammar 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011, 10:56 AM
> +1 (non-binding)
> 
> /Anders
> 
> 2011/8/18 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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
>

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

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

[Benson Margulies]

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  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  wrote:
>
>> From: Anders Hammar 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>>
>> /Anders
>>
>> 2011/8/18 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-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

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

[Daniel Kulp]

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  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  wrote:
> >> From: Anders Hammar 
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven
> >> core with EPL licenses - take 2 To: "Maven Developers List"
> >> 
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >> 
> >> /Anders
> >> 
> >> 2011/8/18 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-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
-- 
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com

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

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

[Mark Struberg]

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  wrote:

> From: Benson Margulies 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> 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 
> 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 
> wrote:
> >
> >> From: Anders Hammar 
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as
> dependencies of maven core with EPL licenses - take 2
> >> To: "Maven Developers List" 
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >>
> >> /Anders
> >>
> >> 2011/8/18 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-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
> >
> >
> -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
>

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

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

[Jason van Zyl]

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  wrote:
> 
>> From: Anders Hammar 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>> 
>> /Anders
>> 
>> 2011/8/18 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-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

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

[Benson Margulies]

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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Mark Struberg]

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  wrote:

> From: Jason van Zyl 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> 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 
> wrote:
> > 
> >> From: Anders Hammar 
> >> Subject: Re: [VOTE] Usage of Aether and Sisu as
> dependencies of maven core with EPL licenses - take 2
> >> To: "Maven Developers List" 
> >> Date: Thursday, August 18, 2011, 10:56 AM
> >> +1 (non-binding)
> >> 
> >> /Anders
> >> 
> >> 2011/8/18 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-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >> 
> >> 
> > 
> >
> -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
> 
> In short, man creates for him

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

[Mark Struberg]

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  wrote:

> From: Benson Margulies 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> 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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

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

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

[Jason van Zyl]

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  wrote:
> 
>> From: Jason van Zyl 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> 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 
>> wrote:
>>> 
 From: Anders Hammar 
 Subject: Re: [VOTE] Usage of Aether and Sisu as
>> dependencies of maven core with EPL licenses - take 2
 To: "Maven Developers List" 
 Date: Thursday, August 18, 2011, 10:56 AM
 +1 (non-binding)
 
 /Anders
 
 2011/8/18 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-unsubscr...@maven.a

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

[Jason van Zyl]

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  wrote:
>> 
>>> From: Jason van Zyl 
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>>> with EPL licenses - take 2
>>> To: "Maven Developers List" 
>>> 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 
>>> wrote:
 
> From: Anders Hammar 
> Subject: Re: [VOTE] Usage of Aether and Sisu as
>>> dependencies of maven core with EPL licenses - take 2
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011, 10:56 AM
> +1 (non-binding)
> 
> /Anders
> 
> 2011/8/18 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)
>> 
>> Ar

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

[Arnaud Héritier]

>
>
>
> > 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

[Olivier Lamy]

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 :
> 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  wrote:
>
>> From: Anders Hammar 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>>
>> /Anders
>>
>> 2011/8/18 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-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

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

[Jason van Zyl]

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

[Jason van Zyl]

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 :
>> 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  wrote:
>> 
>>> From: Anders Hammar 
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>>> with EPL licenses - take 2
>>> To: "Maven Developers List" 
>>> Date: Thursday, August 18, 2011, 10:56 AM
>>> +1 (non-binding)
>>> 
>>> /Anders
>>> 
>>> 2011/8/18 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-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

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

A party which is not afraid of letting culture,

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

[Kristian Rosenvold]

> 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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Ralph Goers]

+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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

I broke the build ;)

[Kristian Rosenvold]

By staging a dual release of maven-archiver and maven-jar-plugin. So now
you have 3 days to fix the adding of
https://repository.apache.org/content/groups/staging/ or whatever to
hudson ;)

Kristian



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

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

[Olivier Lamy]

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

2011/8/18 Jason van Zyl :
>
> 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 :
>>> 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  wrote:
>>>
 From: Anders Hammar 
 Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
 with EPL licenses - take 2
 To: "Maven Developers List" 
 Date: Thursday, August 18, 2011, 10:56 AM
 +1 (non-binding)

 /Anders

 2011/8/18 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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> 

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

[Jason van Zyl]

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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@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

[Mark Struberg]

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  wrote:

> From: Kristian Rosenvold 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> 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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

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

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

[Jason van Zyl]

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 :
>> 
>> 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 :
 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  wrote:
 
> From: Anders Hammar 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven 
> core with EPL licenses - take 2
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011, 10:56 AM
> +1 (non-binding)
> 
> /Anders
> 
> 2011/8/18 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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...

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

[Olivier Lamy]

2011/8/18 Jason van Zyl :
>
> 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 :
>>>
>>> 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 :
> 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  wrote:
>
>> From: Anders Hammar 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven 
>> core with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 10:56 AM
>> +1 (non-binding)
>>
>> /Anders
>>
>> 2011/8/18 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-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev

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

[Mark Struberg]

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  wrote:

> From: Olivier Lamy 
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
> with EPL licenses - take 2
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011, 2:34 PM
> 2011/8/18 Jason van Zyl :
> >
> > 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 :
> >>>
> >>> 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 :
> > 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
> 
> wrote:
> >
> >> From: Anders Hammar 
> >> Subject: Re: [VOTE] Usage of
> Aether and Sisu as dependencies of maven core with EPL
> licenses - take 2
> >> To: "Maven Developers List" 
> >> Date: Thursday, August 18, 2011,
> 10:56 AM
> >> +1 (non-binding)
> >>
> >> /Anders
> >>
> >> 2011/8/18 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 librari

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

[Jason van Zyl]

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  wrote:
> 
>> From: Olivier Lamy 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 2:34 PM
>> 2011/8/18 Jason van Zyl :
>>> 
>>> 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 :
> 
> 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 :
>>> 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
>> 
>> wrote:
>>> 
 From: Anders Hammar 
 Subject: Re: [VOTE] Usage of
>> Aether and Sisu as dependencies of maven core with EPL
>> licenses - take 2
 To: "Maven Developers List" 
 Date: Thursday, August 18, 2011,
>> 10:56 AM
 +1 (non-binding)
 
 /Anders
 
 2011/8/18 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

[VOTE] Release Maven Jar Plugin version 2.3.2 and maven-archiver version 2.4.2

[Kristian Rosenvold]

Hi,

The main intention of this release is to get java7 file attribute api's
in use, which can be a great performance improvment for java7 mac &
linux users. There should also be some improvement for 1.5/1.6 users,
and this release is java 1.5+.

These are totally new apis and I appreciate java7 users testing.


We solved 2 jar plugin issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=16000

We solved 3 maven-archiver issues (+ a whole lot of plexus-issues):
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15281

There are still a couple of jar-plugin issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&status=1

There are still a couple of maven-archiver issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MSHARED+AND+component+%3D+maven-archiver+AND+status+%3D+Open

Staging repo (contains both):
https://repository.apache.org/content/repositories/maven-053/

Staging sites (sync pending):
http://maven.apache.org/shared/maven-archiver-2.4.2/
http://maven.apache.org/plugins/maven-jar-plugin-2.3.2



Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

And here's mye +1,

Kristian




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

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

[Jason van Zyl]

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  wrote:
> 
>> From: Olivier Lamy 
>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>> with EPL licenses - take 2
>> To: "Maven Developers List" 
>> Date: Thursday, August 18, 2011, 2:34 PM
>> 2011/8/18 Jason van Zyl :
>>> 
>>> 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 :
> 
> 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 :
>>> 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
>> 
>> wrote:
>>> 
 From: Anders Hammar 
 Subject: Re: [VOTE] Usage of
>> Aether and Sisu as dependencies of maven core with EPL
>> licenses - take 2
 To: "Maven Developers List" 
 Date: Thursday, August 18, 2011,
>> 10:56 AM
 +1 (non-binding)
 
 /Anders
 
 2011/8/18 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

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

[Baptiste MATHUS]

+1 (non-binding).

-- 
Baptiste
Le 18 août 2011 11:25, "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

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

[Manfred Moser]

+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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


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

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

[Brian Fox]

I'd like to be added as well please.

On Thu, Aug 18, 2011 at 10:45 AM, Jason van Zyl  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  wrote:
>>
>>> From: Olivier Lamy 
>>> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core 
>>> with EPL licenses - take 2
>>> To: "Maven Developers List" 
>>> Date: Thursday, August 18, 2011, 2:34 PM
>>> 2011/8/18 Jason van Zyl :

 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 :
>>
>> 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 :
 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
>>> 
>>> wrote:

> From: Anders Hammar 
> Subject: Re: [VOTE] Usage of
>>> Aether and Sisu as dependencies of maven core with EPL
>>> licenses - take 2
> To: "Maven Developers List" 
> Date: Thursday, August 18, 2011,
>>> 10:56 AM
> +1 (non-binding)
>
> /Anders
>
> 2011/8/18 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
>>> bot

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

[John Casey]

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  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  wrote:


From: Olivier Lamy
Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with 
EPL licenses - take 2
To: "Maven Developers List"
Date: Thursday, August 18, 2011, 2:34 PM
2011/8/18 Jason van Zyl:


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:


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:

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


wrote:



From: Anders Hammar
Subject: Re: [VOTE] Usage of

Aether and Sisu as dependencies of maven core with EPL
licenses - take 2

To: "Maven Developers List"
Date: Thursday, August 18, 2011,

10:56 AM

+1 (non-binding)

/Anders

2011/8/18 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-unsubscr...@maven.apache.org
For additional commands, e-mail:

dev-h...@maven.apache.org







---

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

[Hervé BOUTEMY]

+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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [Vote] Release Maven/Maven Plugins/Maven Shared Components Parent POMs

[Hervé BOUTEMY]

Here is my +1

Hervé

Le lundi 15 août 2011, Hervé BOUTEMY a écrit :
> Hi,
> 
> These are parent POMs for Maven projects: version 21 for Maven parent,
> version 22 for Maven Plugins parent and version 17 for Maven Shared
> Components parent.
> 
> We solved 11/7/7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&v
> ersion=12316641
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&;
> version=12316642
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&;
> version=12316944
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-042/
> 
> Staging site, with pom.xml diff to previous version link (sync pending):
> http://maven.apache.org/pom/maven-21/
> http://maven.apache.org/pom/maven-plugins-22/
> http://maven.apache.org/pom/maven-shared-commonents-17/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org


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

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

[Jason van Zyl]

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  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  wrote:
 
> From: Olivier Lamy
> Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven 
> core with EPL licenses - take 2
> To: "Maven Developers List"
> Date: Thursday, August 18, 2011, 2:34 PM
> 2011/8/18 Jason van Zyl:
>> 
>> 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:
 
 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:
>> 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
> 
> wrote:
>> 
>>> From: Anders Hammar
>>> Subject: Re: [VOTE] Usage of
> Aether and Sisu as dependencies of maven core with EPL
> licenses - take 2
>>> To: "Maven Developers List"
>>> Date: Thursday, August 18, 2011,
> 10:56 AM
>>> +1 (non-binding)
>>> 
>>> /Anders
>>> 
>>> 2011/8/18 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.
 
>>>

[RESULT][Vote] Release Maven/Maven Plugins/Maven Shared Components Parent POMs

[Hervé BOUTEMY]

Hi,
The vote has passed with the following result :

+1 (binding): John Casey,  Mark Struberg, Stephen Connolly, Olivier Lamy, 
Vincent Siveton, Brett Porter, Hervé BOUTEMY

I will promote the artifacts to the central repo.

Hervé

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

[jira] Subscription: Design & Best Practices

[jira]

Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist

Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
https://jira.codehaus.org/browse/MNG-612
MNG-1950Ability to introduce new lifecycles phases
https://jira.codehaus.org/browse/MNG-1950
MNG-2381improved control over the repositories in the POM
https://jira.codehaus.org/browse/MNG-2381
MNG-1563how to write integration tests
https://jira.codehaus.org/browse/MNG-1563
MNG-2125[doc] when and how to define plugins in a pom
https://jira.codehaus.org/browse/MNG-2125
MNG-139 server definitions should be reusable - review use of repository IDs
https://jira.codehaus.org/browse/MNG-139
MNG-474 performance improvement for forked lifecycles
https://jira.codehaus.org/browse/MNG-474
MNG-1381best practices: testing strategies
https://jira.codehaus.org/browse/MNG-1381
MNG-4656Declarative plugins similar to "jsp tags" or "jsf composites"
https://jira.codehaus.org/browse/MNG-4656
MNG-4713${basedir} variable makes portable builds overly difficult
https://jira.codehaus.org/browse/MNG-4713
MNG-1569Make build process info read-only to mojos, and provide mechanism 
for explicit out-params for mojos to declare
https://jira.codehaus.org/browse/MNG-1569
MNG-416 best practices:  multiple profile deployments
https://jira.codehaus.org/browse/MNG-416
MNG-367 best practices: multi-user installation
https://jira.codehaus.org/browse/MNG-367
MNG-125 guarded mojo execution
https://jira.codehaus.org/browse/MNG-125
MNG-41  best practices: site management
https://jira.codehaus.org/browse/MNG-41
MNG-1441Starting thinking about a proper distributed repository mechanism a 
la CPAN
https://jira.codehaus.org/browse/MNG-1441
MNG-868 Use uniform format for  and other tags
https://jira.codehaus.org/browse/MNG-868
MNG-1425best practices: the location of configuration files vs resources
https://jira.codehaus.org/browse/MNG-1425
MNG-1463best practices: plugin inheritance for a multi project build
https://jira.codehaus.org/browse/MNG-1463
MNG-657 possible chicken and egg problem with extensions
https://jira.codehaus.org/browse/MNG-657
MNG-1867deprecate system scope, analyse other use cases
https://jira.codehaus.org/browse/MNG-1867
MNG-1423best practices: setting up multi-module build
https://jira.codehaus.org/browse/MNG-1423
MNG-1468best practices: version management in multi project builds
https://jira.codehaus.org/browse/MNG-1468

You may edit this subscription at:
https://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341&filterId=11471

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

Re: I broke the build ;)

[Kristian Rosenvold]

I had a small discussion with Tamas on IRC yesterday about this, and I 
did come to realize that the proper way to do this is to do a regular 
release of maven-archiver 2.4.2, then make a branch in svn for 
maven-jar-plugin 2.3.2. On the branch, update to maven-archiver 2.4.2 
and then release from the branch. In that way the build never breaks and 
CI does not need any staging dependencies.


In retrospect I did the next-best thing, which was a temporary revert of 
the upgrade on trunk. So I can procastinate/fear svn branches for a 
little longer ;)


Kristian



Den 18.08.2011 16:08, skrev Kristian Rosenvold:

By staging a dual release of maven-archiver and maven-jar-plugin. So now
you have 3 days to fix the adding of
https://repository.apache.org/content/groups/staging/ or whatever to
hudson ;)

Kristian





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