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
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
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é
---
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:
>
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
+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.
>
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 o
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
+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.
>>
+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 lic
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, Olivie
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 us
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
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
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
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
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 h
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
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 tom
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
+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.
> 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.
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
>
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 thi
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 governan
>
>
>
> > 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) shou
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. F
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 c
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
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.
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
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 Ec
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
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
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
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
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 tha
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, an
+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 p
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
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 proj
+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
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
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, A
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. Son
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 t
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:
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, s
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 val
49 matches
Mail list logo
