The versions upgrades of plugins are part of another topic, which are
indeed 3.7.0 candidates.
As said, the Java 8 update is not just about internal code improvements or
changes. Maven will expose new APIs/SPIs that contain Java 8 Functions, so
it must be seen as a requirement to implement the experimental
buildconsumer feature.
Robert
On Sat, 28 Sep 2019 14:23:16 +0200, Tibor Digana <tibordig...@apache.org>
wrote:
Hello guys,
For the user community these two issues are important:
https://issues.apache.org/jira/browse/MNG-6169
https://issues.apache.org/jira/browse/MNG-6548
The Tycho project is the user as well.
The J8 is internal code improvement/change => lower priority than the
user's priority => release order/priorities/dedicated time spent in
development.
Have a nice day.
Cheers
Tibor17
On Sat, Sep 28, 2019 at 2:08 PM Gary Gregory <garydgreg...@gmail.com>
wrote:
I would say that fixing the Tycho issue comes first.
Gary
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
