Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit : 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... +1 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 that doesn't bomb out if 3.0.3 has pulled snapshot dependencies into the same local repo... is there a Jira issue for this? i may look into that myself... i think it would be fine for it to ignore that extra xml entries in the metadata (least change in behaviour) so only change from 2.2.1 would be the more relaxed metadata parsing... if anyone knows any criticals i would more likely see those in a 2.2.3 or 2.3 ie i wouldn't be release manager for such a release ;-) - 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 14 Jan 2012 15:45, Robert Scholte apa...@sourcegrounds.com wrote: 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 plugins with only reporting-goals the requirement for Maven-2.2.1 seems to be the best solution. -Robert On Sat, 14 Jan 2012 00:10:45 +0100, Dennis Lundberg denn...@apache.org wrote: On 2012-01-13 20:43, Robert Scholte wrote: My guess would be that with relocation it wouldn't matter.[1] I'd like to confirm this with the maven-checkstyle-plugin project, but unfortunately a lot of unit-tests are failing on my machine (win7 + jdk6 + any M2/M3) I can confirm these test errors and failures on Win 7, Java 5 and Maven 2.2.1/3.0.3. On Ubuntu with Java 5 and Maven 2.2.1/3.0.3 it works though. Created an issue in JIRA to track it: http://jira.codehaus.org/**browse/MCHECKSTYLE-170http://jira.codehaus .org/browse/MCHECKSTYLE-170 -Robert [1] http://maven.apache.org/**plugins/maven-shade-plugin/** examples/class-relocation.htmlhttp://maven.apache.org/plugins/maven -shade-plugin/examples/class-relocation.html On Thu, 12 Jan 2012 22:59:36 +0100, Dennis Lundberg denn...@apache.org wrote: Hi Can it work? I haven't had much experience with shading, but I was under the impression that it is a way to hide classes from Maven's class loader. What we really want in this case is a way to *insert* newer versions of classes into Maven's class loader. Don't know if that can be done... On 2012-01-12 00:12, Robert Scholte 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.connolly@gmail.**com stephen.alan.conno...@gmail.com wrote: +1 +1 --**-- ** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apac he.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscribe@maven.apache .org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-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.7
+1 from me On 2012-01-12 23:40, Dennis Lundberg wrote: 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 JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11132status=1 Staging repo: https://repository.apache.org/content/repositories/maven-060/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.7/ 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: [VOTE] Release Maven Eclipse Plugin version 2.9
Hi Barrie, thanks for picking this up. I've fixed some critical issues we faced during development on one of my projects, but lost motivation to continue because of the current structure of the ITs, which take ages to run. Anyhow, here's my +1 -Robert On Fri, 13 Jan 2012 00:22:34 +0100, Barrie Treloar baerr...@gmail.com wrote: Hi, We solved 25 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133version=16240 There are still a large backlog of issues left in JIRA: (extra support would be appreciated) http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MECLIPSE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-061/ Staging site: (not yet synced) http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/ 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
Eclipse plugin ITs was Re: [VOTE] Release Maven Eclipse Plugin version 2.9
Thanks a lot for this hard wok Barrie yes it was my problem too Robert. ITs are now very difficult to use/maintain and sadly are covering only the fact that what we generate is always the same and not that it is working in eclipse. As far as I remember this is the larger plugin we have in lines of codes and also the dirtiest one as it was built from many many contributors (because of the variety of usages and eclipse versions) Since that, I had the chance to switch from eclipse to intellij and it solved all my issues. cheers, Arnaud On Sun, Jan 15, 2012 at 9:35 PM, Robert Scholte apa...@sourcegrounds.comwrote: Hi Barrie, thanks for picking this up. I've fixed some critical issues we faced during development on one of my projects, but lost motivation to continue because of the current structure of the ITs, which take ages to run. Anyhow, here's my +1 -Robert On Fri, 13 Jan 2012 00:22:34 +0100, Barrie Treloar baerr...@gmail.com wrote: Hi, We solved 25 issues: http://jira.codehaus.org/**secure/ReleaseNote.jspa?** projectId=11133version=16240http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133version=16240 There are still a large backlog of issues left in JIRA: (extra support would be appreciated) http://jira.codehaus.org/**secure/IssueNavigator.jspa?** reset=truemode=hidejqlQuery=**project+%3D+MECLIPSE+AND+** resolution+%3D+Unresolved+**ORDER+BY+updated+DESChttp://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MECLIPSE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/**content/repositories/maven-**061/https://repository.apache.org/content/repositories/maven-061/ Staging site: (not yet synced) http://maven.apache.org/**plugins/maven-eclipse-plugin-**2.9/http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/ Guide to testing staged releases: http://maven.apache.org/**guides/development/guide-** testing-releases.htmlhttp://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven EAR Plugin version 2.7
+1 Hervé Le jeudi 12 janvier 2012 23:40:27 Dennis Lundberg a écrit : 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=H tmlversion=17293 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11132sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-060/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.7/ 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: Eclipse plugin ITs was Re: [VOTE] Release Maven Eclipse Plugin version 2.9
2012/1/16 Arnaud Héritier aherit...@gmail.com: Thanks a lot for this hard wok Barrie yes it was my problem too Robert. ITs are now very difficult to use/maintain and sadly are covering only the fact that what we generate is always the same and not that it is working in eclipse. As far as I remember this is the larger plugin we have in lines of codes and also the dirtiest one as it was built from many many contributors (because of the variety of usages and eclipse versions) Since that, I had the chance to switch from eclipse to intellij and it solved all my issues. lol. Well what black magic is intellij doing that makes using maven better? There is the option to switch to m2e. I cant do that for some of my projects because they are Eclipse RCP 3.2 projects that are bodge anyway. m-e-p works well enough. Its worse than you summarize because: * it does its own dependency analysis because there was no standard way of exposing that before (refactoring to use aether is an option) * the ITs were built at the time where there was no IT standard * there is support for eclipse-like environments (RAD, etc) which is even harder to maintain * some OSGi support which is using deprecated feature sets and is impossible to maintain because there are no ITs or use cases for it. This list is probably a part of the reason that Jason suggested retiring plugins. (This one is sporadically maintained but it still works as advertised) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
