Re: [VOTE] Release Maven install plugin version 2.3.1
On 18 May 2010 06:52, Ludwig Magnusson lud...@itcatapult.com wrote: I don't have an official say in this but I recently submitted a patch for an issue I created that allows for a skip parameter to the install plugin. I assigned it to the 2.4 version (2.3.1 did not exist in jira at the time). Is FYI, If you don't have commit access, you should not be assigning a Fix Version for JIRA issues that you create as you do not have any ability to control when the issue gets fixed (if you had commit access you could controld when the issue gets fixed) it possible to add this patch or is it too much work? Given that Kristian has already staged the release it is unlikely to make it into 2.3.1 Check it out here: http://jira.codehaus.org/browse/MINSTALL-73 The patch is simple enough, but anyone applying the patch would really be looking for a positive negative integration test to ensure that things do not break going forward. At this stage due to the great effort that Benjamin has put in to creating integration tests, the Maven community really wants to ensure that we increase coverage with new features. If you add two integration test cases (+ve and -ve) to your patch I will apply it for you. -Stephen /Ludwig -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: den 17 maj 2010 23:36 To: Maven Developers List Subject: Re: [VOTE] Release Maven install plugin version 2.3.1 +1 On 17 May 2010 23:58, Kristian Rosenvold kristian.rosenv...@gmail.comwrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136version=164 59 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejql Query=project+%3D+MINSTALL+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DEhttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejql%0AQuery=project+%3D+MINSTALL+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DE SC Staging repo: https://repository.apache.org/content/repositories/maven-039/ Staging site: http://maven.apache.org/plugins/maven-install-plugin-2.3.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven install plugin version 2.3.1
I'm doing a whole series of releases at the moment for supporting multithreaded builds (and some bugs related to that), and anything that's not already fixed (with decent test-cases) I'm just ignoring. As I announced a week ago (http://www.mail-archive.com/dev@maven.apache.org/msg84663.html), there are still some more plugins that'll are up for imminent release. And there's going to be another bunch after that too (deploy, release and a few more). Your patch looked good enough. Make tests like Stephen says and I'll review it. But it's too late for 2.3.1. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ear plugin version 2.4.2
+1 S. --- [image: Linkedin] http://www.linkedin.com/in/snicoll[image: Twitter]http://twitter.com/snicoll On Tue, May 18, 2010 at 12:58 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132version=16465 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MEAR+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-042/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.4.2/ 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: [VOTE] Release Maven jar plugin version 2.3.1
Kristian Rosenvold wrote: Staging repo: https://repository.apache.org/content/repositories/maven-041/ Staging site: http://maven.apache.org/plugins/maven-jar-plugin-2.3.1 +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven jar plugin version 2.3.1
+1 Le mardi 18 mai 2010 00:58:15, Kristian Rosenvold a écrit : Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137version=16 491 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejq lQuery=project+%3D+MJAR+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-041/ Staging site: http://maven.apache.org/plugins/maven-jar-plugin-2.3.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ear plugin version 2.4.2
+1 Le mardi 18 mai 2010 00:58:33, Kristian Rosenvold a écrit : Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132version=16 465 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejq lQuery=project+%3D+MEAR+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-042/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.4.2/ 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] Release Maven install plugin version 2.3.1
Kristian Rosenvold wrote: Staging repo: https://repository.apache.org/content/repositories/maven-039/ Staging site: http://maven.apache.org/plugins/maven-install-plugin-2.3.1/ +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Compiler plugin version 2.3.1
Kristian Rosenvold wrote: Staging repo: https://repository.apache.org/content/repositories/maven-038/ Staging site: http://maven.apache.org/plugins/maven-compiler-plugin-2.3.1/ +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resources plugin version 2.4.3
Kristian Rosenvold wrote: Staging repo: https://repository.apache.org/content/repositories/maven-040/ Staging site: http://maven.apache.org/plugins/maven-resources-plugin-2.4.3 +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3 versions of the plugins
Why would Maven allow parallel builds that are not thread-safe? Granted, it's the developer's choice to take the chance, but I just don't see why it's beneficial to allow builds being potentially corrupted unbeknownst to the builder. 2010/5/17 Arnaud Héritier aherit...@gmail.com: In m3 if you activate the // mode and you have a plugin which isn't marked as compatible you'll have a warning like that : [WARNING] * [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains the following plugin(s) that are not marked as * [WARNING] * @threadSafe to support parallel building. * [WARNING] * While this /may/ work fine, please look for plugin updates * [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in * [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Maven Model: [WARNING] org.apache.maven.plugins:maven-resources-plugin:2.4.2 [WARNING] org.apache.maven.plugins:maven-clean-plugin:2.3 [WARNING] org.apache.maven.plugins:maven-compiler-plugin:2.0.2 [WARNING] org.apache.maven.plugins:maven-install-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-surefire-plugin:2.4.3 [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-remote-resources-plugin:1.1 [WARNING] org.codehaus.modello:modello-maven-plugin:1.3 Arnaud On May 17, 2010, at 11:42 PM, Paul Benedict wrote: Lots of plugins are up for vote to be @threadSafe with Maven 3. Does Maven 3 have any mechanism to reject plugins prior to the versions being released? What happens if someone uses a Maven 2 version? Paul - 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: Maven 3 versions of the plugins
The intention of the warning was to make it pretty clear that you're running with some risk. We have already agreed that the entire parallel feature is to be marked as experimental (although with the explicit adding of @threadSafe to the mojos I personally think regular parallel is good for prime time). Fortunately most threading-related failures that happen within plugins are quite clear-cut. When I started out with this stuff I was expecting a lot of subtle memory model violations and stuff like that, but there has been almost none of that. In fact, after we fixed a couple of key problems in plexus most of the failing plugins fail fairly quickly and on a reasonably regular basis. The only *real* nasty I've seen so far is modello-plugin, which in its non-thread-safe form produces errors straight out of h*ll (generated-sources is created under random modules - sometimes switching midway in the source generation process, making it appear to be compiling the wrong module). All the others I've seen as of now are fairly mild stuff that usually fail with (some kind of) error message. Also note that most of the corruption issues being fixed related to http://jira.codehaus.org/browse/MSHARED-148 (which is part of JAR/EAR vote as of yesterday) actually can occur in today's 2.2.1. The fixes related to MSHARED-148 contain only 1 issue that is clearly parallel only. We want users to try this feature. Hopefully also create some pressure in the community to make plugins @threadSafe. By the time 3.0 releases, most of the (non-deprecated) core plugins will be @threadSafe I'm not really heavily invested in the current solution, but if we were to fail the build with non-threadsafe plugins I'd want an option to do it anyway. Isn't the current solution noisy enough ? I'm probably coming through as a bleeding-heart liberal here, I don't like forcing users. I think it's mostly about controlling expectations and directing users to the proper places...? Kristian ti., 18.05.2010 kl. 13.32 -0500, skrev Paul Benedict: Why would Maven allow parallel builds that are not thread-safe? Granted, it's the developer's choice to take the chance, but I just don't see why it's beneficial to allow builds being potentially corrupted unbeknownst to the builder. 2010/5/17 Arnaud Héritier aherit...@gmail.com: In m3 if you activate the // mode and you have a plugin which isn't marked as compatible you'll have a warning like that : [WARNING] * [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains the following plugin(s) that are not marked as * [WARNING] * @threadSafe to support parallel building. * [WARNING] * While this /may/ work fine, please look for plugin updates* [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in* [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Maven Model: [WARNING] org.apache.maven.plugins:maven-resources-plugin:2.4.2 [WARNING] org.apache.maven.plugins:maven-clean-plugin:2.3 [WARNING] org.apache.maven.plugins:maven-compiler-plugin:2.0.2 [WARNING] org.apache.maven.plugins:maven-install-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-surefire-plugin:2.4.3 [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-remote-resources-plugin:1.1 [WARNING] org.codehaus.modello:modello-maven-plugin:1.3 Arnaud On May 17, 2010, at 11:42 PM, Paul Benedict wrote: Lots of plugins are up for vote to be @threadSafe with Maven 3. Does Maven 3 have any mechanism to reject plugins prior to the versions being released? What happens if someone uses a Maven 2 version? Paul - 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
AntRun plugin 1.3.1 or 1.4 ?
Hi, I was reviewing the antrun plugin and I saw we have in jira fixed issues in 1.3.1 (threadsafe) and 1.4 (several issues): http://jira.codehaus.org/browse/MANTRUN#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel Everything was applied in trunk with version 1.3.1-SNAPSHOT This plugin wasn't released since oct 2008. I propose to directly release version 1.4. Paul I think you were the last one to work on it. What do you think about non-fixed issues scheduled to 1.4 ? I wanted to fix this 2 issues : http://jira.codehaus.org/browse/MANTRUN-136 http://jira.codehaus.org/browse/MANTRUN-137 I tested locally and it works. Could we apply them ? WDYT ? Arnaud
Re: AntRun plugin 1.3.1 or 1.4 ?
I set the version to 1.3.1, but it seems like it should be 1.4. Kristian ti., 18.05.2010 kl. 23.07 +0200, skrev Arnaud Héritier: Hi, I was reviewing the antrun plugin and I saw we have in jira fixed issues in 1.3.1 (threadsafe) and 1.4 (several issues): http://jira.codehaus.org/browse/MANTRUN#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel Everything was applied in trunk with version 1.3.1-SNAPSHOT This plugin wasn't released since oct 2008. I propose to directly release version 1.4. Paul I think you were the last one to work on it. What do you think about non-fixed issues scheduled to 1.4 ? I wanted to fix this 2 issues : http://jira.codehaus.org/browse/MANTRUN-136 http://jira.codehaus.org/browse/MANTRUN-137 I tested locally and it works. Could we apply them ? WDYT ? Arnaud - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3 versions of the plugins
Kristian Rosenvold wrote: Isn't the current solution noisy enough ? +1, looks fine to me. ti., 18.05.2010 kl. 13.32 -0500, skrev Paul Benedict: Why would Maven allow parallel builds that are not thread-safe? Simply because the absence of the @threadSafe annotation does not imply that the build is actually not thread-safe. And if the dumb machine doesn't know for sure, it's usually best to leave the decision up to the thinking human. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: AntRun plugin 1.3.1 or 1.4 ?
yes and we should update the pom. I'll wait paul's feedback about it to know what to do On May 18, 2010, at 11:22 PM, Kristian Rosenvold wrote: I set the version to 1.3.1, but it seems like it should be 1.4. Kristian ti., 18.05.2010 kl. 23.07 +0200, skrev Arnaud Héritier: Hi, I was reviewing the antrun plugin and I saw we have in jira fixed issues in 1.3.1 (threadsafe) and 1.4 (several issues): http://jira.codehaus.org/browse/MANTRUN#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel Everything was applied in trunk with version 1.3.1-SNAPSHOT This plugin wasn't released since oct 2008. I propose to directly release version 1.4. Paul I think you were the last one to work on it. What do you think about non-fixed issues scheduled to 1.4 ? I wanted to fix this 2 issues : http://jira.codehaus.org/browse/MANTRUN-136 http://jira.codehaus.org/browse/MANTRUN-137 I tested locally and it works. Could we apply them ? WDYT ? Arnaud - 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 Source Plugin 2.1.2
+1 Arnaud On May 17, 2010, at 11:27 PM, Benjamin Bentmann wrote: Hi, We solved 1 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147version=16467 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11147status=1 Staging repo: https://repository.apache.org/content/repositories/maven-043/ Staging site (sync pending): http://maven.apache.org/plugins/maven-source-plugin-2.1.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me 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: [VOTE] Release Maven jar plugin version 2.3.1
+1 Arnaud On May 18, 2010, at 12:58 AM, Kristian Rosenvold wrote: Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137version=16491 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MJAR+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-041/ Staging site: http://maven.apache.org/plugins/maven-jar-plugin-2.3.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ear plugin version 2.4.2
+1 Arnaud On May 18, 2010, at 12:58 AM, Kristian Rosenvold wrote: Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132version=16465 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MEAR+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-042/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.4.2/ 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] Release Maven install plugin version 2.3.1
+1 Arnaud On May 18, 2010, at 12:58 AM, Kristian Rosenvold wrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136version=16459 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MINSTALL+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-039/ Staging site: http://maven.apache.org/plugins/maven-install-plugin-2.3.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Compiler plugin version 2.3.1
+1 Arnaud On May 18, 2010, at 12:59 AM, Kristian Rosenvold wrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130version=16462 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MCOMPILER+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-038/ Staging site: http://maven.apache.org/plugins/maven-compiler-plugin-2.3.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resources plugin version 2.4.3
+1 Arnaud On May 18, 2010, at 12:58 AM, Kristian Rosenvold wrote: Hi, We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145version=16471 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MRESOURCES+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-040/ Staging site: http://maven.apache.org/plugins/maven-resources-plugin-2.4.3 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] Release Maven Project Info Reports Plugin version 2.2
+1 Arnaud On May 15, 2010, at 11:41 PM, Olivier Lamy wrote: Hi, In the process of releasing all stuff for site plugin for maven 3, I'd like to release Maven Project Info Reports Plugin version 2.2. We solved 11 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142version=15042 Staging repo: https://repository.apache.org/content/repositories/maven-034/ Staging site: http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.2 (wait sync) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here is my +1 Thanks, -- Olivier - 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 3 versions of the plugins
+1 It's clear, it allows me to continue if I want to try it anyway, and I think there was plenty of prior discussion of it on the list. -Original Message- From: Kristian Rosenvold [mailto:kristian.rosenv...@gmail.com] Sent: Tuesday, May 18, 2010 2:57 PM To: Maven Developers List Subject: Re: Maven 3 versions of the plugins The intention of the warning was to make it pretty clear that you're running with some risk. We have already agreed that the entire parallel feature is to be marked as experimental (although with the explicit adding of @threadSafe to the mojos I personally think regular parallel is good for prime time). Fortunately most threading-related failures that happen within plugins are quite clear-cut. When I started out with this stuff I was expecting a lot of subtle memory model violations and stuff like that, but there has been almost none of that. In fact, after we fixed a couple of key problems in plexus most of the failing plugins fail fairly quickly and on a reasonably regular basis. The only *real* nasty I've seen so far is modello-plugin, which in its non-thread-safe form produces errors straight out of h*ll (generated-sources is created under random modules - sometimes switching midway in the source generation process, making it appear to be compiling the wrong module). All the others I've seen as of now are fairly mild stuff that usually fail with (some kind of) error message. Also note that most of the corruption issues being fixed related to http://jira.codehaus.org/browse/MSHARED-148 (which is part of JAR/EAR vote as of yesterday) actually can occur in today's 2.2.1. The fixes related to MSHARED-148 contain only 1 issue that is clearly parallel only. We want users to try this feature. Hopefully also create some pressure in the community to make plugins @threadSafe. By the time 3.0 releases, most of the (non-deprecated) core plugins will be @threadSafe I'm not really heavily invested in the current solution, but if we were to fail the build with non-threadsafe plugins I'd want an option to do it anyway. Isn't the current solution noisy enough ? I'm probably coming through as a bleeding-heart liberal here, I don't like forcing users. I think it's mostly about controlling expectations and directing users to the proper places...? Kristian ti., 18.05.2010 kl. 13.32 -0500, skrev Paul Benedict: Why would Maven allow parallel builds that are not thread-safe? Granted, it's the developer's choice to take the chance, but I just don't see why it's beneficial to allow builds being potentially corrupted unbeknownst to the builder. 2010/5/17 Arnaud Héritier aherit...@gmail.com: In m3 if you activate the // mode and you have a plugin which isn't marked as compatible you'll have a warning like that : [WARNING] * [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains the following plugin(s) that are not marked as * [WARNING] * @threadSafe to support parallel building. * [WARNING] * While this /may/ work fine, please look for plugin updates* [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in* [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Maven Model: [WARNING] org.apache.maven.plugins:maven-resources-plugin:2.4.2 [WARNING] org.apache.maven.plugins:maven-clean-plugin:2.3 [WARNING] org.apache.maven.plugins:maven-compiler-plugin:2.0.2 [WARNING] org.apache.maven.plugins:maven-install-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-surefire-plugin:2.4.3 [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2 [WARNING] org.apache.maven.plugins:maven-remote-resources-plugin:1.1 [WARNING] org.codehaus.modello:modello-maven-plugin:1.3 Arnaud On May 17, 2010, at 11:42 PM, Paul Benedict wrote: Lots of plugins are up for vote to be @threadSafe with Maven 3. Does Maven 3 have any mechanism to reject plugins prior to the versions being released? What happens if someone uses a Maven 2 version? Paul - 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
