Plugin testing release for 3.1.1
Hi! With the 3.1.1 release of Maven coming up hopefully soon I would like to move forward with the plugin testing harness using it as well. Jason fixed it to work with 3.0 and requested the repo to be moved from svn to git so he can release 2.2 over a month ago. It seems like nothing happen on the infra side of things. Can somebody take this up and get it done asap. Or could I get some sort of access (maybe through the committer school) to do it myself at Apache? Worst case I could of course just temporarily fork it into my namespace and use it in the android maven plugin but I would rather not waste my time on that. manfred - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
Just a thought that comes to mind. I see just as this vote was raised a new maven-install-plugin was released, and a vote is also underway for an updated wagon release. Is it worth updating the default versions of plugins etc. to use these along with the 3.1.1 release? On 9/09/2013, at 1:07 AM, Jason van Zyl ja...@tesla.io wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team -- Mark Derricutt ( m...@talios.com ) — twitter: https://twitter.com/talios — podcast: http://www.illegalargument.com — blog: http://www.theoryinpractice.net — google+: http://gplus.to/talios signature.asc Description: Message signed with OpenPGP using GPGMail
RE: Plugin testing release for 3.1.1
I am looking for how to run a Mahout project on Maven, or how to run a Mahout project for clustering textual data. Can anyone help please? Regards, Tanveer Ahmad From: Manfred Moser manf...@simpligility.com Sent: 13 September 2013 05:05 To: Maven Developers List Subject: Plugin testing release for 3.1.1 Hi! With the 3.1.1 release of Maven coming up hopefully soon I would like to move forward with the plugin testing harness using it as well. Jason fixed it to work with 3.0 and requested the repo to be moved from svn to git so he can release 2.2 over a month ago. It seems like nothing happen on the infra side of things. Can somebody take this up and get it done asap. Or could I get some sort of access (maybe through the committer school) to do it myself at Apache? Worst case I could of course just temporarily fork it into my namespace and use it in the android maven plugin but I would rather not waste my time on that. manfred - 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: Plugin testing release for 3.1.1
Manfred if there is a problem is on the Apache side you should be able to make the change wheres the hangup I am not a committer so I have no way to do anything. Maybe I should become one.. manfred - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
Assuming that we need another vote, it is worth waiting to include Wagon 2.5 due to WAGON-381. I wouldn't upgrade the Install Plugin yet. First the Deploy Plugin should be released as well, so the installAtEnd and deployAtEnd chain is complete. With only the installAtEnd we can expect confusion. Robert Op Fri, 13 Sep 2013 07:59:58 +0200 schreef Mark Derricutt m...@talios.com: Just a thought that comes to mind. I see just as this vote was raised a new maven-install-plugin was released, and a vote is also underway for an updated wagon release. Is it worth updating the default versions of plugins etc. to use these along with the 3.1.1 release? On 9/09/2013, at 1:07 AM, Jason van Zyl ja...@tesla.io wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team -- Mark Derricutt ( m...@talios.com ) — twitter: https://twitter.com/talios — podcast: http://www.illegalargument.com — blog: http://www.theoryinpractice.net — google+: http://gplus.to/talios - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Plugin testing release for 3.1.1
Manfred if there is a problem is on the Apache side you should be able to make the change wheres the hangup ? Martin __ Date: Fri, 13 Sep 2013 00:05:23 -0400 Subject: Plugin testing release for 3.1.1 From: manf...@simpligility.com To: dev@maven.apache.org Hi! With the 3.1.1 release of Maven coming up hopefully soon I would like to move forward with the plugin testing harness using it as well. Jason fixed it to work with 3.0 and requested the repo to be moved from svn to git so he can release 2.2 over a month ago. It seems like nothing happen on the infra side of things. Can somebody take this up and get it done asap. Or could I get some sort of access (maybe through the committer school) to do it myself at Apache? Worst case I could of course just temporarily fork it into my namespace and use it in the android maven plugin but I would rather not waste my time on that. manfred - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE CANCELLED] Release Maven 3.1.1
We found issues with the release so it's cancel. I'll look into the issue Tamas pointed out and the issue Igor found with workspace dependency resolution as a result of trying to port m2e to 3.1.x. I'll try to fix these issues over the weekend and roll another release. On Sep 8, 2013, at 9:07 AM, Jason van Zyl ja...@tesla.io wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: [VOTE] Release Maven 3.1.1
On Sep 13, 2013, at 10:14 AM, Robert Scholte rfscho...@apache.org wrote: Assuming that we need another vote, it is worth waiting to include Wagon 2.5 due to WAGON-381. No, I would prefer to do another release and only fix what's necessary here. I'd still like to get to the point where we can do push button, mostly automated releases. To get there we need to release more often. There's one issue that Tamas pointed out that needs to be fixed, and we've discovered another issue in m2e while trying to make it use 3.1.x. So I'd like to focus on those issues and release again. I wouldn't upgrade the Install Plugin yet. First the Deploy Plugin should be released as well, so the installAtEnd and deployAtEnd chain is complete. With only the installAtEnd we can expect confusion. Robert Op Fri, 13 Sep 2013 07:59:58 +0200 schreef Mark Derricutt m...@talios.com: Just a thought that comes to mind. I see just as this vote was raised a new maven-install-plugin was released, and a vote is also underway for an updated wagon release. Is it worth updating the default versions of plugins etc. to use these along with the 3.1.1 release? On 9/09/2013, at 1:07 AM, Jason van Zyl ja...@tesla.io wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team -- Mark Derricutt ( m...@talios.com ) — twitter: https://twitter.com/talios — podcast: http://www.illegalargument.com — blog: http://www.theoryinpractice.net — google+: http://gplus.to/talios - 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 -
Re: [VOTE] Release Maven 3.1.1
On 12 September 2013 21:52, Baptiste Mathus m...@batmat.net wrote: 2013/9/12 sebb seb...@gmail.com On 12 September 2013 14:52, Arnaud Héritier aherit...@gmail.com wrote: On Thu, Sep 12, 2013 at 3:44 PM, sebb seb...@gmail.com wrote: On 10 September 2013 16:33, Daniel Kulp dk...@apache.org wrote: -1 The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs to be fixed. I don't have time today to look into that, but might tomorrow if someone doesn't beat me to it. The NL files should also be present at the top-level of SCM. That is not a release-blocker per se, however if they had been there they would likely also be in the source archives at the top-level, which is a release blocker IMO. Like we already say I think we aren't convinced about this because it will imply to recopy these files across ~50 projects (plugins, shared libs) and thus update them the day we'll decide/need to do it. That's why we always prefered to bundle them at build time. The point is: the NL files should be at the top-level of SCM. That is because SCM URLs are published, so the readers need to know the what the license conditions are. Wasn't it explained that SCM is actually a convenience, and that only the released source tarballs would actually matter here? It's not the case that SCM is only a convenience; the SCM locations are published to end-users on the web-site and in the POMs. And the SCM is anyway public. In this case, Arnaud's point about only adding them at build time is really valid here. Not sure what you are referring to here, but the build is not relevant to this discussion. The fact that having the NL files there would likely have ensured they were in the source archive is an added bonus; it's not the primary reason for having them at the top-level of SCM. In the source, but possibly different in many places and having to maintain their sameness, that's again Arnaud's point. As an external observer and a developer, not duplicating files in many places as they should really be the same seem quite a sound PMC choice to me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
