release button in project group page.

Hi, The release button of the project group page only works if all projects in the group have the same parent and the parent is in the group. Why doesn't it make a release of all projects in the group ? I think that it should work as the build all projects button. Benoit.

integration tests in 2.0.x. was: [continuum] BUILD FAILURE: Integration Test Executor

This test seems to work fine in my side. May it be that the 2.0.9 used is not properly built? should I force a build in maven-core? On Thu, Mar 1, 0008 at 10:18 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Online report :

Re: [vote] Release Maven Shade plugin 1.0

+1 Le dimanche 2 mars 2008, Brett Porter a écrit : Hi, The Shade plugin is ready to be released. This is needed for the 2.0.9 release as well. We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName= Htmlversion=13994 The remaining issues in JIRA are

Re: [vote] Release Maven Shade plugin 1.0

+1 for the artifact But -0 for the documentation. Any reasons why the layout is not standard? Cheers, Vincent 2008/3/1, Brett Porter [EMAIL PROTECTED]: Hi, The Shade plugin is ready to be released. This is needed for the 2.0.9 release as well. We solved 6 issues:

Re: svn commit: r620419 - /maven/core-integration-testing/trunk/core-integration-tests/src/test/java/org/apache/maven/integrationtests/IntegrationTestSuite.java

I fixed the test in r630474 (a conflict with wrong manifest in Surefire 2.4, caused by maven-shade-plugin, which is fixed for the release currently being voted on). Now, I don't understand the comment in code: MavenITmng1412DependenciesOrderTest.class ); -- MNG-1412 -- this is a poorly

Re: [vote] Release Maven Shade plugin 1.0

+1 Fabrice On Sun, Mar 2, 2008 at 4:20 AM, Brett Porter [EMAIL PROTECTED] wrote: Hi, The Shade plugin is ready to be released. This is needed for the 2.0.9 release as well. We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName=Htmlversion=13994

Open call for Papers - ApacheCon US 2008

Open Call for Papers for ApacheCon US 2008 !REMINDER: this will be a short CFP, ending on 3 April, so please be sure to get your CFP submissions in soon! The Apache Software Foundation (ASF) invites submissions to its official users' conference, ApacheCon US 2008, held 3 November through

Re: svn commit: r632588 - /maven/shared/trunk/maven-toolchain/

Is this the home of the code that is currently being voted on? If so then it shouldn't be removed. [EMAIL PROTECTED] wrote: Author: mkleint Date: Sat Mar 1 05:07:10 2008 New Revision: 632588 URL: http://svn.apache.org/viewvc?rev=632588view=rev Log: delete maven-toolchain from shared Removed:

Re: svn commit: r632588 - /maven/shared/trunk/maven-toolchain/

On Sun, Mar 2, 2008 at 7:50 AM, Dennis Lundberg [EMAIL PROTECTED] wrote: Is this the home of the code that is currently being voted on? If so then it shouldn't be removed. Here's the tag that goes with the vote thread: http://svn.apache.org/repos/asf/maven/shared/tags/maven-toolchain-1.0/ I

Re: svn commit: r632588 - /maven/shared/trunk/maven-toolchain/

Wendy Smoak wrote: On Sun, Mar 2, 2008 at 7:50 AM, Dennis Lundberg [EMAIL PROTECTED] wrote: Is this the home of the code that is currently being voted on? If so then it shouldn't be removed. Here's the tag that goes with the vote thread:

Re: integration tests in 2.0.x. was: [continuum] BUILD FAILURE: Integration Test Executor

Something is wrong with the environment - if you scroll to the start it is trying to use Maven 2.0.7 to run the tests. I'll take a look. - Brett On 02/03/2008, at 7:05 PM, Carlos Sanchez wrote: This test seems to work fine in my side. May it be that the 2.0.9 used is not properly built?

Re: svn commit: r620419 - /maven/core-integration-testing/trunk/core-integration-tests/src/test/java/org/apache/maven/integrationtests/IntegrationTestSuite.java

Sorry, I should have removed the comment yesterday - I re-enabled the test since you'd earlier fixed it. Done now. - Brett On 02/03/2008, at 10:56 PM, Hervé BOUTEMY wrote: I fixed the test in r630474 (a conflict with wrong manifest in Surefire 2.4, caused by maven-shade-plugin, which is

Re: [POLL] Maven outreach

I'm helping out in Commons. Wendy Smoak wrote: I've been monitoring the [EMAIL PROTECTED] list for a while and have recently gotten more involved trying to make sure ASF releases are correct both from a Maven perspective and from an ASF policy one, with pgp signatures, etc. (Thanks to Carlos

[POLL] Maven outreach

I've been monitoring the [EMAIL PROTECTED] list for a while and have recently gotten more involved trying to make sure ASF releases are correct both from a Maven perspective and from an ASF policy one, with pgp signatures, etc. (Thanks to Carlos for doing the lion's share of the repository work--

Re: svn commit: r518309 - /maven/plugins/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java

Brian and Vincent, are you advocating removing just the one line that added @aggregator, or the entire change related to MJAVADOC-104? Carlos, any thoughts on this? -- Wendy On Thu, Feb 28, 2008 at 9:55 PM, Brian E. Fox [EMAIL PROTECTED] wrote: I say pull the aggregation out (MJAVADOC-104)

RE: svn commit: r518309 - /maven/plugins/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java

The problem is @aggregator, but the quickest and safest is to revert the whole change since it likely expects @aggregator. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Sunday, March 02, 2008 5:11 PM To: Maven Developers List Subject: Re: svn commit: r518309 -

Restriction.java hashCode and equals not merged into 2.0.x

Any reason why revision 614706 from John Casey with Restriction.java hashCode and equals should not be merged in the 2.0.x branch ? -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride