Re: Java version usage survey
On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.comwrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris
Re: Java version usage survey
+1 to ensure that we have a good solution (toolchains) to continue to keep a compatibility with old Java builds. Like always, upgrading the prerequisite of the core is less annoying than the one in plugins. Users can always keep an old core (and many of them will do it as far as new core versions aren't bringing new useful features and plugins are compatible with old versions). Nothing more to ask in the survey or to change in questions/choices ? I let running the thread for few days and we'll launch the survey at the end of the week if you want. We can keep it open for July/August to have a maximum number of responses during holidays. Cheers, On Tue, Jul 16, 2013 at 7:35 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Given that Oracle have stated they will be more aggressive in forcing people to upgrade, eg -target (and I think -source too) will not got all the way down to 1.2 any more from JDK8 IIRC, we will need to sort out a few things: - is toolchains the way to go? - have we good test coverage with toolchains? Specifically building a JavaEE .ear for a JavaEE 5 container (ie using all/most of our plugins)? Better yet would be building a J2EE 1.4 .ear but I suspect we'd be fine with the JDK 5.0 rather than strict spec conformance. (A lot of big business use old containers and have Sarbains-Oxley heavyweight change control, so changing app server is a very big thing) - have we a good store for toolchains and integration tests? (Invoker skipping tests if certain toolchains are missing, reporting what toolchains are required, merging in toolchains, providing mock toolchains... And have we any other users than the JDK?) - what is the experience of Surefire so far (being the first to completely ditch JRE 1.5) On Tuesday, 16 July 2013, Mirko Friedenhagen wrote: On Jul 16, 2013 2:08 AM, Arnaud Héritier aherit...@gmail.com javascript:; wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible with Java 5 (And probably various plugins with Java 4). Couldn't it be interesting to see which JDKs our users are using to see how we can schedule the end of support of Java 5 (and more). Perhaps a removal of Java 5 support in 3.2 or 3.5 ... Perhaps with a survey like this : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform What do you think ? Useful ? Useless Very, very useful. Regards Mirko -- Sent from my phone -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: tags maven-3.1 vs maven-3.1.0
Michael's point about omiting the trailing .0 is valid, and introducing it now does not follow the established convention. Is it going to be cleaned up? -Chris On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.comwrote: lol On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, another bot? Le lundi 15 juillet 2013 22:28:26 Fred Cooke a écrit : What was the hash for future reference? This is why sebb is sooo right. If you have a unique coordinate, you're good for life, no matter what gets done to the SCM. (more or less) On Mon, Jul 15, 2013 at 9:53 PM, Arnaud Héritier aherit...@gmail.com wrote: done On Mon, Jul 15, 2013 at 9:36 PM, Jason van Zyl ja...@tesla.io wrote: Sure, drop the older one. On Jul 15, 2013, at 2:57 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi Jason, It seems we have 2 tags in Git for maven 3.1 : maven-3.1 and maven-3.1.0 I think that the the right one to keep is the second one (893ca28 - 28th June) ? I suppose we need to drop the old maven-3.1 tag ? Cheers, - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
As long as surefire can fork down to 1.5 and as long as tool chains can compile with 1.5, the only issue I can see is if the development environments where these older JVMs are running do not have newer JDKs available also. This is the same issue we face in the Jenkins project, were we are (considering/are - I would need to check the most recent decision) dropping JDK 5.0. But you do raise a valid point about other Java vendors than Oracle On Tuesday, 16 July 2013, Chris Graham wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.comjavascript:; wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- Sent from my phone
Re: Java version usage survey
Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: tags maven-3.1 vs maven-3.1.0
I'm not in favor to recreate a maven-3.1 tag to avoid confusions and we need to keep the maven-3.1.0 which was used in the release But I agree to improve our release/RCs/Staging process as far as it remains as automated as possible. It is already complexe to release stuffs on Apache side and I don't want to add more complexity without a good added-value in return On Tue, Jul 16, 2013 at 8:14 AM, Chris Graham chrisgw...@gmail.com wrote: Michael's point about omiting the trailing .0 is valid, and introducing it now does not follow the established convention. Is it going to be cleaned up? -Chris On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.com wrote: lol On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, another bot? Le lundi 15 juillet 2013 22:28:26 Fred Cooke a écrit : What was the hash for future reference? This is why sebb is sooo right. If you have a unique coordinate, you're good for life, no matter what gets done to the SCM. (more or less) On Mon, Jul 15, 2013 at 9:53 PM, Arnaud Héritier aherit...@gmail.com wrote: done On Mon, Jul 15, 2013 at 9:36 PM, Jason van Zyl ja...@tesla.io wrote: Sure, drop the older one. On Jul 15, 2013, at 2:57 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi Jason, It seems we have 2 tags in Git for maven 3.1 : maven-3.1 and maven-3.1.0 I think that the the right one to keep is the second one (893ca28 - 28th June) ? I suppose we need to drop the old maven-3.1 tag ? Cheers, - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
For all of those who asked to access to replies (I didn't see they were protected) I'll find a solution to share these results when the survey will be really started/published. On Tue, Jul 16, 2013 at 8:19 AM, Arnaud Héritier aherit...@gmail.comwrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.comwrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.comwrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Log4j2/Logback integration updates
This is not (or should not be) an entirely technical question - support for various versions of JDK may be the simpler criterion to discuss, but I feel the more relevant question is Do we first and foremost see small-scale projects [small organisations] or enterprise-scale projects [enterprise-scale organisations] as the recipients of what we build? In the former case, we are at liberty to cut support for older JDK versions and trust in the more modern toolchain and vice versa. While some long-standing problems with newer JDKs (like retina support for JDK 7 on Macs, proper font support for JDK on Linux, or sluggishness of JEE container upgrades for example) can certainly hinder or prevent upgrading the toolchain, to what extent do you believe these problems to be relevant for small-scale projects and enterprise-scale projects respectively? In my experience, the upgrade speed of ASF / Codehaus / Eclipse (which manufacture the toolchains that pretty much everyone uses) is one of the major factors in determining the upgrade speed of most projects out there. Quite few players are willing to pay the cost to sculpt their development process and toolchain entirely from their own needs. IMHO it would be good to upgrade to a JDK 7 based chain, for reasons of both technology, customer affinity and open source society progress - but there are certainly valid opinions for other choices as well. 2013/7/16 Mirko Friedenhagen mfriedenha...@gmail.com I would prefer going from JDK5 to 7 immediately as well, old JDK means usage of old tools. Regards Mirko -- Sent from my mobile On Jul 16, 2013 7:07 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: So what I am hearing is that until we bump core to require JDK6 (or 7) then logback is the only runner from a technical point of view (never mind that log4j2 is still not GA) OTOH I would be interested in bumping JDK all the way to 7 if we were happy that toolchains is good enough and we had tests in play that use toolchains On Tuesday, 16 July 2013, Arnaud Héritier wrote: Hi FYI I rebased both branches on current master : * https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/slf4j-log4j2 * https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/slf4j-logback With all work done by Herve both branches have only one interesting commit to update few deps. If you want to test them I shared some archives : * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-log4j2-bin.tar.gz * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-log4j2-bin.zip * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-logback-bin.tar.gz * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-logback-bin.zip (You just have to replace the non-color config file in conf/logging by the -color one) LOG4J2 has 2 issues : ** It requires Java 6 (while our core is always requiring Java 5 for now) ** beta 7 and beta 8 aren't supporting some methods we used in our integration : [WARNING] setRootLoggerLevel: operation not supported [WARNING] reset(): operation not supported Cheers - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- Sent from my phone -- -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid | EAI Architect Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype):jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==+
Re: tags maven-3.1 vs maven-3.1.0
On Tue, Jul 16, 2013 at 8:14 AM, Chris Graham chrisgw...@gmail.com wrote: Michael's point about omiting the trailing .0 is valid, and introducing it now does not follow the established convention. Is it going to be cleaned up? I sincerely hope not! That would involve potential for confusion should anyone have fetched the old and now deleted (only in the apache copy!) tag. Let the sleeping dog lie and improve the process to avoid it in future. -Chris On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.com wrote: lol On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, another bot? Le lundi 15 juillet 2013 22:28:26 Fred Cooke a écrit : What was the hash for future reference? This is why sebb is sooo right. If you have a unique coordinate, you're good for life, no matter what gets done to the SCM. (more or less) On Mon, Jul 15, 2013 at 9:53 PM, Arnaud Héritier aherit...@gmail.com wrote: done On Mon, Jul 15, 2013 at 9:36 PM, Jason van Zyl ja...@tesla.io wrote: Sure, drop the older one. On Jul 15, 2013, at 2:57 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi Jason, It seems we have 2 tags in Git for maven 3.1 : maven-3.1 and maven-3.1.0 I think that the the right one to keep is the second one (893ca28 - 28th June) ? I suppose we need to drop the old maven-3.1 tag ? Cheers, - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: tags maven-3.1 vs maven-3.1.0
On 16 July 2013 09:44, Fred Cooke fred.co...@gmail.com wrote: On Tue, Jul 16, 2013 at 8:14 AM, Chris Graham chrisgw...@gmail.com wrote: Michael's point about omiting the trailing .0 is valid, and introducing it now does not follow the established convention. Is it going to be cleaned up? I sincerely hope not! That would involve potential for confusion should anyone have fetched the old and now deleted (only in the apache copy!) tag. Let the sleeping dog lie and improve the process to avoid it in future. +1 Now that it is published, you have to live with it. Is the versioning convention documented anywhere? -Chris On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.com wrote: lol On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, another bot? Le lundi 15 juillet 2013 22:28:26 Fred Cooke a écrit : What was the hash for future reference? This is why sebb is sooo right. If you have a unique coordinate, you're good for life, no matter what gets done to the SCM. (more or less) On Mon, Jul 15, 2013 at 9:53 PM, Arnaud Héritier aherit...@gmail.com wrote: done On Mon, Jul 15, 2013 at 9:36 PM, Jason van Zyl ja...@tesla.io wrote: Sure, drop the older one. On Jul 15, 2013, at 2:57 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi Jason, It seems we have 2 tags in Git for maven 3.1 : maven-3.1 and maven-3.1.0 I think that the the right one to keep is the second one (893ca28 - 28th June) ? I suppose we need to drop the old maven-3.1 tag ? Cheers, - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Java version usage survey
Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even *extended* 1.5's life for a year. Sept this year, I think. -Chris -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Log4j2/Logback integration updates
On Tue, Jul 16, 2013 at 6:26 PM, Lennart Jörelid lennart.jore...@gmail.comwrote: This is not (or should not be) an entirely technical question - support for various versions of JDK may be the simpler criterion to discuss, but I feel the more relevant question is Do we first and foremost see small-scale projects [small organisations] or enterprise-scale projects [enterprise-scale organisations] as the recipients of what we build? I think that the premise of the question is utterly wrong! It is not an OR question. The fact is that we do, and need too, cater for both! It's an AND. In the former case, we are at liberty to cut support for older JDK versions and trust in the more modern toolchain and vice versa. While some long-standing problems with newer JDKs (like retina support for JDK 7 on Macs, proper font support for JDK on Linux, or sluggishness of JEE container upgrades for example) can certainly hinder or prevent upgrading the toolchain, to what extent do you believe these problems to be relevant for small-scale projects and enterprise-scale projects respectively? In my experience, the upgrade speed of ASF / Codehaus / Eclipse (which manufacture the toolchains that pretty much everyone uses) is one of the major factors in determining the upgrade speed of most projects out there. Quite few players are willing to pay the cost to sculpt their development process and toolchain entirely from their own needs. In the enterprise space, from what I've seen, it's comes down to one thing: COST. If the existing solution works, then it tends to stay put. As upgrading costs, hugely! The best example that I can think of is that the latest (or later?) of one of the Tivoli products (TIM or TAM) still sits on top of WAS 6.1 (which is EOL) but, as it's embedded into TIM/TAM it is a restricted use, sort of, so it is still supported. My point here is that it is not the specifics of the technology involved (how new or old it is) rather it is the function performed. That is what the enterprise space looks at, they generally do not care how it's done, they just want the job done. I will also be the first to admit, that as things get leaner, and/or start to move to the cloud, that the technology used is getting a better look in. However, with embedded produts, I can not see that changing too much at all. In the open source space, sure, feel free to let the OS stuff lead, as it does eventually find it's way into the corporate space. IMHO it would be good to upgrade to a JDK 7 based chain, for reasons of both technology, customer affinity and open source society progress - but there are certainly valid opinions for other choices as well. 2013/7/16 Mirko Friedenhagen mfriedenha...@gmail.com I would prefer going from JDK5 to 7 immediately as well, old JDK means usage of old tools. Regards Mirko -- Sent from my mobile On Jul 16, 2013 7:07 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: So what I am hearing is that until we bump core to require JDK6 (or 7) then logback is the only runner from a technical point of view (never mind that log4j2 is still not GA) OTOH I would be interested in bumping JDK all the way to 7 if we were happy that toolchains is good enough and we had tests in play that use toolchains On Tuesday, 16 July 2013, Arnaud Héritier wrote: Hi FYI I rebased both branches on current master : * https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/slf4j-log4j2 * https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/slf4j-logback With all work done by Herve both branches have only one interesting commit to update few deps. If you want to test them I shared some archives : * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-log4j2-bin.tar.gz * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-log4j2-bin.zip * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-logback-bin.tar.gz * https://dl.dropboxusercontent.com/u/501043/apache-maven-3.2-SNAPSHOT-logback-bin.zip (You just have to replace the non-color config file in conf/logging by the -color one) LOG4J2 has 2 issues : ** It requires Java 6 (while our core is always requiring Java 5 for now) ** beta 7 and beta 8 aren't supporting some methods we used in our integration : [WARNING] setRootLoggerLevel: operation not supported [WARNING] reset(): operation not supported Cheers - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- Sent from my phone -- -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid | EAI
Re: Java version usage survey
Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible Oracle Java 6 was EOL'd. IBM Java 6 was, and is not due to be for a few more years. They even
Re: Java version usage survey
Recent MacOS also thus only Java 1.6 and 1.7. Maybe I could setup a VM with a Java 1.5 but to be honest I already have not enough time to contribute thus working on Maven inside a VM will never occur. On Tue, Jul 16, 2013 at 1:35 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewanalytics
Re: Java version usage survey
perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible
Re: Java version usage survey
I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewform Replies : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu gPmGW4/viewanalytics On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com wrote: On Tue, Jul 16, 2013 at 10:07 AM, Arnaud
Re: Java version usage survey
Me: Linux, Windows, AIX (and if I have too, OS/2!) 1.4, 5, 6 and if I need it, I can get 7. On Tue, Jul 16, 2013 at 10:13 PM, Lennart Jörelid lennart.jore...@gmail.com wrote: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com wrote: Good point. I updated the survey to tell it is the Oracle JDK EOL Survey :
RE: Java version usage survey
Folks In the states..government sector (specifically State Agencies) lag at least 5 years behind available current releases the specific example I provide is the app I was working on was based on JVM 1.5 the Portal was based on JVM 1.4 the end result was: Annotations: NOPE Generics: NOPE EfficientGC: NOPE The agency managers are listening to the hogwash from offshore consultants who say : too expensive to upgrade to 1.7 this type of thinking is costing every taxpayer beaucoups bucks as each and every single tweak to the 1.4 JVM (patches already rolled into 1.6 and improved for 1.7 and tested) take a week or so (to test) on 1.4 Login to ANY State agency website ..attempt to upgrade your Browser's JVM plugin to 1.6 or 1.7 and watch the fireworks! In other words: SNAFU Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 16 Jul 2013 12:35:06 +0100 Subject: Re: Java version usage survey From: stephen.alan.conno...@gmail.com To: dev@maven.apache.org Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM
Release enforcer plugin?
Hi. Would anybody care to release the enforcer 1.3.1 plugin so we can go around http://jira.codehaus.org/browse/MENFORCER-156? All issues for 1.3.1 are fixed: http://jira.codehaus.org/browse/MENFORCER/fixforversion/19426#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
RE: Java version usage survey
Nice idea to have this survey to have some feedback from users. Do you think it may be possible to make this kind of survey to get feedback for maven web site (not plugin) or other area of maven ? Eric Joke: perso win user so using jdk8 or jdk7 according to the os version Real: jdk 7 on server and on win box. -Message d'origine- De : Lennart Jörelid [mailto:lennart.jore...@gmail.com] Envoyé : mardi 16 juillet 2013 14:14 À : Maven Developers List Objet : Re: Java version usage survey I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-li fe-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well.
Re: Release enforcer plugin?
Hi, The release vote is already in progress. Cheers, On Tue, Jul 16, 2013 at 10:17 AM, David Karlsen davidkarl...@gmail.comwrote: Hi. Would anybody care to release the enforcer 1.3.1 plugin so we can go around http://jira.codehaus.org/browse/MENFORCER-156? All issues for 1.3.1 are fixed: http://jira.codehaus.org/browse/MENFORCER/fixforversion/19426#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Java version usage survey
*BUT* such agencies also find it too expensive to upgrade Maven to 3.2 so we don't actually have to worry about them ;-) If you are a refusenick on JVM you are likely also a refusenik on Maven ;-) On 16 July 2013 13:45, Martin Gainty mgai...@hotmail.com wrote: Folks In the states..government sector (specifically State Agencies) lag at least 5 years behind available current releases the specific example I provide is the app I was working on was based on JVM 1.5 the Portal was based on JVM 1.4 the end result was: Annotations: NOPE Generics: NOPE EfficientGC: NOPE The agency managers are listening to the hogwash from offshore consultants who say : too expensive to upgrade to 1.7 this type of thinking is costing every taxpayer beaucoups bucks as each and every single tweak to the 1.4 JVM (patches already rolled into 1.6 and improved for 1.7 and tested) take a week or so (to test) on 1.4 Login to ANY State agency website ..attempt to upgrade your Browser's JVM plugin to 1.6 or 1.7 and watch the fireworks! In other words: SNAFU Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 16 Jul 2013 12:35:06 +0100 Subject: Re: Java version usage survey From: stephen.alan.conno...@gmail.com To: dev@maven.apache.org Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450
Re: Java version usage survey
The last project I was on was migrating WAS/WPS/Portal V6 (JDK 1.4) - WAS/BPM/Portal V8 (JDK 1.6). Why? Because the support costs for EOL software finally made it cost effective to upgrade! :-) And even then, it was meant to be a lift and shift as in just keep the functionality the same as much as possible. Exploitation of new features/bugs would come at a later stage. :-) -Chris On Tue, Jul 16, 2013 at 10:58 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: *BUT* such agencies also find it too expensive to upgrade Maven to 3.2 so we don't actually have to worry about them ;-) If you are a refusenick on JVM you are likely also a refusenik on Maven ;-) On 16 July 2013 13:45, Martin Gainty mgai...@hotmail.com wrote: Folks In the states..government sector (specifically State Agencies) lag at least 5 years behind available current releases the specific example I provide is the app I was working on was based on JVM 1.5 the Portal was based on JVM 1.4 the end result was: Annotations: NOPE Generics: NOPE EfficientGC: NOPE The agency managers are listening to the hogwash from offshore consultants who say : too expensive to upgrade to 1.7 this type of thinking is costing every taxpayer beaucoups bucks as each and every single tweak to the 1.4 JVM (patches already rolled into 1.6 and improved for 1.7 and tested) take a week or so (to test) on 1.4 Login to ANY State agency website ..attempt to upgrade your Browser's JVM plugin to 1.6 or 1.7 and watch the fireworks! In other words: SNAFU Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 16 Jul 2013 12:35:06 +0100 Subject: Re: Java version usage survey From: stephen.alan.conno...@gmail.com To: dev@maven.apache.org Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support
Re: Java version usage survey
I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com wrote: Hi Arnaud. You need to at least add an OTHER (ie non oracle) entry as well. You you can track Oracle java 6 and Non-Oracle java 6. -Chris On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.com
Re: Log4j2/Logback integration updates
FYI, in the next version of logback, i.e. 2.0, we will be using JDK 1.6. However, the logback 1.1.x series will continue to be based on JDK 1.5. On 16.07.2013 07:06, Stephen Connolly wrote: So what I am hearing is that until we bump core to require JDK6 (or 7) then logback is the only runner from a technical point of view (never mind that log4j2 is still not GA) OTOH I would be interested in bumping JDK all the way to 7 if we were happy that toolchains is good enough and we had tests in play that use toolchains - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish
Re: Java version usage survey
Yep. Sent from my iPhone On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote: Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, July 16, 2013 3:47 AM To: Maven Developers List Subject: Re: Java version usage survey I've put a question on Stack Overflow: http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto see if we can get something that is a bit more focus on facts. e.g. we are all OSS developers: thus premium/extended/sustaining support contracts are outside our budget. If we cannot test it for free, we cannot support it. On 16 July 2013 09:01, Fred Cooke fred.co...@gmail.com wrote: My 2c: - J7 on Mac is unstable (trust me...) and non-performant, and thus I require my users to use Apple's J6 on the Mac. - On Linux there are lots of Swing bugs in all versions, but a lot less in J7 than J6, so I recommend J7 for Linux guys. - I don't use J5 for anything at all and none of my code can run on it due to basics that are missing there. I didn't distinguish vendors because the comments apply across all of them anyway. Fred. On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham
Re: Java version usage survey
Just to clarify my comments: I can't and won't build anything with anything higher than J6 for the foreseeable future, maybe upto 2 years or so, who knows. J7 is purely a runtime option for users for me, same for J8. J5 is dead for both builds and runtime in my eyes. I'd prefer to maximise my choice by keeping M3 and plugins on J6, however I wouldn't cry if M3 itself went J7, but I would cry if the plugins went J7 without first releasing Git-functional versions of m-release-p and m-site-p. Even then, while wiping the tears away, I could hard code some fixes and release my own fork for my own use, no biggy. Preference: Don't exceed J6 as a requirement for Maven or plugins. Bottom line: I'll survive anything you do. 3 open sauce. Especially ketchup. Another 2c, there is some signature difference which can result in J6-clean source building to a J7-only binary using J7 javac. I forget the details, but IIRC it was on the MOJO list that I learned this. Unsure if it was added to the sniffer or not. Fred. On Tue, Jul 16, 2013 at 8:38 PM, Stéphane Nicoll stephane.nic...@gmail.comwrote: Yep. Sent from my iPhone On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote: Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using commercial products that require them that themselves are not EOLed. Given that current versions of Maven support Java 5 and 6, the real question is how important is it for older applications that cannot support Java 7 to be able to use future versions of Maven? As far as I know, there is nothing from preventing Maven developers from using the existing versions of JDK 5/6 to build and test Maven. -- Robert Patrick robert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle Corporation Office: +1.940.725.0011 1148 Triple Crown Court Fax: +1.940.725.0012 Bartonville, TX 76226, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page:
Re: tags maven-3.1 vs maven-3.1.0
Isn't the convention way to omit the last zero? This has been done for Maven and all plugins/components before. No, we have 2.1.0 and 2.2.0 for the Maven core distro. Plugins would/could be a different story though. /Anders Mike --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
For now what is resulting from this thread is : * We do a survey to better know where our user are and were they are going * We check what is the status of our tools (toolchains co) to be sure how we can easily use versions of java older than the one required by maven * We discuss on the ML to clearly cover all aspects of such upgrades (core vs plugins ...) And from all of this we should be able to schedule and announce how we will update our prerequisites. WDYT ? From my point of view there is now urgency. It is just to advance on some subject as I know they aren't easy to solve (and dev products like jenkins are analyzing such changes too). Arnaud On Tue, Jul 16, 2013 at 8:54 PM, Fred Cooke fred.co...@gmail.com wrote: Just to clarify my comments: I can't and won't build anything with anything higher than J6 for the foreseeable future, maybe upto 2 years or so, who knows. J7 is purely a runtime option for users for me, same for J8. J5 is dead for both builds and runtime in my eyes. I'd prefer to maximise my choice by keeping M3 and plugins on J6, however I wouldn't cry if M3 itself went J7, but I would cry if the plugins went J7 without first releasing Git-functional versions of m-release-p and m-site-p. Even then, while wiping the tears away, I could hard code some fixes and release my own fork for my own use, no biggy. Preference: Don't exceed J6 as a requirement for Maven or plugins. Bottom line: I'll survive anything you do. 3 open sauce. Especially ketchup. Another 2c, there is some signature difference which can result in J6-clean source building to a J7-only binary using J7 javac. I forget the details, but IIRC it was on the MOJO list that I learned this. Unsure if it was added to the sniffer or not. Fred. On Tue, Jul 16, 2013 at 8:38 PM, Stéphane Nicoll stephane.nic...@gmail.comwrote: Yep. Sent from my iPhone On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote: Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a release that claims to work on Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea. Tools like animal-sniffer are great to help developers who cannot set up the older JVMs on their development environment... but in my experience they are no substitute for running on the older JVM. If our test capability is basically the Windows/Java 1.5 slave and the *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep that integration test suite passing *then* Java 1.5 is dead for Maven IMHO -Stephen On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote: Oracle Java 5 and 6 are EOLed but Oracle continues to support
Re: [VOTE] Release Apache Maven Enforcer version 1.3.1
+1 Regards, Hervé Le vendredi 12 juillet 2013 23:12:02 Robert Scholte a écrit : Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=H tmlversion=19426 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11530sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-140/ https://repository.apache.org/content/repositories/maven-140/org/apache/mave n/enforcer/enforcer/1.3.1/enforcer-1.3.1-source-release.zip Staging site: http://maven.apache.org/enforcer-archives/enforcer-LATEST/ 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: Java version usage survey
What I do not really understand: - Say I am a company which are forced to run JDK1.5 because they have to recertificate everything due to Sarbains-Oxley or German GOBS. - Would I not force my developers to use the same tools to build they used for previous versions, then? - Maven 3 behaves slightly different from Maven 2, so propably they used Maven 2 back then and should stay with it. - Management not willing to upgrade the JDK should not invest either in upgrading the tool chain or any dependencies IMO. Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Tue, Jul 16, 2013 at 9:55 PM, Arnaud Héritier aherit...@gmail.com wrote: For now what is resulting from this thread is : * We do a survey to better know where our user are and were they are going * We check what is the status of our tools (toolchains co) to be sure how we can easily use versions of java older than the one required by maven * We discuss on the ML to clearly cover all aspects of such upgrades (core vs plugins ...) And from all of this we should be able to schedule and announce how we will update our prerequisites. WDYT ? From my point of view there is now urgency. It is just to advance on some subject as I know they aren't easy to solve (and dev products like jenkins are analyzing such changes too). Arnaud On Tue, Jul 16, 2013 at 8:54 PM, Fred Cooke fred.co...@gmail.com wrote: Just to clarify my comments: I can't and won't build anything with anything higher than J6 for the foreseeable future, maybe upto 2 years or so, who knows. J7 is purely a runtime option for users for me, same for J8. J5 is dead for both builds and runtime in my eyes. I'd prefer to maximise my choice by keeping M3 and plugins on J6, however I wouldn't cry if M3 itself went J7, but I would cry if the plugins went J7 without first releasing Git-functional versions of m-release-p and m-site-p. Even then, while wiping the tears away, I could hard code some fixes and release my own fork for my own use, no biggy. Preference: Don't exceed J6 as a requirement for Maven or plugins. Bottom line: I'll survive anything you do. 3 open sauce. Especially ketchup. Another 2c, there is some signature difference which can result in J6-clean source building to a J7-only binary using J7 javac. I forget the details, but IIRC it was on the MOJO list that I learned this. Unsure if it was added to the sniffer or not. Fred. On Tue, Jul 16, 2013 at 8:38 PM, Stéphane Nicoll stephane.nic...@gmail.comwrote: Yep. Sent from my iPhone On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote: Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box sitting beside me... powered off (the Sun Ultra T-20's are noisy don't you know) I only turn it on when I *need* windows and a virtual machine will not suffice (i.e. firmware updates on Samsung Galaxy S... which is now only used as a game console by my son) That has Java 1.4-1.7 on it but it is far from current in terms of AV and patches, so not something I would turn on for a quick test of a release. Effectively the lowest I can test releases is Java 1.6. It would be interesting to hear what the rest of the committers have as their testing capability. If very few committers have access to Java 1.5 across operating systems then I think the answer is clear... namely we would not be in a position to stand over a
Re: Java version usage survey
Look you chickens; until quite recently I kept a 1.3 JVM running on windows to do the occasional test of surefire on jdk 1.3. (I kept a vmware image since installing 1.3 on linux required surrendering your first born to Sauron) All your complaining about not being able to run 1.5 sounds like childish whining. On a more serious note, since we support all relevant new features in 1.6 1.7 already, the only real reason to move away from 1.5 (for me) is to get the improved generics notations of 1.7. 1.6 was about as boring a release as Sun ever managed to make. So it would seem to me like animal-sniffer at 1.5 level is the way to go until we can decide to move directly to 1.7? It would seem to me like we'll just have to rely on this kind of sniffing ? I still think 1.7 is at least a year away..? Most of plexus already has a java 7 compile time requirement right now, which means we can avoid using reflection for all kinds of stupid stuff. But since most of that is handled, we only really have the diamond notation left ? I don't think there's much to be gained by introducing a 1.7 library level for the rest of maven ? I'm looking for use cases outside what animal sniffer should be able to handle for us here? Jenkins also does a fairly nice JDK 1.5 test for most of our projects ? Kristian 16. juli 2013 kl. 02:07 skrev Arnaud Héritier aherit...@gmail.com: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible with Java 5 (And probably various plugins with Java 4). Couldn't it be interesting to see which JDKs our users are using to see how we can schedule the end of support of Java 5 (and more). Perhaps a removal of Java 5 support in 3.2 or 3.5 ... Perhaps with a survey like this : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform What do you think ? Useful ? Useless ?he - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
16. juli 2013 kl. 07:35 skrev Stephen Connolly stephen.alan.conno...@gmail.com: - have we good test coverage with toolchains? No. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.1 - Stable ?
Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Maven 3.1 - Stable ?
Typo on my part. There are 48 things to change when updating a release. I updated and triggered the publish an hour ago. I'm not sure when/how it updates. On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C.
Re: Maven 3.1 - Stable ?
On Tue, Jul 16, 2013 at 11:37 PM, Jason van Zyl ja...@tesla.io wrote: Typo on my part. There are 48 things to change when updating a release. Ok. I wasn't sure if it was intentional I agree, that's a pain to do a release :( I updated and triggered the publish an hour ago. I'm not sure when/how it updates. ok, no problem/urgency thx On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Enforcer version 1.3.1
On Fri, 12 Jul 2013 23:12:02 +0200 Robert Scholte rfscho...@apache.org wrote: +1, works fine to me, thanks, tony. Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=Htmlversion=19426 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11530status=1 Staging repo: https://repository.apache.org/content/repositories/maven-140/ https://repository.apache.org/content/repositories/maven-140/org/apache/maven/enforcer/enforcer/1.3.1/enforcer-1.3.1-source-release.zip Staging site: http://maven.apache.org/enforcer-archives/enforcer-LATEST/ 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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3.1 - Stable ?
On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote: Typo on my part. There are 48 things to change when updating a release. I updated and triggered the publish an hour ago. I'm not sure when/how it updates. Should be immediate (within a few seconds), assuming svnpubsub is running normally. On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
On 16 July 2013 21:52, Kristian Rosenvold kristian.rosenv...@zenior.nowrote: Look you chickens; until quite recently I kept a 1.3 JVM running on windows to do the occasional test of surefire on jdk 1.3. (I kept a vmware image since installing 1.3 on linux required surrendering your first born to Sauron) All your complaining about not being able to run 1.5 sounds like childish whining. On a more serious note, since we support all relevant new features in 1.6 1.7 already, the only real reason to move away from 1.5 (for me) is to get the improved generics notations of 1.7. 1.6 was about as boring a release as Sun ever managed to make. So it would seem to me like animal-sniffer at 1.5 level is the way to go until we can decide to move directly to 1.7? It would seem to me like we'll just have to rely on this kind of sniffing ? I still think 1.7 is at least a year away..? Most of plexus already has a java 7 compile time requirement right now, which means we can avoid using reflection for all kinds of stupid stuff. But since most of that is handled, we only really have the diamond notation left ? I don't think there's much to be gained by introducing a 1.7 library level for the rest of maven ? I'm looking for use cases outside what animal sniffer should be able to handle for us here? Jenkins also does a fairly nice JDK 1.5 test for most of our projects ? Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my personal view) Maven job type will be unable to run 1.5 Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) -Stephen Kristian 16. juli 2013 kl. 02:07 skrev Arnaud Héritier aherit...@gmail.com: Hi, Java 6 EOL was in feb and Maven and its plugins are always compatible with Java 5 (And probably various plugins with Java 4). Couldn't it be interesting to see which JDKs our users are using to see how we can schedule the end of support of Java 5 (and more). Perhaps a removal of Java 5 support in 3.2 or 3.5 ... Perhaps with a survey like this : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform What do you think ? Useful ? Useless ?he - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my personal view) Maven job type will be unable to run 1.5 The crappy one which doesn't work with Maven 3.1.0 too (I tested it this afternoon) Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) asJenkinsUser Me too if we backport features from the crappy maven integration into the freestyle job (automatic dependencies, post build deployment ..). What was done in Hudson was good from my point UI (excepted the GWT UI which was ugly) /asJenkinsUser
Re: Java version usage survey
On 16 July 2013 23:01, Arnaud Héritier aherit...@gmail.com wrote: Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my personal view) Maven job type will be unable to run 1.5 The crappy one which doesn't work with Maven 3.1.0 too (I tested it this afternoon) I'm sure Olivier will rush to try and defend that job type... Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) asJenkinsUser Me too if we backport features from the crappy maven integration into the freestyle job (automatic dependencies, post build deployment ..). What was done in Hudson was good from my point UI (excepted the GWT UI which was ugly) /asJenkinsUser Ahem... there are other ways to skin this cat... but the people who know have been sworn to secrecy under pain of being shot, hung, drawn and quartered before having the entire troupé of Riverdance dance on their grave... so you'll just have to wait a month of so to find out!
Re: Java version usage survey
On 17 July 2013 07:31, Arnaud Héritier aherit...@gmail.com wrote: Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) asJenkinsUser Me too if we backport features from the crappy maven integration into the freestyle job (automatic dependencies, post build deployment ..). What was done in Hudson was good from my point UI (excepted the GWT UI which was ugly) /asJenkinsUser Should we not improve the crappy Maven job for Jenkins? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java version usage survey
On 16 July 2013 23:25, Barrie Treloar baerr...@gmail.com wrote: On 17 July 2013 07:31, Arnaud Héritier aherit...@gmail.com wrote: Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) asJenkinsUser Me too if we backport features from the crappy maven integration into the freestyle job (automatic dependencies, post build deployment ..). What was done in Hudson was good from my point UI (excepted the GWT UI which was ugly) /asJenkinsUser Should we not improve the crappy Maven job for Jenkins? I have plans... and I may even have the OK to implement them... we'll see how much I get done - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3.1 - Stable ?
On Jul 16, 2013, at 5:42 PM, sebb seb...@gmail.com wrote: On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote: Typo on my part. There are 48 things to change when updating a release. I updated and triggered the publish an hour ago. I'm not sure when/how it updates. Should be immediate (within a few seconds), assuming svnpubsub is running normally. I've not found that to be the case generally. On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - 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 - the course of true love never did run smooth ... -- Shakespeare
Re: Java version usage survey
We generally follow the practice of building on the target platform using the tools of the target platform. EG on AIX using the same version of the JDK that WAS runs on (typically using Jenkins). That does not meant that I do not want to make use of the newer versions of maven, it's plugins and the features that they may offer; even on the older JDK's. Case in point: I was quite happy to substantially reduce our release times by running -T16 :-) In our case around 4-6 hours dropped to 38 minutes. :-) But perhaps I'm a real edge case. :-) -Chris On Wed, Jul 17, 2013 at 6:34 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: What I do not really understand: - Say I am a company which are forced to run JDK1.5 because they have to recertificate everything due to Sarbains-Oxley or German GOBS. - Would I not force my developers to use the same tools to build they used for previous versions, then? - Maven 3 behaves slightly different from Maven 2, so propably they used Maven 2 back then and should stay with it. - Management not willing to upgrade the JDK should not invest either in upgrading the tool chain or any dependencies IMO. Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Tue, Jul 16, 2013 at 9:55 PM, Arnaud Héritier aherit...@gmail.com wrote: For now what is resulting from this thread is : * We do a survey to better know where our user are and were they are going * We check what is the status of our tools (toolchains co) to be sure how we can easily use versions of java older than the one required by maven * We discuss on the ML to clearly cover all aspects of such upgrades (core vs plugins ...) And from all of this we should be able to schedule and announce how we will update our prerequisites. WDYT ? From my point of view there is now urgency. It is just to advance on some subject as I know they aren't easy to solve (and dev products like jenkins are analyzing such changes too). Arnaud On Tue, Jul 16, 2013 at 8:54 PM, Fred Cooke fred.co...@gmail.com wrote: Just to clarify my comments: I can't and won't build anything with anything higher than J6 for the foreseeable future, maybe upto 2 years or so, who knows. J7 is purely a runtime option for users for me, same for J8. J5 is dead for both builds and runtime in my eyes. I'd prefer to maximise my choice by keeping M3 and plugins on J6, however I wouldn't cry if M3 itself went J7, but I would cry if the plugins went J7 without first releasing Git-functional versions of m-release-p and m-site-p. Even then, while wiping the tears away, I could hard code some fixes and release my own fork for my own use, no biggy. Preference: Don't exceed J6 as a requirement for Maven or plugins. Bottom line: I'll survive anything you do. 3 open sauce. Especially ketchup. Another 2c, there is some signature difference which can result in J6-clean source building to a J7-only binary using J7 javac. I forget the details, but IIRC it was on the MOJO list that I learned this. Unsure if it was added to the sniffer or not. Fred. On Tue, Jul 16, 2013 at 8:38 PM, Stéphane Nicoll stephane.nic...@gmail.comwrote: Yep. Sent from my iPhone On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote: Can you tell me if now you can see the result : https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: I tucked away the last public debs of 1.5 and can release 1.5 indefinitely. In the release of the last security patch, it seems like Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't have it. Kristian Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com følgende: I rum mainly on OSX for client and some Linuxes for server - so client side is = JDK 1.6 // vänlig hälsning, // [sw: best regards], // // Lennart Jörelid 16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org: perso osx. So only = 1.6 2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com: Speaking as a Maven Developer... My primary development machine is OS-X. On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One that has some Java 1.5 and 1.6 versions on it... but I have not turned it on more than twice since March 2011... most likely I will wipe it and reinstall some more recent linux on it which will remove the older JDK versions leaving it with likely a 1.6 and a 1.7. I also have a windows box
Re: Java version usage survey
2013/7/17 Stephen Connolly stephen.alan.conno...@gmail.com: On 16 July 2013 23:01, Arnaud Héritier aherit...@gmail.com wrote: Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my personal view) Maven job type will be unable to run 1.5 The crappy one which doesn't work with Maven 3.1.0 too (I tested it this afternoon) I'm sure Olivier will rush to try and defend that job type... I prefer to keep my time to maybe update it to get it working with 3.1.x rather than waste my time on mailing list discussions. Can still keep trucking with a FreeStyle + Maven Build Step though (and I prefer that way anyway) asJenkinsUser Me too if we backport features from the crappy maven integration into the freestyle job (automatic dependencies, post build deployment ..). What was done in Hudson was good from my point UI (excepted the GWT UI which was ugly) /asJenkinsUser Ahem... there are other ways to skin this cat... but the people who know have been sworn to secrecy under pain of being shot, hung, drawn and quartered before having the entire troupé of Riverdance dance on their grave... so you'll just have to wait a month of so to find out! -- Olivier Lamy Ecetera: http://ecetera.com.au 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: [VOTE] Release Apache Maven Enforcer version 1.3.1
+1 2013/7/13 Robert Scholte rfscho...@apache.org: Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=Htmlversion=19426 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11530status=1 Staging repo: https://repository.apache.org/content/repositories/maven-140/ https://repository.apache.org/content/repositories/maven-140/org/apache/maven/enforcer/enforcer/1.3.1/enforcer-1.3.1-source-release.zip Staging site: http://maven.apache.org/enforcer-archives/enforcer-LATEST/ 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 -- Olivier Lamy Ecetera: http://ecetera.com.au 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: Maven 3.1 - Stable ?
On 16 July 2013 23:45, Jason van Zyl ja...@tesla.io wrote: On Jul 16, 2013, at 5:42 PM, sebb seb...@gmail.com wrote: On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote: Typo on my part. There are 48 things to change when updating a release. I updated and triggered the publish an hour ago. I'm not sure when/how it updates. Should be immediate (within a few seconds), assuming svnpubsub is running normally. I've not found that to be the case generally. In that case, maybe what you think is publishing is not actually publishing. I don't know how the Maven site is set up, but certainly the main ASF site is visible a few seconds - at most a minute - after making a update. The EU site sometimes takes a bit longer to catch up. The sites are directly checked out from the live SVN, and this happens very soon after checkin. If anything takes more than 5 minutes to become visible, either the system is down, or the change was not published to it. [Of course, remember to clear your browser cache] You can of course check the the file in SVN history to see what has happened. On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote: Hi, Do we consider the 3.1.0 as the latest stable ? On the download page there is a typo (?) http://maven.apache.org/download.cgi Maven 3.1.0 :This is the future of Maven (alpha status). On the homepage we always have the Get Maven 3.0.5 on the right http://maven.apache.org/index.html We also have an ad for ApacheCon NA 2013 that was in february - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - 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 - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
