Re: Re: Why does mvn compiile using java 1.3?
Hi, I have never seen any java application fail just because I run the version 7 VM. Even really old code still runs. A couple of Atlassian applications I work with in our department that didn't run (fine) with Java 7: - JIRA = 5.1.x (5.2 was released ~3 weeks ago) - Bamboo = 3.2.x (3.3 was released 11 october 2011) - Confluence = 4.1.x (4.2 was released 10 april 2012) etc. It took quite a long time for the manufacturer to implement the necessary changes to let their products work with Java 7. JIRA for example wouldn't even start correctly when using 1.7.* and instead threw lots of exceptions in its log, whereas for at least Confluence 4.1.x there were some workarounds to let it run with a JVM 7... In our department we had a very old legacy application written by some colleagues back in the days of Java 1.2 when the first Swing UI came out. They told me they had lots of problems with former Swing UI bugs and programmed workarounds to get the application finally work with Java 1.4. These workarounds didn't work correct anymore with Java 5 (Swing bugs were fixed?), i.e. the application's UI had some nice features a.k.a bugs :-o Unfortunately they weren't given the time to fix them (you know, the usual problems with sales that had other priorities...) so they had to stick with Java 1.4 until ~2.5 years ago (!), until the application finally died about one year ago. That's life... Regards Thorsten
Re: Re: Why does mvn compiile using java 1.3?
Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly (similar to what resources plugin does with encoding). I would actually go as far as warning people if they explicitly specify version 1.7. There are a lot of folks who think they are so great using the newest versions, but it actually may cause problems. We have a pretty big and old application which is currently developed and run on JDK 1.6. There were issues with 1.7, but they were fixed. The real problem is updating customers - there are about 300 different installations supported by our teams. It's actually pretty difficult to get on customers servers, for each you have to contact their IT and schedule a session and downtime. The problem is the following. Real life experience: I wanted to use Adobe XMP core and luckily, it was in Maven central. But not so luckily, it was compiled with JDK 1.7 (without any need) and JDK 1.6 refused to compile with it. I had to get the sources, compile with JDK 1.6 and put it to our local Nexus. If maven-compiler-plugin default version is updated to 1.7, I expect more artifacts built for 1.7 without any need. Regards, htfv (Aliaksei Lahachou) On Fri, Nov 30, 2012 at 12:01 PM, Thorsten Heit thorsten.h...@vkb.dewrote: Hi, I have never seen any java application fail just because I run the version 7 VM. Even really old code still runs. A couple of Atlassian applications I work with in our department that didn't run (fine) with Java 7: - JIRA = 5.1.x (5.2 was released ~3 weeks ago) - Bamboo = 3.2.x (3.3 was released 11 october 2011) - Confluence = 4.1.x (4.2 was released 10 april 2012) etc. It took quite a long time for the manufacturer to implement the necessary changes to let their products work with Java 7. JIRA for example wouldn't even start correctly when using 1.7.* and instead threw lots of exceptions in its log, whereas for at least Confluence 4.1.x there were some workarounds to let it run with a JVM 7... In our department we had a very old legacy application written by some colleagues back in the days of Java 1.2 when the first Swing UI came out. They told me they had lots of problems with former Swing UI bugs and programmed workarounds to get the application finally work with Java 1.4. These workarounds didn't work correct anymore with Java 5 (Swing bugs were fixed?), i.e. the application's UI had some nice features a.k.a bugs :-o Unfortunately they weren't given the time to fix them (you know, the usual problems with sales that had other priorities...) so they had to stick with Java 1.4 until ~2.5 years ago (!), until the application finally died about one year ago. That's life... Regards Thorsten
Re: Why does mvn compiile using java 1.3?
We are not talking about making Maven only run on 7. We just want to move the default compiler to 6 (at least) or 7. You can always set it back to 1.3. It is just odd for new projects to start up with Maven and suddenly find than Maven wants to use 1.3 to compile code. Please, no more warnings about perfectly correct behaviour. I already get a bogus warning message if my parent pom and my project are in the same group which is exactly the way its supposed to be. There is nothing wrong with building with Java 7 if that is the run-time that you want. Your point about people building shared libraries is very good. I don't know of any convention or build process that will indicate that a Maven Artifact requires 1.7 (or 1.6 or 1.5) to run properly. I guess that the library author will have to decide how far back into Java history needs to be supported. Does Apache have any policies or guidelines or Best Practices with regard to the choice of Java version with which to publish libraries? Ron On 30/11/2012 8:42 AM, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly (similar to what resources plugin does with encoding). I would actually go as far as warning people if they explicitly specify version 1.7. There are a lot of folks who think they are so great using the newest versions, but it actually may cause problems. We have a pretty big and old application which is currently developed and run on JDK 1.6. There were issues with 1.7, but they were fixed. The real problem is updating customers - there are about 300 different installations supported by our teams. It's actually pretty difficult to get on customers servers, for each you have to contact their IT and schedule a session and downtime. The problem is the following. Real life experience: I wanted to use Adobe XMP core and luckily, it was in Maven central. But not so luckily, it was compiled with JDK 1.7 (without any need) and JDK 1.6 refused to compile with it. I had to get the sources, compile with JDK 1.6 and put it to our local Nexus. If maven-compiler-plugin default version is updated to 1.7, I expect more artifacts built for 1.7 without any need. Regards, htfv (Aliaksei Lahachou) On Fri, Nov 30, 2012 at 12:01 PM, Thorsten Heit thorsten.h...@vkb.dewrote: Hi, I have never seen any java application fail just because I run the version 7 VM. Even really old code still runs. A couple of Atlassian applications I work with in our department that didn't run (fine) with Java 7: - JIRA = 5.1.x (5.2 was released ~3 weeks ago) - Bamboo = 3.2.x (3.3 was released 11 october 2011) - Confluence = 4.1.x (4.2 was released 10 april 2012) etc. It took quite a long time for the manufacturer to implement the necessary changes to let their products work with Java 7. JIRA for example wouldn't even start correctly when using 1.7.* and instead threw lots of exceptions in its log, whereas for at least Confluence 4.1.x there were some workarounds to let it run with a JVM 7... In our department we had a very old legacy application written by some colleagues back in the days of Java 1.2 when the first Swing UI came out. They told me they had lots of problems with former Swing UI bugs and programmed workarounds to get the application finally work with Java 1.4. These workarounds didn't work correct anymore with Java 5 (Swing bugs were fixed?), i.e. the application's UI had some nice features a.k.a bugs :-o Unfortunately they weren't given the time to fix them (you know, the usual problems with sales that had other priorities...) so they had to stick with Java 1.4 until ~2.5 years ago (!), until the application finally died about one year ago. That's life... Regards Thorsten -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
I understand that it's not about making Maven run on 7. The problem is that people build artifacts on 7 (which will become more often if it's default) and deploy these artifacts to repository, then people who are using JDK 6 will not be able to compile with this artifacts (the target JDK is written somewhere in .class files and older compilers will refuse to accept them). Try building a project on JDK 6 which depends on com.adobe.xmp:xmpcore:5.1.2, it will fail. But the XMP core source can be built with JDK 5. Whoever uploaded this artifact to Maven central made it unusable with JDK 5 or 6 simply because he compiled it with JDK 7. On Fri, Nov 30, 2012 at 3:39 PM, Ron Wheeler rwhee...@artifact-software.com wrote: We are not talking about making Maven only run on 7. We just want to move the default compiler to 6 (at least) or 7. You can always set it back to 1.3. It is just odd for new projects to start up with Maven and suddenly find than Maven wants to use 1.3 to compile code. Please, no more warnings about perfectly correct behaviour. I already get a bogus warning message if my parent pom and my project are in the same group which is exactly the way its supposed to be. There is nothing wrong with building with Java 7 if that is the run-time that you want. Your point about people building shared libraries is very good. I don't know of any convention or build process that will indicate that a Maven Artifact requires 1.7 (or 1.6 or 1.5) to run properly. I guess that the library author will have to decide how far back into Java history needs to be supported. Does Apache have any policies or guidelines or Best Practices with regard to the choice of Java version with which to publish libraries? Ron On 30/11/2012 8:42 AM, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly (similar to what resources plugin does with encoding). I would actually go as far as warning people if they explicitly specify version 1.7. There are a lot of folks who think they are so great using the newest versions, but it actually may cause problems. We have a pretty big and old application which is currently developed and run on JDK 1.6. There were issues with 1.7, but they were fixed. The real problem is updating customers - there are about 300 different installations supported by our teams. It's actually pretty difficult to get on customers servers, for each you have to contact their IT and schedule a session and downtime. The problem is the following. Real life experience: I wanted to use Adobe XMP core and luckily, it was in Maven central. But not so luckily, it was compiled with JDK 1.7 (without any need) and JDK 1.6 refused to compile with it. I had to get the sources, compile with JDK 1.6 and put it to our local Nexus. If maven-compiler-plugin default version is updated to 1.7, I expect more artifacts built for 1.7 without any need. Regards, htfv (Aliaksei Lahachou) On Fri, Nov 30, 2012 at 12:01 PM, Thorsten Heit thorsten.h...@vkb.de wrote: Hi, I have never seen any java application fail just because I run the version 7 VM. Even really old code still runs. A couple of Atlassian applications I work with in our department that didn't run (fine) with Java 7: - JIRA = 5.1.x (5.2 was released ~3 weeks ago) - Bamboo = 3.2.x (3.3 was released 11 october 2011) - Confluence = 4.1.x (4.2 was released 10 april 2012) etc. It took quite a long time for the manufacturer to implement the necessary changes to let their products work with Java 7. JIRA for example wouldn't even start correctly when using 1.7.* and instead threw lots of exceptions in its log, whereas for at least Confluence 4.1.x there were some workarounds to let it run with a JVM 7... In our department we had a very old legacy application written by some colleagues back in the days of Java 1.2 when the first Swing UI came out. They told me they had lots of problems with former Swing UI bugs and programmed workarounds to get the application finally work with Java 1.4. These workarounds didn't work correct anymore with Java 5 (Swing bugs were fixed?), i.e. the application's UI had some nice features a.k.a bugs :-o Unfortunately they weren't given the time to fix them (you know, the usual problems with sales that had other priorities...) so they had to stick with Java 1.4 until ~2.5 years ago (!), until the application finally died about one year ago. That's life... Regards Thorsten -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional
Re: Re: Why does mvn compiile using java 1.3?
On 30 November 2012 13:42, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly I too am in favour of maintaining the current behaviour, explicit declaration of version, or you get 1.3. Explicit versioning is what Maven is all about! cheers Tim -- Tim Pizey - http://pizey.net/~timp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re: Why does mvn compiile using java 1.3?
Actually the current behaviour is 1.5 is using Maven Compiler Plugin 2.5 or newer (might be 2.4 but I'd need to check) With Maven 3.1.0, the version of the Maven Compiler Plugin that you get if you have not locked down plugin versions will be upped to a version with this new default. So if you don't lock things down and live on the latest Maven, out of the box you will get Java 1.5 compatible classes until you lock things down. On 30 November 2012 15:35, Tim Pizey tim.pi...@gmail.com wrote: On 30 November 2012 13:42, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly I too am in favour of maintaining the current behaviour, explicit declaration of version, or you get 1.3. Explicit versioning is what Maven is all about! cheers Tim -- Tim Pizey - http://pizey.net/~timp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re: Why does mvn compiile using java 1.3?
BTW I favour keeping at 1.5. That is the highest version we can guarantee a user of Maven 3.1.0's JDK can compile at (because in order to run Maven 2.2.1+ you need Java 1.5) so unless they are using toolchains (which to be honest, given the lack of bugs reported around toolchains and my knowledge of what kind of bugs we should expect to see reported [xyz plugin doesn't support toolchains] they are not using) that is a good and sensible default. If we set the default higher, then a user will download Maven 3.1.0 having seen it say (all you need is JDK 1.5 or higher) and try and build some code and bomb out with -source 1.6 is unknown and say Maven is shit. So as I see it. The Core plugins (i.e. the ones hosted at org.apache.maven.plugins) or maybe the core plugins involved in the default lifecycles, cannot assume Java higher than the minimum required to run the Maven version they run on. Core is still at 1.5. So therefore the highest default the compiler plugin can consider at this point in time is 1.5. I will -1 any change to that default above the min required by core unless somebody gives a compelling argument for the change, and I do not see such a compelling argument. (I am not saying I will -1 upping the min JDK required by Maven, just that compiler's default cannot be higher than the minimum version required by Maven) -Stephen On 30 November 2012 15:53, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Actually the current behaviour is 1.5 is using Maven Compiler Plugin 2.5 or newer (might be 2.4 but I'd need to check) With Maven 3.1.0, the version of the Maven Compiler Plugin that you get if you have not locked down plugin versions will be upped to a version with this new default. So if you don't lock things down and live on the latest Maven, out of the box you will get Java 1.5 compatible classes until you lock things down. On 30 November 2012 15:35, Tim Pizey tim.pi...@gmail.com wrote: On 30 November 2012 13:42, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly I too am in favour of maintaining the current behaviour, explicit declaration of version, or you get 1.3. Explicit versioning is what Maven is all about! cheers Tim -- Tim Pizey - http://pizey.net/~timp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re: Why does mvn compiile using java 1.3?
You have been getting 1.5 by default for a long time. At least since the 2.3 release of the compiler plugin.. On Fri, November 30, 2012 7:35 am, Tim Pizey wrote: On 30 November 2012 13:42, Aliaksei Lahachou wrote: Hello everyone, I'm am against updating default version to 1.7. My favourite option would be to use the lowest possible version of JDK and give a warning if version is not specified explicitly I too am in favour of maintaining the current behaviour, explicit declaration of version, or you get 1.3. Explicit versioning is what Maven is all about! cheers Tim -- Tim Pizey - http://pizey.net/~timp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Point is, unless you are using java 1.3, until 2.5ish you have had the source1.5/source and target1.5/target in your pom anyway. So changing the default from 1.5 to 1.7 will not make life any harder for you as you'll just be putting back in the source1.5/source and target1.5/target (assuming you didn't keep it there, because its safer) On 29 November 2012 10:06, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: I don't love that as a default! because there are OS which do not yet have up-to-date Open JDK 7 or JDK 8. And we do not have influence to the company not delivering as they should, years after promising that Java is what we need for future OpenVMS developments. Or has someone knowledge when HP releases a Open JDK 7.0? And yes, we know, changing a platform with 25 to 30 year old business algorithms written in PASCAL, today integrated with Java to form part of a larger web-service server on OpenVMS is not so easy. Legacy code has value too, not only legacy data! Josef -Ursprüngliche Nachricht- Von: Mark Derricutt [mailto:m...@talios.com] Gesendet: Mittwoch, 28. November 2012 19:36 An: Maven Users List Betreff: Re: Why does mvn compiile using java 1.3? Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct.
Re: Why does mvn compiile using java 1.3?
That is a fair point. And I concur, that until core ups its minimum JRE requirement, compiler shouldn't move past that... Raises the question should core up to 1.6... I don't see a pressing need yet... Lambdas are not until 1.8, and we don't do the crazy generics stuff that, for example, forced Jenkins to require 1.6 to build. So without a pressing need, I think core should stay on 1.5 for now On 29 November 2012 10:39, Jochen Wiedmann jochen.wiedm...@gmail.comwrote: Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct.
Re: Why does mvn compiile using java 1.3?
Java 7 has been out for almost a year and a half. Java 6 was released in 2006 What keeps people on old versions for over 8 years(1.5)? We have tried to keep up with the times and feel that we got a lot of performance improvements over time without any pain as we changed versions. There does not seem to be any problem using Maven to compile Java version 7. Java 7 certainly runs Maven just fine. Are we not just talking about changing the default to 7 not forcing everyone to use 7 or run their IDE on 7 or am I missing something? They can still select the compiler that they want if they are not up to date. Ron On 29/11/2012 9:19 AM, Stephen Connolly wrote: That is a fair point. And I concur, that until core ups its minimum JRE requirement, compiler shouldn't move past that... Raises the question should core up to 1.6... I don't see a pressing need yet... Lambdas are not until 1.8, and we don't do the crazy generics stuff that, for example, forced Jenkins to require 1.6 to build. So without a pressing need, I think core should stay on 1.5 for now On 29 November 2012 10:39, Jochen Wiedmann jochen.wiedm...@gmail.comwrote: Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
People is stuck for old Java versions due to the fact that for example organizations are using IBM WebSphere and do not upgrade those immediately when new version of WAS is released. WAS 6.1 which was released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7 which has JDK 6 support build in from beginning 2008. Just latest WAS 8.5 has possibility to use JDK 7. Lot of organizations is still running with WAS 6 . Markku On 11/29/2012 04:55 PM, Ron Wheeler wrote: Java 7 has been out for almost a year and a half. Java 6 was released in 2006 What keeps people on old versions for over 8 years(1.5)? We have tried to keep up with the times and feel that we got a lot of performance improvements over time without any pain as we changed versions. There does not seem to be any problem using Maven to compile Java version 7. Java 7 certainly runs Maven just fine. Are we not just talking about changing the default to 7 not forcing everyone to use 7 or run their IDE on 7 or am I missing something? They can still select the compiler that they want if they are not up to date. Ron On 29/11/2012 9:19 AM, Stephen Connolly wrote: That is a fair point. And I concur, that until core ups its minimum JRE requirement, compiler shouldn't move past that... Raises the question should core up to 1.6... I don't see a pressing need yet... Lambdas are not until 1.8, and we don't do the crazy generics stuff that, for example, forced Jenkins to require 1.6 to build. So without a pressing need, I think core should stay on 1.5 for now On 29 November 2012 10:39, Jochen Wiedmann jochen.wiedm...@gmail.comwrote: Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 10:17 AM, Markku Saarela wrote: People is stuck for old Java versions due to the fact that for example organizations are using IBM WebSphere and do not upgrade those immediately when new version of WAS is released. WAS 6.1 which was released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7 which has JDK 6 support build in from beginning 2008. Just latest WAS 8.5 has possibility to use JDK 7. Lot of organizations is still running with WAS 6 . You are saying that for those organizations, Java 6 and 7 broke upward compatibility? We never had that problem but I guess IBM's coding was a bit too tied to features that were deprecated and then removed in java 6 or 7. What would it mean for them if Maven had a default of Java 7. Could they not just change the Java setting to 1.4 or 1.3 and still run Maven and compile their Websphere apps? Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? I think that we have done that in the past where our app was being built using 1.5 but we had our Eclipse and Maven running in a 1.6VM. Ron Markku On 11/29/2012 04:55 PM, Ron Wheeler wrote: Java 7 has been out for almost a year and a half. Java 6 was released in 2006 What keeps people on old versions for over 8 years(1.5)? We have tried to keep up with the times and feel that we got a lot of performance improvements over time without any pain as we changed versions. There does not seem to be any problem using Maven to compile Java version 7. Java 7 certainly runs Maven just fine. Are we not just talking about changing the default to 7 not forcing everyone to use 7 or run their IDE on 7 or am I missing something? They can still select the compiler that they want if they are not up to date. Ron On 29/11/2012 9:19 AM, Stephen Connolly wrote: That is a fair point. And I concur, that until core ups its minimum JRE requirement, compiler shouldn't move past that... Raises the question should core up to 1.6... I don't see a pressing need yet... Lambdas are not until 1.8, and we don't do the crazy generics stuff that, for example, forced Jenkins to require 1.6 to build. So without a pressing need, I think core should stay on 1.5 for now On 29 November 2012 10:39, Jochen Wiedmann jochen.wiedm...@gmail.comwrote: Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 12:01 PM, Curtis Rueden wrote: Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. I would be surprised if this is true since it is certainly possible to compile with Java7 and to run Maven in a Java7 VM. I would not expect changing a default value to affect the running of Maven. I certainly am not suggesting doing anything to Maven itself that would make it so that it would not run in a Java5 VM I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. Ron What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Why does mvn compiile using java 1.3?
You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 On 29 November 2012 17:25, Ron Wheeler rwhee...@artifact-software.comwrote: On 29/11/2012 12:01 PM, Curtis Rueden wrote: Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. I would be surprised if this is true since it is certainly possible to compile with Java7 and to run Maven in a Java7 VM. I would not expect changing a default value to affect the running of Maven. I certainly am not suggesting doing anything to Maven itself that would make it so that it would not run in a Java5 VM I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. Ron What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 12:48 PM, Stephen Connolly wrote: You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 Not sure that I understand how this follows. The target compiler should not determine the Java VM that Maven runs in. I believe that I can compile 1.5 while running maven in a Java 7 VM. Ron On 29 November 2012 17:25, Ron Wheeler rwhee...@artifact-software.com mailto:rwhee...@artifact-software.com wrote: On 29/11/2012 12:01 PM, Curtis Rueden wrote: Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. I would be surprised if this is true since it is certainly possible to compile with Java7 and to run Maven in a Java7 VM. I would not expect changing a default value to affect the running of Maven. I certainly am not suggesting doing anything to Maven itself that would make it so that it would not run in a Java5 VM I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. Ron What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com mailto:rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Why does mvn compiile using java 1.3?
I was only saying that why organizations are not moving to JDK 7. Lot of those organizations has policy to use only that JDK also for devepment , so you cannot install JDK 7. I know you can run Maven over Java7 with older projects with some restrictions. One is if you project use jasper-reports-plugin which generates classes with that Java version which you are running Maven and then fails to use them because the Java class files are version 51.0 and 50,0 is required and build fails. MArkku On 11/29/2012 06:46 PM, Ron Wheeler wrote: On 29/11/2012 10:17 AM, Markku Saarela wrote: People is stuck for old Java versions due to the fact that for example organizations are using IBM WebSphere and do not upgrade those immediately when new version of WAS is released. WAS 6.1 which was released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7 which has JDK 6 support build in from beginning 2008. Just latest WAS 8.5 has possibility to use JDK 7. Lot of organizations is still running with WAS 6 . You are saying that for those organizations, Java 6 and 7 broke upward compatibility? We never had that problem but I guess IBM's coding was a bit too tied to features that were deprecated and then removed in java 6 or 7. What would it mean for them if Maven had a default of Java 7. Could they not just change the Java setting to 1.4 or 1.3 and still run Maven and compile their Websphere apps? Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? I think that we have done that in the past where our app was being built using 1.5 but we had our Eclipse and Maven running in a 1.6VM. Ron Markku On 11/29/2012 04:55 PM, Ron Wheeler wrote: Java 7 has been out for almost a year and a half. Java 6 was released in 2006 What keeps people on old versions for over 8 years(1.5)? We have tried to keep up with the times and feel that we got a lot of performance improvements over time without any pain as we changed versions. There does not seem to be any problem using Maven to compile Java version 7. Java 7 certainly runs Maven just fine. Are we not just talking about changing the default to 7 not forcing everyone to use 7 or run their IDE on 7 or am I missing something? They can still select the compiler that they want if they are not up to date. Ron On 29/11/2012 9:19 AM, Stephen Connolly wrote: That is a fair point. And I concur, that until core ups its minimum JRE requirement, compiler shouldn't move past that... Raises the question should core up to 1.6... I don't see a pressing need yet... Lambdas are not until 1.8, and we don't do the crazy generics stuff that, for example, forced Jenkins to require 1.6 to build. So without a pressing need, I think core should stay on 1.5 for now On 29 November 2012 10:39, Jochen Wiedmann jochen.wiedm...@gmail.comwrote: Leaving aside questions of compatibility, Java 7 as compiler default would be a poor choice. After all, that would require JRE 7 as a standard for running Maven, or using one of the Eclipse compilers. Otherwise, that would be unsupported by the compiler. On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- The best argument for celibacy is that the clergy will sooner or later become extinct. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Surely the change here is ONLY with the maven-compiler-plugin and affects what it puts as the --source and --target arguments to javac when compiler - I don't see why that should affect core? I admit I'm not really sure how m-c-p relates down into plexus-compiler and the compiler infrastructure, is javac always run in the same JVM as the one maven runs under? Personally - even if one is -targetting- an older JVM they should at least HAVE the new JVM - runs much faster IMHO. Ron Wheeler wrote: If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to1.7 while keeping Maven core itself compatible with1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java1.5, as Stephen suggested. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Not would but I hazard an argument to say could, there are subtle API -signature- changes that make targetting older bytecode problematic, aka from JDK5-6 I believe there were some methods ( class escapes me now ) that used to take a String but now take a CharSequence, source compatible but runtime-linker incompatible when resolving the method. If building an older -target IMHO one should always use the toolchains plugin or switch the whole VM to ensure the bootclasspath of the compile uses the appropriate one. If we did do this change - could we not have m-c-p make a big visible WARNING about not locking down the source/target like we have with no-versions for plugins? Ron Wheeler wrote: On 29/11/2012 12:48 PM, Stephen Connolly wrote: You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 Not sure that I understand how this follows. The target compiler should not determine the Java VM that Maven runs in. I believe that I can compile 1.5 while running maven in a Java 7 VM. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
It was a response to I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. For the Maven (core) developers to take advantage of the newer features, we would need to up the source level we compile core with. JavaC will allow source less than target but not the other way around, so if we want to use the newer features in core, we force all Maven users to have to run core with a newer version of Maven. At this point in time I do not see any compelling features in 1.7 which are worth the difference. If it turns out that a core library we use needs a newer version of Java because that core library needed the newer language features, then we would have to consider upgrading core to use the newer version of that core library. The only feature in 1.7 that we would benefit from is the try with resources... which is not that big a difference. 1.8's lambdas is a different story though... but it will likely be a good while before we can consider alienating all the pre 1.8 users On 29 November 2012 18:14, Ron Wheeler rwhee...@artifact-software.comwrote: On 29/11/2012 12:48 PM, Stephen Connolly wrote: You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 Not sure that I understand how this follows. The target compiler should not determine the Java VM that Maven runs in. I believe that I can compile 1.5 while running maven in a Java 7 VM. Ron On 29 November 2012 17:25, Ron Wheeler rwhee...@artifact-software.comwrote: On 29/11/2012 12:01 PM, Curtis Rueden wrote: Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. I would be surprised if this is true since it is certainly possible to compile with Java7 and to run Maven in a Java7 VM. I would not expect changing a default value to affect the running of Maven. I certainly am not suggesting doing anything to Maven itself that would make it so that it would not run in a Java5 VM I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. Ron What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 2:14 PM, Mark Derricutt wrote: Not would but I hazard an argument to say could, there are subtle API -signature- changes that make targetting older bytecode problematic, aka from JDK5-6 I believe there were some methods ( class escapes me now ) that used to take a String but now take a CharSequence, source compatible but runtime-linker incompatible when resolving the method. I have never seen any java application fail just because I run the version 7 VM. Even really old code still runs. If building an older -target IMHO one should always use the toolchains plugin or switch the whole VM to ensure the bootclasspath of the compile uses the appropriate one. I only use Eclipse to compile but I am able to specify any run-time that I have installed to compile code even if my Eclipse and Maven run in Java 7 VM. If we did do this change - could we not have m-c-p make a big visible WARNING about not locking down the source/target like we have with no-versions for plugins? Ron Wheeler wrote: On 29/11/2012 12:48 PM, Stephen Connolly wrote: You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 Not sure that I understand how this follows. The target compiler should not determine the Java VM that Maven runs in. I believe that I can compile 1.5 while running maven in a Java 7 VM. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 2:27 PM, Stephen Connolly wrote: It was a response to I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. For the Maven (core) developers to take advantage of the newer features, we would need to up the source level we compile core with. JavaC will allow source less than target but not the other way around, so if we want to use the newer features in core, we force all Maven users to have to run core with a newer version of Maven. That is what I thought when I made that comment. At this point in time I do not see any compelling features in 1.7 which are worth the difference. No annotations that strike your fancy? If it turns out that a core library we use needs a newer version of Java because that core library needed the newer language features, then we would have to consider upgrading core to use the newer version of that core library. The only feature in 1.7 that we would benefit from is the try with resources... which is not that big a difference. 1.8's lambdas is a different story though... but it will likely be a good while before we can consider alienating all the pre 1.8 users It would be interesting to see where the Maven users are WRT to Java environments. I can not imagine that most developers are struggling with old hardware and OSs. Programmer productivity is usually a big concern and having someone running a Pentium or old Apple with 512 Mb of memory and trying to run Eclipse/Netbeans with Maven seems like a horrible way to save $400. On 29 November 2012 18:14, Ron Wheeler rwhee...@artifact-software.com mailto:rwhee...@artifact-software.com wrote: On 29/11/2012 12:48 PM, Stephen Connolly wrote: You only get the new language features from after 1.5 if target 1.5, so switching core to use the newer features would make core incompatible with running on 1.5 Not sure that I understand how this follows. The target compiler should not determine the Java VM that Maven runs in. I believe that I can compile 1.5 while running maven in a Java 7 VM. Ron On 29 November 2012 17:25, Ron Wheeler rwhee...@artifact-software.com mailto:rwhee...@artifact-software.com wrote: On 29/11/2012 12:01 PM, Curtis Rueden wrote: Hi Ron, Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3 compiler? If you have a JRE7 VM available, then sure. If JRE7 is not available for your platform, then it must remain possible to run Maven with an older JRE, or else no more Maven for you. I do not know enough about Maven internals to know if it would be feasible to increase the default source/target version to 1.7 while keeping Maven core itself compatible with 1.5, though. From Jochen Stephen's exchange, it sounds like maybe not. If so, then my vote is for Maven core to remain compatible with Java 1.5, as Stephen suggested. I would be surprised if this is true since it is certainly possible to compile with Java7 and to run Maven in a Java7 VM. I would not expect changing a default value to affect the running of Maven. I certainly am not suggesting doing anything to Maven itself that would make it so that it would not run in a Java5 VM I am sure that some of the Maven developers would like to use some of the new Java features to make the coding easier. Ron What keeps people on old versions for over 8 years(1.5)? One reason is old hardware. For example, if you have a Mac PowerPC, you are stuck on OS X 10.5 Leopard, which will never run Java 7. Another reason is old software. If you run OS X 10.6 Snow Leopard, you are stuck with Java 6, since the OpenJDK7 and Oracle JDK 7 projects decided to require 10.7 Lion or newer. This might be OK if upgrading were free, and/or if Lion were strictly an upgrade, but it actually removes functionality (e.g., Rosetta). When deciding whether to start requiring Java 6 for some of our OSS projects, we took at look at our usage statistics, and found that (as of ~1 year ago) more than 10% of our total user base ran OS X 10.5 or earlier. So we decided to wait a bit longer. Regards, Curtis -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com mailto:rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Ron Wheeler President Artifact Software Inc email:rwhee...@artifact-software.com
Re: Why does mvn compiile using java 1.3?
Most serious users of Maven start out by building and releasing a common parent POM for their corporation or workgroup. This locks down plugin versions and configures core plugins such as the maven-compiler-plugin. So the old default to 1.3 was never a very serious inconvenience, since it's just a line or two as part of the overall process. Please don't even suggest the idea that we'd default Maven to 1.7. Taken as a lump, the Java development community is very slow to adopt new versions of Java, thanks in part to the disfunctions of Sun and Oracle that occupied the last few years. As for the core devs, no, un-uh. We have our own constraints, and requiring Java 1.7 to contribute to Maven would gratuitously exclude. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 2:58 PM, Benson Margulies wrote: Most serious users of Maven start out by building and releasing a common parent POM for their corporation or workgroup. This locks down plugin versions and configures core plugins such as the maven-compiler-plugin. So the old default to 1.3 was never a very serious inconvenience, since it's just a line or two as part of the overall process. Please don't even suggest the idea that we'd default Maven to 1.7. It would be good to know what new Maven adopters are intending to use as development platforms. As you correctly point out, the old-timers have already figured out how to set up the version that they want to use. Taken as a lump, the Java development community is very slow to adopt new versions of Java, thanks in part to the disfunctions of Sun and Oracle that occupied the last few years. I would be surprised if a new Maven user would be starting a new project on a version of Java earlier than 7 given that it has been out for so long. I suppose that there are some users who are new to Maven but are converting an old project that has its own history. We stay pretty current but it does take a few months to get the time to switch. Is there any way to find out what new users are using as their Java compilers. Ron As for the core devs, no, un-uh. We have our own constraints, and requiring Java 1.7 to contribute to Maven would gratuitously exclude. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
On Thu, Nov 29, 2012 at 3:41 PM, Ron Wheeler rwhee...@artifact-software.com wrote: On 29/11/2012 2:58 PM, Benson Margulies wrote: Most serious users of Maven start out by building and releasing a common parent POM for their corporation or workgroup. This locks down plugin versions and configures core plugins such as the maven-compiler-plugin. So the old default to 1.3 was never a very serious inconvenience, since it's just a line or two as part of the overall process. Please don't even suggest the idea that we'd default Maven to 1.7. It would be good to know what new Maven adopters are intending to use as development platforms. As you correctly point out, the old-timers have already figured out how to set up the version that they want to use. Taken as a lump, the Java development community is very slow to adopt new versions of Java, thanks in part to the disfunctions of Sun and Oracle that occupied the last few years. I would be surprised if a new Maven user would be starting a new project on a version of Java earlier than 7 given that it has been out for so long. I suppose that there are some users who are new to Maven but are converting an old project that has its own history. We stay pretty current but it does take a few months to get the time to switch. One of us will certainly be surprised. I know many people who still live under a '1.5' policy, and many more who live under a '1.6' policy. I don't think I know anyone professionally who is depending on 1.7. The slowness of policy, certification, and other bureaucracy is not to be underestimated. Is there any way to find out what new users are using as their Java compilers. Remember that many 'new maven users' are porting existing code bases, with existing dependencies, and existing customer obligations, to maven. Ron As for the core devs, no, un-uh. We have our own constraints, and requiring Java 1.7 to contribute to Maven would gratuitously exclude. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
On 29/11/2012 9:06 PM, Benson Margulies wrote: On Thu, Nov 29, 2012 at 3:41 PM, Ron Wheeler rwhee...@artifact-software.com wrote: On 29/11/2012 2:58 PM, Benson Margulies wrote: Most serious users of Maven start out by building and releasing a common parent POM for their corporation or workgroup. This locks down plugin versions and configures core plugins such as the maven-compiler-plugin. So the old default to 1.3 was never a very serious inconvenience, since it's just a line or two as part of the overall process. Please don't even suggest the idea that we'd default Maven to 1.7. It would be good to know what new Maven adopters are intending to use as development platforms. As you correctly point out, the old-timers have already figured out how to set up the version that they want to use. Taken as a lump, the Java development community is very slow to adopt new versions of Java, thanks in part to the disfunctions of Sun and Oracle that occupied the last few years. I would be surprised if a new Maven user would be starting a new project on a version of Java earlier than 7 given that it has been out for so long. I suppose that there are some users who are new to Maven but are converting an old project that has its own history. We stay pretty current but it does take a few months to get the time to switch. One of us will certainly be surprised. I know many people who still live under a '1.5' policy, and many more who live under a '1.6' policy. I don't think I know anyone professionally who is depending on 1.7. The slowness of policy, certification, and other bureaucracy is not to be underestimated. You do now. I am not too surprised actually. Is there any way to find out what new users are using as their Java compilers. Remember that many 'new maven users' are porting existing code bases, with existing dependencies, and existing customer obligations, to maven. True but I would like to know what the breakdown actually is. Do we have any idea about the distribution of the people who are adopting Maven. Ron As for the core devs, no, un-uh. We have our own constraints, and requiring Java 1.7 to contribute to Maven would gratuitously exclude. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
I use mvn on the command line. I actually solved the problem by setting the
java version explicitly. I have jdk 1.6.0_33. I found some things on
various sites which suggested mvn always compiles in 1.3 mode. You might
not notice this in an IDE (if it is true) since your IDE is likely to fix
this for you. After all, you also have an explicit java version in your IDE.
mvg,
Jasper
On Fri, Nov 16, 2012 at 4:42 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
What IDE are you using.
If your colleagues are using the same pom, you need to look at your IDE
setup.
For example, Eclipse will let you select any of the available compilers.
Ron
On 16/11/2012 8:21 AM, John Patrick wrote:
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-8/project.custom.encoding
project.custom.java.version1.6/project.custom.java.version
maven.compiler.source${project.custom.java.version}/maven.compiler.source
maven.compiler.target${project.custom.java.version}/maven.compiler.target
project.build.sourceEncoding${project.custom.encoding}/project.build.sourceEncoding
project.build.outputEncoding${project.custom.encoding}/project.build.outputEncoding
project.reporting.outputEncoding${project.custom.encoding}/project.reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand
this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family:
unix
Its a Mint distro, but with my own java installed as I required the 1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Up until m-c-p 2.5ish the default value for source was 1.3.
That was updated and newer versions of m-c-p use 1.5 as the default
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
Maven 3.1.0 will have m-c-p's default version pinned at least at 2.5, so
when that gets released you will have, by default, the source level at 1.5
(unless you downgrade your m-c-p plugin or override it to something lower
On 28 November 2012 15:14, Jasper Floor j.fl...@onehippo.com wrote:
I use mvn on the command line. I actually solved the problem by setting the
java version explicitly. I have jdk 1.6.0_33. I found some things on
various sites which suggested mvn always compiles in 1.3 mode. You might
not notice this in an IDE (if it is true) since your IDE is likely to fix
this for you. After all, you also have an explicit java version in your
IDE.
mvg,
Jasper
On Fri, Nov 16, 2012 at 4:42 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
What IDE are you using.
If your colleagues are using the same pom, you need to look at your IDE
setup.
For example, Eclipse will let you select any of the available compilers.
Ron
On 16/11/2012 8:21 AM, John Patrick wrote:
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-8/project.custom.encoding
project.custom.java.version1.6/project.custom.java.version
maven.compiler.source${project.custom.java.version}/maven.compiler.source
maven.compiler.target${project.custom.java.version}/maven.compiler.target
project.build.sourceEncoding${project.custom.encoding}/project.build.sourceEncoding
project.build.outputEncoding${project.custom.encoding}/project.build.outputEncoding
project.reporting.outputEncoding${project.custom.encoding}/project.reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand
this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is
a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family:
unix
Its a Mint distro, but with my own java installed as I required the
1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Good to know that Maven is now only 8 years behind. Better than 12, I
suppose!
Ron
On 28/11/2012 10:40 AM, Stephen Connolly wrote:
Up until m-c-p 2.5ish the default value for source was 1.3.
That was updated and newer versions of m-c-p use 1.5 as the default
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
Maven 3.1.0 will have m-c-p's default version pinned at least at 2.5, so
when that gets released you will have, by default, the source level at 1.5
(unless you downgrade your m-c-p plugin or override it to something lower
On 28 November 2012 15:14, Jasper Floor j.fl...@onehippo.com wrote:
I use mvn on the command line. I actually solved the problem by setting the
java version explicitly. I have jdk 1.6.0_33. I found some things on
various sites which suggested mvn always compiles in 1.3 mode. You might
not notice this in an IDE (if it is true) since your IDE is likely to fix
this for you. After all, you also have an explicit java version in your
IDE.
mvg,
Jasper
On Fri, Nov 16, 2012 at 4:42 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
What IDE are you using.
If your colleagues are using the same pom, you need to look at your IDE
setup.
For example, Eclipse will let you select any of the available compilers.
Ron
On 16/11/2012 8:21 AM, John Patrick wrote:
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-8/project.custom.encoding
project.custom.java.version1.6/project.custom.java.version
maven.compiler.source${project.custom.java.version}/maven.compiler.source
maven.compiler.target${project.custom.java.version}/maven.compiler.target
project.build.sourceEncoding${project.custom.encoding}/project.build.sourceEncoding
project.build.outputEncoding${project.custom.encoding}/project.build.outputEncoding
project.reporting.outputEncoding${project.custom.encoding}/project.reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand
this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is
a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family:
unix
Its a Mint distro, but with my own java installed as I required the
1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Hi Ron,
Good to know that Maven is now only 8 years behind.
I blame Apple.
-Curtis
On Wed, Nov 28, 2012 at 9:51 AM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Good to know that Maven is now only 8 years behind. Better than 12, I
suppose!
Ron
On 28/11/2012 10:40 AM, Stephen Connolly wrote:
Up until m-c-p 2.5ish the default value for source was 1.3.
That was updated and newer versions of m-c-p use 1.5 as the default
http://maven.apache.org/**plugins/maven-compiler-plugin/**
compile-mojo.html#sourcehttp://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
Maven 3.1.0 will have m-c-p's default version pinned at least at 2.5, so
when that gets released you will have, by default, the source level at 1.5
(unless you downgrade your m-c-p plugin or override it to something lower
On 28 November 2012 15:14, Jasper Floor j.fl...@onehippo.com wrote:
I use mvn on the command line. I actually solved the problem by setting
the
java version explicitly. I have jdk 1.6.0_33. I found some things on
various sites which suggested mvn always compiles in 1.3 mode. You might
not notice this in an IDE (if it is true) since your IDE is likely to fix
this for you. After all, you also have an explicit java version in your
IDE.
mvg,
Jasper
On Fri, Nov 16, 2012 at 4:42 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
What IDE are you using.
If your colleagues are using the same pom, you need to look at your IDE
setup.
For example, Eclipse will let you select any of the available compilers.
Ron
On 16/11/2012 8:21 AM, John Patrick wrote:
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.**plugins/groupId
artifactIdmaven-compiler-**plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-**8/project.custom.encoding
project.custom.java.version**1.6/project.custom.java.**
version
maven.compiler.source${**project.custom.java.version}/**
maven.compiler.source
maven.compiler.target${**project.custom.java.version}/**
maven.compiler.target
project.build.sourceEncoding**${project.custom.encoding}/**
project.build.sourceEncoding
project.build.outputEncoding**${project.custom.encoding}/**
project.build.outputEncoding
project.reporting.**outputEncoding${project.**
custom.encoding}/project.**reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand
this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is
a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family:
unix
Its a Mint distro, but with my own java installed as I required the
1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
--**--**
-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--**--**
-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
--**--**
-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
Re: Why does mvn compiile using java 1.3?
Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple.
Re: Why does mvn compiile using java 1.3?
Hi Mark, Now that Oracle are controlling Java on OSX we can no longer blame Apple Well, the new problem is that Java 7 only runs on Lion or later. So then I blame whoever made that decision. It has forced my projects to stay with Java 6 (which can for the most part be run in a Java 5 environment too using Retrotranslator) for the foreseeable future. I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. I agree, actually. That said, I think Java source/target versions are analogous to Maven plugin versions, in that it is safest to *always* lock them down, for all the same reasons. Regards, Curtis On Wed, Nov 28, 2012 at 12:36 PM, Mark Derricutt m...@talios.com wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple.
Re: Why does mvn compiile using java 1.3?
+1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
+1 even though that would trip up lots if users IMHO. Given that Jdk 6 will be deprecated in spring it might be a good move Ron Wheeler rwhee...@artifact-software.com wrote: +1 On 28/11/2012 1:36 PM, Mark Derricutt wrote: Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: Why does mvn compiile using java 1.3?
Do users often accidentally upgrade major releases of maven without care or thought? ….maybe I shouldn't ask that tho :) On 29/11/2012, at 9:47 AM, Manfred Moser manf...@mosabuam.com wrote: +1 even though that would trip up lots if users IMHO.
Re: Why does mvn compiile using java 1.3?
Hi, Which maven-compiler-plugin version are you using ? Does your colleague set JAVA_HOME env var on windows ? 2012/11/16 Jasper Floor j.fl...@onehippo.com: Hi, For some reason mvn is compiling using java 1.3. I do not understand this behavior. I have never seen this before and it doesn't do this on my colleagues machine with the same project. The big difference is he is a windows use and I am a linux user. Apache Maven 3.0.4 Maven home: /usr/share/maven Java version: 1.6.0_33, vendor: Sun Microsystems Inc. Java home: /opt/jdk/jdk1.6.0_33/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.0-29-generic, arch: amd64, family: unix Its a Mint distro, but with my own java installed as I required the 1.6 jdk. mvg, Jasper -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-8/project.custom.encoding
project.custom.java.version1.6/project.custom.java.version
maven.compiler.source${project.custom.java.version}/maven.compiler.source
maven.compiler.target${project.custom.java.version}/maven.compiler.target
project.build.sourceEncoding${project.custom.encoding}/project.build.sourceEncoding
project.build.outputEncoding${project.custom.encoding}/project.build.outputEncoding
project.reporting.outputEncoding${project.custom.encoding}/project.reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family: unix
Its a Mint distro, but with my own java installed as I required the 1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does mvn compiile using java 1.3?
What IDE are you using.
If your colleagues are using the same pom, you need to look at your IDE
setup.
For example, Eclipse will let you select any of the available compilers.
Ron
On 16/11/2012 8:21 AM, John Patrick wrote:
Jasper,
I also experience similar issues, it comes down to what version of
java you have installed, what version of the plugin you use and what
their respective defaults are. To avoid this I would explicitly state
version's of plugins and also a few other useful properties. I always
but at the least the following in every new project pom;
project ...
[...]
build
[...]
pluginManagement
[...]
plugins
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.5.1/version
/plugin
[...]
/plugins
[...]
/pluginManagement
[...]
/build
[...]
properties
[...]
project.custom.encodingUTF-8/project.custom.encoding
project.custom.java.version1.6/project.custom.java.version
maven.compiler.source${project.custom.java.version}/maven.compiler.source
maven.compiler.target${project.custom.java.version}/maven.compiler.target
project.build.sourceEncoding${project.custom.encoding}/project.build.sourceEncoding
project.build.outputEncoding${project.custom.encoding}/project.build.outputEncoding
project.reporting.outputEncoding${project.custom.encoding}/project.reporting.outputEncoding
[...]
/properties
/project
John
On 16 November 2012 09:50, Olivier Lamy ol...@apache.org wrote:
Hi,
Which maven-compiler-plugin version are you using ?
Does your colleague set JAVA_HOME env var on windows ?
2012/11/16 Jasper Floor j.fl...@onehippo.com:
Hi,
For some reason mvn is compiling using java 1.3. I do not understand this
behavior. I have never seen this before and it doesn't do this on my
colleagues machine with the same project. The big difference is he is a
windows use and I am a linux user.
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
Java home: /opt/jdk/jdk1.6.0_33/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-29-generic, arch: amd64, family: unix
Its a Mint distro, but with my own java installed as I required the 1.6
jdk.
mvg,
Jasper
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
