Re: Updating the release plan for Assembly Plugin
+1. Sounds reasonnable for me too to remove those beta/alpha. 2010/9/15 Dennis Lundberg denn...@apache.org: Hi I saw that John added http://jira.codehaus.org/browse/MASSEMBLY-502 with a wish for Java 1.5. This is fine, but I think we need to discuss the contents of the coming versions. Over the last year or so I've tried to get rid of as many alpha and beta plugins as possible. We are now down to only 4 remaining, and the Assembly plugin is one of them. In my opinion alpha and beta versions of plugins only adds to the version confusion for our users. Now to the Assembly plugin. Here's what we have in JIRA: 2.2-beta-6: 4 out of 23 issues fixed 2.2: 0 out of 14 issues fixed 2.3-beta-1: 0 out of 14 issues fixed I propose that we shuffle these around: - Skip 2.2-beta-6, the next version will be 2.2 - 2.2 will contain the 4 issues already solved for 2.2-beta-6, and anything else (small) that we can cram in there without disturbing too much. Remember that it won't be beta any more :-) - The version after that will be 2.3 (not a beta), which will require Java 1.5 - If necessary 2.2.x releases can be branched off, while trunk continues towards 2.3 Comments? -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0.1
+1 Thanks Dennis! -Lukas Dennis Lundberg wrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100styleName=Htmlversion=16674 There is still an issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12100status=1 Staging repo: https://repository.apache.org/content/repositories/maven-031/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0.1/ 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
relativePath in m3 release notes
Hi all, Just read the link provided in the previous mail about m3-rc1. About this parent pom resolution, I was aware Maven3 would now not resolve in the project if parent project is not found in the default relative path : ../pom.xml. But the comment here https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ParentPOMResolution says : Maven 3 no longer resolves parent POMs from the local project checkout unless the relativePath element is properly specified in the child POM Does it mean that relativePath must now be put *even if* the parent pom is in the default path? Cheers PS : IAsking this question on the dev list, since m3 is not yet released as final. But I you feel this kind of question should have be post on users list, just let me know and I will do so in the future. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC1
+1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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: [PLEASE TEST] Apache Maven 3.0-RC1
Hervé BOUTEMY wrote: is this a formal vote Neither in the mail's subject nor in its body did I refer to any vote. This is an attempt to collect feedback from a broad audience before we start the vote for 3.0, similar to what was done in the past [0]. Benjamin [0] http://www.mail-archive.com/us...@maven.apache.org/msg100482.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
mvn 2.2.1: How to modify modules to build inside a custom plugin (apis to use)
Apologies if this is not the correct mailing list - I thought the developers would be better suited to answering API questions. I am implementing a mojo plugin that has a selection of modules to build that were specified in a pom.xml. How do I invoke a reactor to execute my List of modules filtered from the original mavenProject.getModules() list ? So far I have: MavenExecutionRequest request = mavenSession.getRequest(); EventDispatcher dispatcher = session.getEventDispatcher() String event = MavenEvents.REACTOR_EXECUTION; dispatcher.dispatchStart( event, request.getBaseDirectory() ); // lifeCycleExecutor to execute? // logging? Or should I invoke the system command line version to execute mvn deploy and assume logging will be chained correctly to the plugin's session? Thanks in advance.
Re: relativePath in m3 release notes
Baptiste MATHUS wrote: Does it mean thatrelativePath must now be put *even if* the parent pom is in the default path? No, it means the effective value for relativePath should be correct, whether that value is given by the user or using the implicit default. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
+1, no problem. Tested multimodules build, on windows and AIX (ibm jvm), with and without // build activated. Congratulations for the work! 2010/9/16 Paul Merlin eska...@n0pe.org +1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Le Wed, 15 Sep 2010 22:34:47 +0200, Benjamin Bentmann benjamin.bentm...@udo.edu a écrit : works fine on our project (install + site) Tony ps: my first mail was lost ? Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: relativePath in m3 release notes
I agree with Baptiste that the explanation is ambiguous. I understand the same thing. Regards Jeff MAURY On Thu, Sep 16, 2010 at 11:30 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Baptiste MATHUS wrote: Does it mean thatrelativePath must now be put *even if* the parent pom is in the default path? No, it means the effective value for relativePath should be correct, whether that value is given by the user or using the implicit default. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Le Thu, 16 Sep 2010 11:53:45 +0200, Tony Chemit che...@codelutin.com a écrit : Le Wed, 15 Sep 2010 22:34:47 +0200, Benjamin Bentmann benjamin.bentm...@udo.edu a écrit : works fine on our project (install + site) + release :) (I just made one) Tony ps: my first mail was lost ? Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0.1
+1 Emmanuel On Wed, Sep 15, 2010 at 11:36 PM, Dennis Lundberg denn...@apache.orgwrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100styleName=Htmlversion=16674 There is still an issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12100status=1 Staging repo: https://repository.apache.org/content/repositories/maven-031/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
+1 Seems to work fine for me. On 09/15/2010 03:34 PM, Benjamin Bentmann wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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: maven-release-plugin release?
Brett Porter wrote: On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be good to get the release plugin to come along for the ride as well... Yah, I lost the window of opportunity I had originally, and things have kept coming up since. I'm getting back to it now... there were nearly 30 issues with recent patches on them that I'd like to have a quick look at, then try for the release again. Beyond that, there's another 30 issues marked as having patches that are somewhat older that would be worth going through and a number of highly voted issues that seem fixable. Might be good for a follow up release. There's also a regression reported in: http://jira.codehaus.org/browse/MNG-4687 - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0.1
+1 Vincent 2010/9/15 Dennis Lundberg denn...@apache.org: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100styleName=Htmlversion=16674 There is still an issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12100status=1 Staging repo: https://repository.apache.org/content/repositories/maven-031/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - 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] Release Maven Linkcheck Plugin version 1.0.1
+1 2010/9/15 Dennis Lundberg denn...@apache.org: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100styleName=Htmlversion=16674 There is still an issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12100status=1 Staging repo: https://repository.apache.org/content/repositories/maven-031/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Integration tests in the Apache Sling build are pretty consistently failing on 3.0-RC1 and 3.0-beta-3 in two different modules. Both pass consistently in 2.2.1. To reproduce: $ svn co http://svn.apache.org/repos/asf/sling/trunk $ mvn clean install In about 4 minutes (depending upon the state of your local repository), the module at installer/osgi/it will fail with about 20 test failures. From there, you can proceed by using -rf $ mvn -rf installer/jcr/jcrinstall clean install The next few modules will build until the last, final integration test module which fails with about 70 test failures. With 2.2.1, both sets of integration tests pass. Any clues as to what we should be looking for? The first set of failures are all pax exam tests. The second set are normal JUnit tests which run against a container started and stopped by Maven. Thanks, Justin On 09/15/2010 03:34 PM, Benjamin Bentmann wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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: [PLEASE TEST] Apache Maven 3.0-RC1
I have a plugin where I use the maven3 api. maven-beta-2, maven-beta-1, maven-alpha-6/7, worked maven-beta-3 gives Caused by: java.lang.NullPointerException at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:185) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:175) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:237) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:219) maven-RC1 gives Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.ProjectBuildingRequest.setForceUpdate(Z)Lorg/apache/maven/project/ProjectBuildingRequest; maybe I should not have used that ProjectBuilder, maybe that is not part of the public API, maybe I am the only one writing plugin with maven3 API - then never mind I fix it on my side. regards Kristian On Thu, Sep 16, 2010 at 3:13 PM, Baptiste MATHUS m...@batmat.net wrote: +1, no problem. Tested multimodules build, on windows and AIX (ibm jvm), with and without // build activated. Congratulations for the work! 2010/9/16 Paul Merlin eska...@n0pe.org +1 (non-binding) Tested corporate and oss projects. Did not test the release process. /Paul Quoting Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/mav en/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+N otes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversi on=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
no problems here so far. I was able to run the assembly plugin ITs without trouble, which is a change from beta-3...there seemed to be some problem with passing expressions in on the command-line in beta-3. At any rate, it looks good. On 9/15/10 4:34 PM, Benjamin Bentmann wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Justin Edelson wrote: Any clues as to what we should be looking for? Well, I would hope that the Sling guys now best what makes their tests fail. One thing I have seen in the past were projects having duplicate classes/resources on their class path and having a subtle dependency on their ordering for stuff to work. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
On 9/16/10 11:12 AM, Benjamin Bentmann wrote: Justin Edelson wrote: Any clues as to what we should be looking for? Well, I would hope that the Sling guys now best what makes their tests fail. Indeed we do. In this case, what's making the tests fail is using a different Maven version. One thing I have seen in the past were projects having duplicate classes/resources on their class path and having a subtle dependency on their ordering for stuff to work. Benjamin - 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: maven-release-plugin release?
Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_235494is not a workaround, but the right way to go. See also https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ParentPOMResolutionor http://docs.codehaus.org/display/MAVENUSER/Iron+Fist+of+Maven+3.0+transition+pack Cheers. 2010/9/16 Jörg Schaible joerg.schai...@gmx.de Brett Porter wrote: On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be good to get the release plugin to come along for the ride as well... Yah, I lost the window of opportunity I had originally, and things have kept coming up since. I'm getting back to it now... there were nearly 30 issues with recent patches on them that I'd like to have a quick look at, then try for the release again. Beyond that, there's another 30 issues marked as having patches that are somewhat older that would be worth going through and a number of highly voted issues that seem fixable. Might be good for a follow up release. There's also a regression reported in: http://jira.codehaus.org/browse/MNG-4687 - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: maven-release-plugin release?
Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Incorrect information on maven-archetype-plugin/source-repository.html
Dear All: Sorry to bother, but just wanted to let you know that on: http://maven.apache.org/archetype/maven-archetype-plugin/source-repository.html I believe all references to: http://svn.apache.org/viewvc/maven/archetype/tags/maven-archetype-2.0-alpha-5/maven-archetype-plugin should actually be: http://svn.apache.org/viewvc/maven/archetype/tags/maven-archetype-2.0-alpha-5/archetype-plugin Thank you for making a great product! Misha -- View this message in context: http://maven.40175.n5.nabble.com/Incorrect-information-on-maven-archetype-plugin-source-repository-html-tp2842656p2842656.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Fine here (tested on some corporate builds) Thanks (good job !) 2010/9/15 Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [Checkstyle plugin] possible release
I could do with this release too and am happy to perform it. Having a few problems updating my environment though; I'll send a separate mail. Mark On 13 September 2010 22:37, Olivier Lamy ol...@apache.org wrote: Hi, I will try to work on this at the end of the week (if no spare time issue :-) ). 2010/9/13 Dominique Jean-Prost dominique.jean-pr...@dexia-sofaxis.com: Hello, Could someone consider releasing checkstyle plugin 2.6 as there are no more pending issues please ? As I'm eagerly waiting for some fixes, I dared to write here. Thank you in advance. Dom -- View this message in context: http://maven.40175.n5.nabble.com/Checkstyle-plugin-possible-release-tp2837375p2837375.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - 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
Plugin deployment problems
Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
Works fine here. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0.1
+1 Hervé Le mercredi 15 septembre 2010, Dennis Lundberg a écrit : Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100styleName= Htmlversion=16674 There is still an issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12100st atus=1 Staging repo: https://repository.apache.org/content/repositories/maven-031/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0.1/ 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
Re: snapshot range changes in m3
+1 Thinking about it - I like the idea of a (for lack of a better name) ~/.m2/resolutions.xml that provides control over the resolver. First thoughts that come to mind: - missing or empty file - existing 2.x behaviour, -SNAPSHOTS resolved across the board. - profile based (optional?) Maybe something like: resolutions resolution groupIdcom.smxemail.*/groupId artifactId.*/artifactId snapshots enabledtrue/enabled /snapshots /resolution profiles profile idrelease/id resolutions resolution groupId.*/groupId artifactId.*/artifactId snapshots enabledfalse/enabled /snapshots /resolution /resolutions /profile /profiles /resolutions As much as I hate mavens use of elements only, the above conforms to the current standard - a somewhat mix between a dependency and a repository definition. I like the notion of enabling resolution based on profile, which is already an accepted way of dynamically altering pom resolution. What do you guys think of something like this? If something like this was adopted, would it be doable for 3.0? ( having no clue as to how many layers of maven these things affect ). mark -- Pull me down under... On Thu, Sep 16, 2010 at 1:10 AM, Jason van Zyl ja...@sonatype.com wrote: The approach that I could think of to sufficiently address this issue requires quite some rework of the settings.xml or better a different file in order to not break side-by-side use of Maven 2.x and 3.x. Given that we want to release 3.0 soon, I will probably just rollback the changes for MNG-3092 and restore 2.x behavior, i.e. always include snapshots in ranges, and postpone a more robust solution to 3.1. +1 This is just more consistent with 3.0 being backward compatible, and making the whole scenario of SNAPSHOTs for CI and integration and blocking them from releases will take some more thinking. Only one person has complained but I posit 95% of Maven users aren't going to try Maven 3.x until 3.0 is released.
Re: [PLEASE TEST] Apache Maven 3.0-RC1
I am getting: java.lang.ClassNotFoundException: javax.persistence.Entity from spring context initialization. Class not found varies depending on the order of spring dependencies, could be a Logger, etc. Same build works fine under 2.2.1. and 3.0-beta-2 I will create an issue if manage to localize into a test project, otherwise it's just a FYI. 2010/9/15 Benjamin Bentmannbenjamin.bentm...@udo.edu: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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: [PLEASE TEST] Apache Maven 3.0-RC1
Benjamin I just found this problem : http://jira.codehaus.org/browse/MNG-4813 It is failing for all alpha/beta I tested thus it isn't a problem in RC itself. It occurs with an old version of the jdocbook plugin we are always using in GateIn and few others projects. Arnaud Héritier Software Factory Manager http://www.exoplatform.com Phone : +33 (0)6 89 74 64 24 Skype : aheritier Twitter : @aheritier Blog : http://aheritier.net On Sep 15, 2010, at 10:34 PM, Benjamin Bentmann wrote: Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ Before reporting any issues found during testing, please be sure to have a close look at the compatibility notes for Maven 3.x: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes If you encounter unexpected build issues, please fill a report in JIRA that provides sufficient information to reproduce and analyze the issue: http://jira.codehaus.org/browse/MNG The fixes contained in this release candidate since the 3.0-beta-3 release can also be seen in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create Thanks, -The Maven team - 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
maven-remote-resources-plugin ignores offline?
I asked about this on the users list about a month ago and got no response. I think the maven-remote-resources-plugin has a problem. When I build for the first time in 24 hours with -o, I still get stuff like this: [INFO] --- maven-remote-resources-plugin:1.0:process (default) @ geronimo-jetty-web-cts --- [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] snapshot org.apache.geronimo.modules:geronimo-naming-builder:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo:geronimo:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.openwebbeans:openwebbeans-web:1.0.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.xbean:xbean-asm-shaded:3.8-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.modules:geronimo-jetty8-builder:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.modules:geronimo-aries-builder:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.plugins:aries:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.configs:welcome-jetty:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.plugins:welcome:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.framework:shutdown:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.modules:geronimo-persistence-jpa20-builder:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.plugins:openjpa2:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.configs:jsr88-war-configurer:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.framework:geronimo-shell:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.configs:connector-deployer-1_6:3.0-SNAPSHOT: checking for updates from nexus [INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking for updates from codehaus.snapshots [INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking for updates from apache.snapshots [INFO] snapshot org.apache.geronimo:geronimo:3.0-SNAPSHOT: checking for updates from codehaus.snapshots [INFO] snapshot org.apache.geronimo:geronimo:3.0-SNAPSHOT: checking for updates from apache.snapshots ... IIRC I get the same results with m-r-r-p v 1.1. When I don't have internet access, there's an extremely long delay (maybe a minute?) between each line. I get the same results with maven 2.2.1 and 3 beta 1. Does anyone else see this and/or think its a problem? So far I haven't located any of the code that might be responsible for this. thanks david jencks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-remote-resources-plugin ignores offline?
David Jencks wrote: I get the same results with maven 2.2.1 and 3 beta 1. 3.0-beta-1 was yesterday, so I recommend to try 3.0-RC1: https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/ If that also doesn't respect the offline mode, then I would appreciate some minimal example project to reproduce the issue such that it can be properly analyzed and eventually fixed. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC1
An odd thing I'm noticing trying to release some multi-module projects with
M3 nightlies:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project smx3.core: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare failed: For
artifact {org.apache.maven.plugins:maven-install-plugin:null:maven-plugin}:
The version cannot be empty. - [Help 1]
I don't declare or use the maven-install-plugin anywhere in my project so
I'm not sure why I would need to declare it ( mvn clean install works fine
).
Anyone else seen this? Or should I just bite the bullet and put in a
declaration of the install plugin and lock its version down?
Mark
--
Pull me down under...
On Thu, Sep 16, 2010 at 8:34 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive can
get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/
Before reporting any issues found during testing, please be sure to have a
close look at the compatibility notes for Maven 3.x:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
If you encounter unexpected build issues, please fill a report in JIRA that
provides sufficient information to reproduce and analyze the issue:
http://jira.codehaus.org/browse/MNG
The fixes contained in this release candidate since the 3.0-beta-3 release
can also be seen in JIRA:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-iversion=13142styleName=TextprojectId=10500Create=Create
Thanks,
-The Maven team
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. If I understand correctly, it's more that the release plugin doesn't yet understand relativePath/releativePath, which is something new in Maven 3 to represent no relative path for the warning? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[jira] Subscription: Design Best Practices
Issue Subscription
Filter: Design Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.org/browse/MNG-2381
MNG-2125[doc] when and how to define plugins in a pom
http://jira.codehaus.org/browse/MNG-2125
MNG-139 server definitions should be reusable - review use of repository IDs
http://jira.codehaus.org/browse/MNG-139
MNG-474 performance improvement for forked lifecycles
http://jira.codehaus.org/browse/MNG-474
MNG-1563how to write integration tests
http://jira.codehaus.org/browse/MNG-1563
MNG-1381best practices: testing strategies
http://jira.codehaus.org/browse/MNG-1381
MNG-1950Ability to introduce new lifecycles phases
http://jira.codehaus.org/browse/MNG-1950
MNG-4656Declarative plugins similar to jsp tags or jsf composites
http://jira.codehaus.org/browse/MNG-4656
MNG-4713${basedir} variable makes portable builds overly difficult
http://jira.codehaus.org/browse/MNG-4713
MNG-1468best practices: version management in multi project builds
http://jira.codehaus.org/browse/MNG-1468
MNG-1569Make build process info read-only to mojos, and provide mechanism
for explicit out-params for mojos to declare
http://jira.codehaus.org/browse/MNG-1569
MNG-416 best practices: multiple profile deployments
http://jira.codehaus.org/browse/MNG-416
MNG-367 best practices: multi-user installation
http://jira.codehaus.org/browse/MNG-367
MNG-125 guarded mojo execution
http://jira.codehaus.org/browse/MNG-125
MNG-41 best practices: site management
http://jira.codehaus.org/browse/MNG-41
MNG-1441Starting thinking about a proper distributed repository mechanism a
la CPAN
http://jira.codehaus.org/browse/MNG-1441
MNG-868 Use uniform format for properties and other tags
http://jira.codehaus.org/browse/MNG-868
MNG-1423best practices: setting up multi-module build
http://jira.codehaus.org/browse/MNG-1423
MNG-1425best practices: the location of configuration files vs resources
http://jira.codehaus.org/browse/MNG-1425
MNG-1463best practices: plugin inheritance for a multi project build
http://jira.codehaus.org/browse/MNG-1463
MNG-1867deprecate system scope, analyse other use cases
http://jira.codehaus.org/browse/MNG-1867
MNG-657 possible chicken and egg problem with extensions
http://jira.codehaus.org/browse/MNG-657
You may edit this subscription at:
http://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341filterId=11471
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?
Forwarding this question to dev list, since I don't really know. To me, catalog descriptor [1] should not contain goals or properties elements, but archetype descriptor [2] should have goals instead (it already has properties). Any objection if I remove goals and properties elements from catalog descriptor? Then I'll release maven-archetype-plugin 2.0 without this goals feature, which is not implemented: it will be postponed to 2.1+ Regards, Hervé [1] http://maven.apache.org/archetype/archetype-common/archetype-catalog.html [2] http://maven.apache.org/archetype/archetype-common/archetype- descriptor.html -- Message transmis -- Sujet : Re: archetype-catalog.xml and its properties and goals elements, what populates them? Date : jeudi 16 septembre 2010, 00:11:46 De : lukewpatterson lukewpatter...@gmail.com À : us...@maven.apache.org Anyone have any info/background on the goals and properties sections of archetype-catalog.xml ? -- View this message in context: http://maven.40175.n5.nabble.com/archetype- catalog-xml-and-its-properties-and-goals-elements-what-populates-them- tp2799170p2841463.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
