You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Attila-Mihály Balázs <di...@gmail.com> on 2015/11/06 13:56:48 UTC
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 happy to submit a patch!
Cheers,
Attila Balazs (Grey Panther)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Tamás Cservenák <ta...@cservenak.net>.
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 <ta...@cservenak.net> wrote:
> 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 stuck with old JVM: just accept you are stuck with tooling too then...
>
> On Sat, Nov 7, 2015, 08:56 Hervé BOUTEMY <he...@free.fr> wrote:
>
>> 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 want to see a table in the
>> plugin
>> documentation showing which version of the plugin has which default java
>> version
>>
>> because the immense benefit I see currently is that it's always the same
>>
>> Regards,
>>
>> Hervé
>>
>> Le samedi 7 novembre 2015 08:28:51 Anders Hammar a écrit :
>> > 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 of incompatibility for those
>> > still using Java 6 or earlier. The default could then stay at 1.5.
>> >
>> > /Anders
>> >
>> > On Fri, Nov 6, 2015 at 10:30 PM, Karl Heinz Marbaise <khmarbaise@gmx.de
>> >
>> >
>> > wrote:
>> > > 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 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
>> > >> plugin for an earlier version if the software needs to be built to
>> > >> support a system that's not updated. These systems can (and probably
>> > >> already are) using older versions of this plugin anyway, so changing
>> > >> the default in newer versions isn't likely to affect them.
>> > >>
>> > >> But, at the very least, 1.7 is a big +1, incremental improvement to
>> the
>> > >> default.
>> > >>
>> > >> --
>> > >> Christopher L Tubbs II
>> > >> http://gravatar.com/ctubbsii
>> > >>
>> > >>
>> > >> On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <garydgregory@gmail.com
>> >
>> > >>
>> > >> wrote:
>> > >>> +1 for 1.7.
>> > >>>
>> > >>> Gary
>> > >>>
>> > >>> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <
>> dify.ltd@gmail.com
>> > >>>
>> > >>> 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:
>> > >>>>
>> > >>>>
>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-com
>> > >>>> piler-source-and-target.html ).
>> > >>>>
>> > >>>> If there is interest, I'm happy to submit a patch!
>> > >>>>
>> > >>>> Cheers,
>> > >>>> Attila Balazs (Grey Panther)
>> > >>>>
>> > >>>>
>> ---------------------------------------------------------------------
>> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
>> > >>>
>> > >>> --
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Re: Updating the default versions for maven-compiler-plugin
Posted by Mirko Friedenhagen <mf...@gmail.com>.
Am 07.11.2015 10:22 schrieb "Tamás Cservenák" <ta...@cservenak.net>:
> 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
Posted by Mirko Friedenhagen <mf...@gmail.com>.
Am 07.11.2015 10:22 schrieb "Tamás Cservenák" <ta...@cservenak.net>:
>
> 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 JDK however, seems the most natural fit to
me. I am supporting about 200 developers concerning Maven questions and
before we enforced the level in our department pom, this was one of the
more frequent questions (years back).
The disadvantage would be, that environment would play a bigger role.
Re: Updating the default versions for maven-compiler-plugin
Posted by Tamás Cservenák <ta...@cservenak.net>.
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
stuck with old JVM: just accept you are stuck with tooling too then...
On Sat, Nov 7, 2015, 08:56 Hervé BOUTEMY <he...@free.fr> wrote:
> 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 want to see a table in the plugin
> documentation showing which version of the plugin has which default java
> version
>
> because the immense benefit I see currently is that it's always the same
>
> Regards,
>
> Hervé
>
> Le samedi 7 novembre 2015 08:28:51 Anders Hammar a écrit :
> > 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 of incompatibility for those
> > still using Java 6 or earlier. The default could then stay at 1.5.
> >
> > /Anders
> >
> > On Fri, Nov 6, 2015 at 10:30 PM, Karl Heinz Marbaise <kh...@gmx.de>
> >
> > wrote:
> > > 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 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
> > >> plugin for an earlier version if the software needs to be built to
> > >> support a system that's not updated. These systems can (and probably
> > >> already are) using older versions of this plugin anyway, so changing
> > >> the default in newer versions isn't likely to affect them.
> > >>
> > >> But, at the very least, 1.7 is a big +1, incremental improvement to
> the
> > >> default.
> > >>
> > >> --
> > >> Christopher L Tubbs II
> > >> http://gravatar.com/ctubbsii
> > >>
> > >>
> > >> On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <ga...@gmail.com>
> > >>
> > >> wrote:
> > >>> +1 for 1.7.
> > >>>
> > >>> Gary
> > >>>
> > >>> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <
> dify.ltd@gmail.com
> > >>>
> > >>> 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:
> > >>>>
> > >>>>
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-com
> > >>>> piler-source-and-target.html ).
> > >>>>
> > >>>> If there is interest, I'm happy to submit a patch!
> > >>>>
> > >>>> Cheers,
> > >>>> Attila Balazs (Grey Panther)
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>
> > >>> --
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Updating the default versions for maven-compiler-plugin
Posted by Hervé BOUTEMY <he...@free.fr>.
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 want to see a table in the plugin
documentation showing which version of the plugin has which default java
version
because the immense benefit I see currently is that it's always the same
Regards,
Hervé
Le samedi 7 novembre 2015 08:28:51 Anders Hammar a écrit :
> 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 of incompatibility for those
> still using Java 6 or earlier. The default could then stay at 1.5.
>
> /Anders
>
> On Fri, Nov 6, 2015 at 10:30 PM, Karl Heinz Marbaise <kh...@gmx.de>
>
> wrote:
> > 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 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
> >> plugin for an earlier version if the software needs to be built to
> >> support a system that's not updated. These systems can (and probably
> >> already are) using older versions of this plugin anyway, so changing
> >> the default in newer versions isn't likely to affect them.
> >>
> >> But, at the very least, 1.7 is a big +1, incremental improvement to the
> >> default.
> >>
> >> --
> >> Christopher L Tubbs II
> >> http://gravatar.com/ctubbsii
> >>
> >>
> >> On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <ga...@gmail.com>
> >>
> >> wrote:
> >>> +1 for 1.7.
> >>>
> >>> Gary
> >>>
> >>> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <dify.ltd@gmail.com
> >>>
> >>> 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:
> >>>>
> >>>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-com
> >>>> piler-source-and-target.html ).
> >>>>
> >>>> If there is interest, I'm happy to submit a patch!
> >>>>
> >>>> Cheers,
> >>>> Attila Balazs (Grey Panther)
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>> --
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Anders Hammar <an...@hammar.net>.
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 of incompatibility for those
still using Java 6 or earlier. The default could then stay at 1.5.
/Anders
On Fri, Nov 6, 2015 at 10:30 PM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> 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 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
>> plugin for an earlier version if the software needs to be built to
>> support a system that's not updated. These systems can (and probably
>> already are) using older versions of this plugin anyway, so changing
>> the default in newer versions isn't likely to affect them.
>>
>> But, at the very least, 1.7 is a big +1, incremental improvement to the
>> default.
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>>
>> On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>
>>> +1 for 1.7.
>>>
>>> Gary
>>>
>>> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <dify.ltd@gmail.com
>>> >
>>> 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:
>>>>
>>>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
>>>> ).
>>>>
>>>> If there is interest, I'm happy to submit a patch!
>>>>
>>>> Cheers,
>>>> Attila Balazs (Grey Panther)
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Updating the default versions for maven-compiler-plugin
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
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 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
> plugin for an earlier version if the software needs to be built to
> support a system that's not updated. These systems can (and probably
> already are) using older versions of this plugin anyway, so changing
> the default in newer versions isn't likely to affect them.
>
> But, at the very least, 1.7 is a big +1, incremental improvement to the default.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <ga...@gmail.com> wrote:
>> +1 for 1.7.
>>
>> Gary
>>
>> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <di...@gmail.com>
>> 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:
>>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
>>> ).
>>>
>>> If there is interest, I'm happy to submit a patch!
>>>
>>> Cheers,
>>> Attila Balazs (Grey Panther)
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Christopher <ct...@apache.org>.
+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
plugin for an earlier version if the software needs to be built to
support a system that's not updated. These systems can (and probably
already are) using older versions of this plugin anyway, so changing
the default in newer versions isn't likely to affect them.
But, at the very least, 1.7 is a big +1, incremental improvement to the default.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Fri, Nov 6, 2015 at 2:04 PM, Gary Gregory <ga...@gmail.com> wrote:
> +1 for 1.7.
>
> Gary
>
> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <di...@gmail.com>
> 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:
>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
>> ).
>>
>> If there is interest, I'm happy to submit a patch!
>>
>> Cheers,
>> Attila Balazs (Grey Panther)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Gary Gregory <ga...@gmail.com>.
+1 for 1.7.
Gary
On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <di...@gmail.com>
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:
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
> ).
>
> If there is interest, I'm happy to submit a patch!
>
> Cheers,
> Attila Balazs (Grey Panther)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Updating the default versions for maven-compiler-plugin
Posted by Andreas Gudian <an...@gmail.com>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Updating the default versions for maven-compiler-plugin
Posted by Michael Osipov <mi...@apache.org>.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Andreas Gudian <an...@gmail.com>.
2015-11-06 18:42 GMT+01:00 Uwe Barthel <ba...@x-reizend.de>:
> -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 default value 1.5 is just useless and
constantly confuses people that are new to maven).
This is not about limiting the possible JDK versions that can be used in
toolchains or used in the build, or to limit the possible values of those
parameters... :-)
>
> mit freundlichen Grüßen
> --
> Uwe Barthel <ba...@x-reizend.de>
>
>
>
>
> On November 6, 2015 1:57:04 PM Attila-Mihály Balázs <di...@gmail.com>
> 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:
>>
>> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
>> ).
>>
>> If there is interest, I'm happy to submit a patch!
>>
>> Cheers,
>> Attila Balazs (Grey Panther)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Updating the default versions for maven-compiler-plugin
Posted by Uwe Barthel <ba...@x-reizend.de>.
-1
Many commercial projects still require Java 1.6.
mit freundlichen Grüßen
--
Uwe Barthel <ba...@x-reizend.de>
On November 6, 2015 1:57:04 PM Attila-Mihály Balázs <di...@gmail.com> 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:
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html).
>
> If there is interest, I'm happy to submit a patch!
>
> Cheers,
> Attila Balazs (Grey Panther)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Benson Margulies <bi...@gmail.com>.
-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 <di...@gmail.com> 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:
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html).
>
> If there is interest, I'm happy to submit a patch!
>
> Cheers,
> Attila Balazs (Grey Panther)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Updating the default versions for maven-compiler-plugin
Posted by Mirko Friedenhagen <mf...@gmail.com>.
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" <jo...@gmail.com>:
> On Fri, Nov 6, 2015 at 1:56 PM, Attila-Mihály Balázs <di...@gmail.com>
> 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:
> >
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
> ).
> >
> > If there is interest, I'm happy to submit a patch!
>
> Whatever year we now have: What you propose is a *incompatible
> change*, and we don't do that. Or, to quite Linus Torvalds:
>
> WE DO NOT BREAK USERSPACE!
>
> Jochen
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Updating the default versions for maven-compiler-plugin
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Fri, Nov 6, 2015 at 1:56 PM, Attila-Mihály Balázs <di...@gmail.com> 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:
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html).
>
> If there is interest, I'm happy to submit a patch!
Whatever year we now have: What you propose is a *incompatible
change*, and we don't do that. Or, to quite Linus Torvalds:
WE DO NOT BREAK USERSPACE!
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org