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
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 most of them
still depend on Maven API 2.2.1. It takes some
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 corporate or some other higher level pom is
I think some
-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 was missed in the OP's
I wonder if this would be a good candidate for a corporate POM that deals with
this kind of configuration?
Sander Verhagen
[ san...@sanderverhagen.net ]
NOTICE: my e-mail address has changed. You may still e-mail me at
verha...@sander.com but you will see me using san...@sanderverhagen.net
Yes... a corporate or some other higher level pom is typically how you
configure this across lots of projects. But even if you dont ... its two lines
of config on the compiler plugin.
Manfred
Sander Verhagen wrote on 17.06.2015 15:16:
I wonder if this would be a good candidate for a
