Hi Tibor,
On 6/18/15 1:42 PM, Tibor Digana wrote:
It's truth that we upgrade the JDK version for Maven distrib in 3.3/jdk7 and
3.2/jdk6 and not the compiler.
From the users perspective I would also suppose the compiler changed.
On the other side migrating all plugins takes time. Due to mo
kes some time to support Maven 3.0 API
in maven-compiler-plugin and maybe this topic would be relevant when this
would happen.
--
View this message in context:
http://maven.40175.n5.nabble.com/Default-Maven-Compiler-Version-tp5837828p5837866.html
Sent from the Maven Developers mailing list ar
Hi Jason,
Jason Pyeron wrote:
>> -Original Message-
>> From: Manfred Moser [mailto:manf...@mosabuam.com]
>> Sent: Thursday, June 18, 2015 12:21 AM
>> To: dev@maven.apache.org
>> Subject: Re: Default Maven Compiler Version
>>
>> Yes... a corporat
> -Original Message-
> From: Manfred Moser [mailto:manf...@mosabuam.com]
> Sent: Thursday, June 18, 2015 12:21 AM
> To: dev@maven.apache.org
> Subject: Re: Default Maven Compiler Version
>
> Yes... a corporate or some other higher level pom is
I think some detail w
now on. Feel free to update your address book.
>
>> -Original Message-
>> From: Mangold, Kevin C. [mailto:kevin.mang...@nist.gov]
>> Sent: Wednesday, June 17, 2015 12:55
>> To: dev@maven.apache.org
>> Subject: Default Maven Compiler Version
>>
>&
from
now on. Feel free to update your address book.
> -Original Message-
> From: Mangold, Kevin C. [mailto:kevin.mang...@nist.gov]
> Sent: Wednesday, June 17, 2015 12:55
> To: dev@maven.apache.org
> Subject: Default Maven Compiler Version
>
> Why does the maven
Why does the maven compiler plugin STILL target 1.5 by default and not the
JDK's current version? This seems completely backwards. We use CI tools to test
against different JDK versions and architectures and it is a massive pain to
implement all these workarounds to have the compiler target each
