Re: Updating the default versions for maven-compiler-plugin

On Fri, Nov 6, 2015 at 1:56 PM, Attila-Mihály Balázs wrote: > Given that we're almost in 2015, what do people think about updating the > default source / target for maven-compiler-plugin to 1.8? (And also on the > site: >

Re: Updating the default versions for maven-compiler-plugin

Or, with latest tools: - Update poms to set langlevel explicitly, if not set - Pay attention to maven and plugin reqs re JVM - Use toolchain Etc On Sat, Nov 7, 2015, 10:22 Tamás Cservenák wrote: > How bout starting to fail if lang level is not explicitly set and _remove_ >

Re: Updating the default versions for maven-compiler-plugin

Am 07.11.2015 10:22 schrieb "Tamás Cservenák" : > > How bout starting to fail if lang level is not explicitly set and _remove_ > defaults? > Hello, letting Maven fail if you do not configure language levels leads to bad beginner's experience. Using the level of the invoking

Re: Updating the default versions for maven-compiler-plugin

How bout starting to fail if lang level is not explicitly set and _remove_ defaults? Am sick of discussions in present about something to happen in future future (when thing is released) to fit something EOLd in past :) Ie. For the stuck people: Use current/older versions of tooling, if you are

Re: Updating the default versions for maven-compiler-plugin

Am 07.11.2015 10:22 schrieb "Tamás Cservenák" : > Ie. For the stuck people: Use current/older versions of tooling, if you are > stuck with old JVM: just accept you are stuck with tooling too then... +1 for that.

Re: Updating the default versions for maven-compiler-plugin

Hello Jochen, could not a new major update of the compiler plugin change the default? My guess is we would not break much anyway as the majority of projects already needs to manage source and target explicitly. Regards Mirko -- Sent from my mobile Am 07.11.2015 16:15 schrieb "Jochen Wiedmann"

Re: Updating the default versions for maven-compiler-plugin

Just to clarify, it's Oracle's JDK 1.7 that is EOL. IBM still supports their Java 6 and 7 level JDKs. Moving to a 1.7 default is still ok I think. However, if we think that most people will still need to configure 1.8 (or 1.9 soon) I don't see the point of doing this as it does introduce a level

Re: Updating the default versions for maven-compiler-plugin

since it's a good practice to define java version explicitely, to avoid any misunderstanding, I'm not sure changing default value is really something important: what's important it to know that it costs only 2 properties (and eventually merge them) notice that if we change default value, I

Re: Updating the default versions for maven-compiler-plugin

I think it's actually a good idea to do something about that. Users who don't specify a source/target version would fall on their bottoms with a change to 1.7 as default as well. So why using 1.7 as a default, which is EOL (or at least nearly) anyway? Keeping the default on 1.5 might bite users

Re: Updating the default versions for maven-compiler-plugin

+1 for 1.7. Gary On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs wrote: > Hello, > > Given that we're almost in 2015, what do people think about updating the > default source / target for maven-compiler-plugin to 1.8? (And also on the > site: >

Re: Updating the default versions for maven-compiler-plugin

Am 2015-11-06 um 13:56 schrieb Attila-Mihály Balázs: Hello, Given that we're almost in 2015, what do people think about updating the default source / target for maven-compiler-plugin to 1.8? (And also on the site:

Re: Updating the default versions for maven-compiler-plugin

-1. We might want to move to 1.7, but many people are still not in a position to use 1.8. On Fri, Nov 6, 2015 at 7:56 AM, Attila-Mihály Balázs wrote: > Hello, > > Given that we're almost in 2015, what do people think about updating the > default source / target for

Re: Updating the default versions for maven-compiler-plugin

2015-11-06 18:42 GMT+01:00 Uwe Barthel : > -1 > > Many commercial projects still require Java 1.6. > The question asked by Attila is if the *default *values for the source/target parameters in the compiler-plugin could use some attention (and I think it should, as the

Re: Updating the default versions for maven-compiler-plugin

-1 Many commercial projects still require Java 1.6. mit freundlichen Grüßen -- Uwe Barthel On November 6, 2015 1:57:04 PM Attila-Mihály Balázs wrote: Hello, Given that we're almost in 2015, what do people think about updating the default source

Updating the default versions for maven-compiler-plugin

Hello, Given that we're almost in 2015, what do people think about updating the default source / target for maven-compiler-plugin to 1.8? (And also on the site: https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html). If there is interest, I'm

Re: Updating the default versions for maven-compiler-plugin

+1 to at least 1.7 However, since 1.7 is EOL, I do think it also makes sense to default to 1.8, since it's the earliest version still getting public security updates, and therefore it's reasonable that most people should be using that version if possible. It's a trivial matter to configure the

Re: Updating the default versions for maven-compiler-plugin

Hi, -1 to 1.8 +1 to 1.7 so we already jump over 1.6 as default which is absolutely ok... Kind regards Karl Heinz Marbaise On 11/6/15 10:17 PM, Christopher wrote: +1 to at least 1.7 However, since 1.7 is EOL, I do think it also makes sense to default to 1.8, since it's the earliest version