Minimize an Uber Jar correctly, Using Shade-Plugin
Dear fellows, I am using the Maven-Shade-Plugin to create a runnable Uber-jar. According to the last frame on maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html, the size of the jar can be minimized by using: configuration minimizeJartrue/minimizeJar /configuration But this feature does not take into consideration the classes that are declared in the log4j.properties file. Hence, e.g. org.apache.log4j.appender.TimeAndSizeRollingAppender is not included in the Uber-jar, even though it's declared in the log4j.properties file. I believe I will face the same problem with Spring. If my code only refers to interface A and my Spring file contains an instantiation of class B that implements A, then B might not be added to the jar, since it's not in the code. How can I solve this problem? You input will be highly appreciated. Thanks in advance, Shmuel Blitz This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com
Re: Minimize an Uber Jar correctly, Using Shade-Plugin
Moving to Users list as this is a question for people developing WITH maven not a question for people developing maven. At present there is no solution, other than having those classes referenced from a referenced class. Shade has no way of knowing that you use properties files to pull in classes via dynamic class loading, as there are sooo sooo many ways you could set that up. While we are on dev@m.a.o A fix would be to allow you to specify classes that should be retained in the minimized jar as a plugin parameter. Would you like to try and write a patch to shade for such a feature? If you are willing to take a shot, please open a JIRA, attach the patch (with tests if you want to stand a chance of getting the patch applied) and give me or the dev@m.a.o list a ping and somebody will apply the patch (assuming you have written tests and used the Maven formatting, but once you have a patch written we can help you get that stuff sorted) It would be relatively easy to do, just not an itch that any of the current committers has needed to scratch. -Stephen On 11 January 2012 09:46, Blitz, Shmuel sbl...@nds.com wrote: Dear fellows, I am using the Maven-Shade-Plugin to create a runnable Uber-jar. According to the last frame on maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html, the size of the jar can be minimized by using: configuration minimizeJartrue/minimizeJar /configuration But this feature does not take into consideration the classes that are declared in the log4j.properties file. Hence, e.g. org.apache.log4j.appender.TimeAndSizeRollingAppender is not included in the Uber-jar, even though it's declared in the log4j.properties file. I believe I will face the same problem with Spring. If my code only refers to interface A and my Spring file contains an instantiation of class B that implements A, then B might not be added to the jar, since it's not in the code. How can I solve this problem? You input will be highly appreciated. Thanks in advance, Shmuel Blitz This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1229755 - /maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/AbstractReleaseMojo.java
Hi Simone,
simple answer: because the original code wasn't using the entryset. I only
added generics, verifying I didn't introduce a potential NPE with new
for-loops.
I haven't checked if the code could be optimized, but this looks like one.
-Robert
On Wed, 11 Jan 2012 08:57:17 +0100, Simone Tripodi
simonetrip...@apache.org wrote:
Hi Robert!
+for ( String providerType :
providerImplementations.keySet() )
{
-String providerType = (String) i.next();
-String providerImplementation = (String)
providerImplementations.get( providerType );
+String providerImplementation =
providerImplementations.get( providerType );
why not just iterating over providerImplementations.entrySet() ?
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.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: [CALL FOR TEST] Apache Maven 3.0.4-RC5 staged
looking good. Tested on a lot of mojo projects. -Robert On Tue, 10 Jan 2012 15:31:12 +0100, Jeff MAURY jeffma...@jeffmaury.com wrote: Works fine with 2 of my Tycho builds, maven-gwt-plugin and hudson-the-definitive-guide Jeff On Tue, Jan 10, 2012 at 2:13 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Works fine here. Regards Mirko On Tue, Jan 10, 2012 at 01:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: None here On 9 January 2012 23:44, Brett Porter br...@apache.org wrote: No issues here. On 06/01/2012, at 7:52 AM, Olivier Lamy wrote: Hello, Apache Maven 3.0.4-RC5 has been staged for testing purpose. This is a preview (and not an official supported version) of the coming 3.0.4 official release. The repository is available here: https://repository.apache.org/content/repositories/maven-017/ For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC5/ Changelog is available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create Since previous RC following changes have been added: * [MNG-5224] - REGRESSION: Injected Settings in a Mojo are missing the profiles from settings.xml * [MNG-5225] - The default version of the maven-site-plugin as defined in the site-lifecycle must be 3.x The review period will end on 16 Jan (see http://s.apache.org/REVIEW-END-MVN-3.0.4-RC5) Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - 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
Need translation help into French for PMD Plugin
Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need translation help into French for PMD Plugin
Hello, I think I can :-) 2012/1/11 Dennis Lundberg denn...@apache.org: Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need translation help into French for PMD Plugin
I'll add a dutch translation for both reports too. By the way, it looks like some cpd-report properties have an incorrect value for report.cpd.cpdlink It refers to PMD instead of CPD, or am I missing something? -Robert On Wed, 11 Jan 2012 22:26:36 +0100, Olivier Lamy ol...@apache.org wrote: Hello, I think I can :-) 2012/1/11 Dennis Lundberg denn...@apache.org: Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- 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: Need translation help into French for PMD Plugin
Okay, I see the reason of the confusion: http://maven.apache.org/plugins/maven-clean-plugin/cpd.html -Robert On Wed, 11 Jan 2012 22:36:37 +0100, Robert Scholte apa...@sourcegrounds.com wrote: I'll add a dutch translation for both reports too. By the way, it looks like some cpd-report properties have an incorrect value for report.cpd.cpdlink It refers to PMD instead of CPD, or am I missing something? -Robert On Wed, 11 Jan 2012 22:26:36 +0100, Olivier Lamy ol...@apache.org wrote: Hello, I think I can :-) 2012/1/11 Dennis Lundberg denn...@apache.org: Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[PROPOSAL] Reporting plugins should require Maven 2.2.1
Hi I've had a look at this issue in the Checkstyle Plugin http://jira.codehaus.org/browse/MCHECKSTYLE-146 The issue is not unique to the Checkstyle Plugin, but rather any plugin that uses Doxia 1.1.x or newer. That means at least all reporting plugins. I've verified it on the PMD Plugin that I am working on. All Maven 2 versions come with a bundled Doxia version. This means that it is locked and cannot use newer versions of Doxia. Most current reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0. Maven version prior to that cannot use Doxia 1.1 features like Doxia Logging. So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x there is a high probability that it will crash, in a way similar to what is described in the above issue. To remedy this I propose that all plugins that use Doxia 1.1+ has its Maven prerequisite set to 2.2.1. Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. Comments? This is something that can be done one plugin at a time, when it's due for release. We should register JIRA issues for each plugin stating the updated Maven prerequisite, to make the change visible to our users. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need translation help into French for PMD Plugin
Thanks to both of you! On 2012-01-11 22:36, Robert Scholte wrote: I'll add a dutch translation for both reports too. By the way, it looks like some cpd-report properties have an incorrect value for report.cpd.cpdlink It refers to PMD instead of CPD, or am I missing something? -Robert On Wed, 11 Jan 2012 22:26:36 +0100, Olivier Lamy ol...@apache.org wrote: Hello, I think I can :-) 2012/1/11 Dennis Lundberg denn...@apache.org: Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- 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 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
Hi Some background on Maven and Doxia versions and compatibility can be found here: http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan On 2012-01-11 23:22, Dennis Lundberg wrote: Hi I've had a look at this issue in the Checkstyle Plugin http://jira.codehaus.org/browse/MCHECKSTYLE-146 The issue is not unique to the Checkstyle Plugin, but rather any plugin that uses Doxia 1.1.x or newer. That means at least all reporting plugins. I've verified it on the PMD Plugin that I am working on. All Maven 2 versions come with a bundled Doxia version. This means that it is locked and cannot use newer versions of Doxia. Most current reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0. Maven version prior to that cannot use Doxia 1.1 features like Doxia Logging. So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x there is a high probability that it will crash, in a way similar to what is described in the above issue. To remedy this I propose that all plugins that use Doxia 1.1+ has its Maven prerequisite set to 2.2.1. Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. Comments? This is something that can be done one plugin at a time, when it's due for release. We should register JIRA issues for each plugin stating the updated Maven prerequisite, to make the change visible to our users. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
+1 - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 11 Jan 2012 22:23, Dennis Lundberg denn...@apache.org wrote: Hi I've had a look at this issue in the Checkstyle Plugin http://jira.codehaus.org/browse/MCHECKSTYLE-146 The issue is not unique to the Checkstyle Plugin, but rather any plugin that uses Doxia 1.1.x or newer. That means at least all reporting plugins. I've verified it on the PMD Plugin that I am working on. All Maven 2 versions come with a bundled Doxia version. This means that it is locked and cannot use newer versions of Doxia. Most current reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0. Maven version prior to that cannot use Doxia 1.1 features like Doxia Logging. So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x there is a high probability that it will crash, in a way similar to what is described in the above issue. To remedy this I propose that all plugins that use Doxia 1.1+ has its Maven prerequisite set to 2.2.1. Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. Comments? This is something that can be done one plugin at a time, when it's due for release. We should register JIRA issues for each plugin stating the updated Maven prerequisite, to make the change visible to our users. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
What about plugins containing both build and report goals? If the suggested shading of Doxia will work, I'd prefer that option. -Robert On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar baerr...@gmail.com wrote: On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 +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: [PROPOSAL] Reporting plugins should require Maven 2.2.1
On Thu, Jan 12, 2012 at 9:42 AM, Robert Scholte apa...@sourcegrounds.com wrote: What about plugins containing both build and report goals? If the suggested shading of Doxia will work, I'd prefer that option. Can you elaborate on the problem? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
I tend to feel that this community is a bit whelmed, and that we'd do better service to the world at large if we drew a line in the sand at 2.2.1. Anyone who really wants new functionality with older core maven can step up and volunteer to maintain branches of plugins. On Wed, Jan 11, 2012 at 6:12 PM, Robert Scholte apa...@sourcegrounds.com wrote: What about plugins containing both build and report goals? If the suggested shading of Doxia will work, I'd prefer that option. -Robert On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar baerr...@gmail.com wrote: On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 +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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
+1 - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 11 Jan 2012 23:22, Benson Margulies bimargul...@gmail.com wrote: I tend to feel that this community is a bit whelmed, and that we'd do better service to the world at large if we drew a line in the sand at 2.2.1. Anyone who really wants new functionality with older core maven can step up and volunteer to maintain branches of plugins. On Wed, Jan 11, 2012 at 6:12 PM, Robert Scholte apa...@sourcegrounds.com wrote: What about plugins containing both build and report goals? If the suggested shading of Doxia will work, I'd prefer that option. -Robert On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar baerr...@gmail.com wrote: On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 +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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
we should maybe roll a 2.3 where the fix is being aware of the new snapshot metadata so that people who have projects not ready for 3.0.4 can have them coexist. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 11 Jan 2012 23:22, Benson Margulies bimargul...@gmail.com wrote: I tend to feel that this community is a bit whelmed, and that we'd do better service to the world at large if we drew a line in the sand at 2.2.1. Anyone who really wants new functionality with older core maven can step up and volunteer to maintain branches of plugins. On Wed, Jan 11, 2012 at 6:12 PM, Robert Scholte apa...@sourcegrounds.com wrote: What about plugins containing both build and report goals? If the suggested shading of Doxia will work, I'd prefer that option. -Robert On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar baerr...@gmail.com wrote: On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 +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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
JDK 5 needed for Performing a Maven Project Release?
http://maven.apache.org/developers/release/maven-project-release-procedure.html says you have JDK 5 installed and on your shell's path. I was about to try out the new laptop, which is a Macbook Air, and the is the first time I've used a Mac. It comes with JDK 6. Are we happy that compiler options will correctly build JDK 5 classes? (Things like http://docs.oracle.com/javase/6/docs/api/java/lang/String.html#isEmpty%28%29 break binary backwards compatibility.) Or do I need to work out how to install JDK 5? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 5 needed for Performing a Maven Project Release?
On 12/01/2012, at 2:08 PM, Barrie Treloar wrote: http://maven.apache.org/developers/release/maven-project-release-procedure.html says you have JDK 5 installed and on your shell's path. it should probably say or above... I was about to try out the new laptop, which is a Macbook Air, and the is the first time I've used a Mac. It comes with JDK 6. Are we happy that compiler options will correctly build JDK 5 classes? Yep, as long as you used the right things, as you note next: (Things like http://docs.oracle.com/javase/6/docs/api/java/lang/String.html#isEmpty%28%29 break binary backwards compatibility.) Or do I need to work out how to install JDK 5? Maven 3 has the animal sniffer plugin set up in its build - maybe that could be pushed up to the parent. I think Jenkins runs all the plugins under JDK 5 so you could check that's building fine first too. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
+1 Den 11. jan. 2012 kl. 23:23 skrev Dennis Lundberg denn...@apache.org: Hi I've had a look at this issue in the Checkstyle Plugin http://jira.codehaus.org/browse/MCHECKSTYLE-146 The issue is not unique to the Checkstyle Plugin, but rather any plugin that uses Doxia 1.1.x or newer. That means at least all reporting plugins. I've verified it on the PMD Plugin that I am working on. All Maven 2 versions come with a bundled Doxia version. This means that it is locked and cannot use newer versions of Doxia. Most current reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0. Maven version prior to that cannot use Doxia 1.1 features like Doxia Logging. So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x there is a high probability that it will crash, in a way similar to what is described in the above issue. To remedy this I propose that all plugins that use Doxia 1.1+ has its Maven prerequisite set to 2.2.1. Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. Comments? This is something that can be done one plugin at a time, when it's due for release. We should register JIRA issues for each plugin stating the updated Maven prerequisite, to make the change visible to our users. -- 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: [PROPOSAL] Reporting plugins should require Maven 2.2.1
+1 -- Olivier Le 11 janv. 2012 23:23, Dennis Lundberg denn...@apache.org a écrit : Hi I've had a look at this issue in the Checkstyle Plugin http://jira.codehaus.org/browse/MCHECKSTYLE-146 The issue is not unique to the Checkstyle Plugin, but rather any plugin that uses Doxia 1.1.x or newer. That means at least all reporting plugins. I've verified it on the PMD Plugin that I am working on. All Maven 2 versions come with a bundled Doxia version. This means that it is locked and cannot use newer versions of Doxia. Most current reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0. Maven version prior to that cannot use Doxia 1.1 features like Doxia Logging. So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x there is a high probability that it will crash, in a way similar to what is described in the above issue. To remedy this I propose that all plugins that use Doxia 1.1+ has its Maven prerequisite set to 2.2.1. Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. Comments? This is something that can be done one plugin at a time, when it's due for release. We should register JIRA issues for each plugin stating the updated Maven prerequisite, to make the change visible to our users. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
