Hi,
On 03.10.19 14:36, Elliotte Rusty Harold wrote:
Theoretically that would work. In practice though, every project I've
seen convert to Java 8 rapidly starts adding lambdas that make the
code more obfuscated for no good reason and soon introduces hard
dependencies on Java 8, intentionally or otherwise. At a bare minimum,
a CI environment that runs Java 7 is required.
If people don't understand how to use Java 8 code like Streams, lambdas,
functions etc... I think they should learn how to it the right way...I
admit that lambdas is a hard nut to crack ...
Apart from that Pual has gieven the hint to use toolchains as already
done by Stephen Connolly.. which supports exactly what is needed ..
Run your Build (Maven) on JDK 8 where as your code will run on Java 7
(build/test)..
So I don't see here a real issue to lift the minimum for Maven to JDK
8... (Furthermore the request of Robert Scholte)..
Kind regards
Karl Heinz Marbaise
On Thu, Oct 3, 2019 at 8:25 AM Paul Hammant <p...@hammant.org> wrote:
Would jdk 8 for maven itself and a target of 7 for the compiler (etc) for
maven-using projects be ok?
On Thu, Oct 3, 2019 at 1:15 PM Elliotte Rusty Harold <elh...@ibiblio.org>
wrote:
Strong -1 on Java 8 as the minimum version. Google Cloud Platform has
lots of products and customers that still require Java 7. If Maven
requires Java 8, we'd have to stick to the latest of whichever release
does support Java 7 for at least a year and I'm guessing longer.
On Sat, Sep 28, 2019 at 8:04 AM Robert Scholte <rfscho...@apache.org>
wrote:
Hi,
TLDR; introduce maven.experimental.buildconsumer and push Java
requirement
to Java 8
now that Maven 3.6.2 is out for a couple of weeks, it seems like we
didn't
face real regressions.
The only one might be tricky is the issue related to Tycho.
However, I think we're ready to push Maven to the next level.
For those actively reading this list, they should recognize the need for
splitting up the pom as it is on the local system versus the pom being
uploaded. Once we truly control this mechanism we can think of
improvements on model 5.0.0 and new fileformats.
I've created and implemented MNG-6656[1]. It also contains a zip with an
example (original, patched, README) to understand what's happening.
In order to make this successful, we need IDEs and CI Servers to
understand and support these changes. The likely need to implement one of
the interfaces[2].
The new interface uses Java8 Functions (and especially SAXEventFactory is
way easier to read+maintain with Java 8). I've tried to keep Maven Java 7
compatible, but that was too hard to do.
So I'd like to use this opportunity to move Maven forward and start
requiring Java 8.
There are some other improvements I'd like to add (those messages will
follow), so this will imply that it will take some time before we do a
new
release.
WDTY,
Robert
[1] https://issues.apache.org/jira/browse/MNG-6656
[2] https://github.com/apache/maven/compare/MNG-6656?expand=1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
