+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 <[email protected]> wrote:
> +1 for 1.7.
>
> Gary
>
> On Fri, Nov 6, 2015 at 4:56 AM, Attila-Mihály Balázs <[email protected]>
> 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: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> E-Mail: [email protected] | [email protected]
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to