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 also in the near future, as the JDK compiler only supports a limited number of previous versions. Is 1.5 even still supported in JDK 8? But I guess the question is if we want to put in a fixed default value for those parameters anyway. Instead, we could just detect the actual language version of the JDK used for the build / in the toolchain.... Using source/target versions different than the JDK language version is fishy anyway - which will change in JDK 9, but there it's a new parameter (-platform or something? I don't remember right now). My 0,02€... ;-) Andreas Am Freitag, 6. November 2015 schrieb Michael Osipov : > 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: >> >> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html >> ). >> > > Clearly -1 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
