Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1

2012-01-14 Thread Mirko Friedenhagen
+1 Now that Java 1.5 has already seen EOL for some years it is funny that most plugins even are still working with 1.4. Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Jan 12, 2012 12:22 AM,

Re: [VOTE] Release Maven EAR Plugin version 2.7

2012-01-14 Thread Olivier Lamy
+1 2012/1/12 Dennis Lundberg denn...@apache.org: Hi, We solved 4 issues, including [MEAR-60] Improve support for skinny war files which has 50 votes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132styleName=Htmlversion=17293 There are still a couple of issues left in

Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1

2012-01-14 Thread Robert Scholte
I've fixed MCHECKSTYLE-170 and tried to apply some shading. The separation of api/interfaces versus implementation is not done well in Doxia. This would mean, that the shade-plugin will need a lot of configuration, which also needs to be maintained if there are new Doxia-classes. So for

Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1

2012-01-14 Thread Stephen Connolly
personally i think we need to draw a line in the sand for all plugins... 2.2.1 is the best line at the moment imho... 2.1.0 and 2.2.0 are not recommended versions, and drawing a line above them makes our message to users that much cleaner. the only other thing we maybe should do is roll a 2.2.2