Then why you are setting target to 1.8 without the code?
It does not make sense to set it without adapting the code.
You know what it looks like? Many people will hate me when I say this in
public.
It looks like a lobby. And there can be anything in background,
organizations, money flow, anything. But we do not do it for money. We are
doing it for the top notch quality and satisfied user.
We know the one of our user created a commit in a plugin where the code was
migrated automatically.
It helps but still you have to remove the "modernizer" annotations:
<plugin>
<groupId>org.gaul</groupId>
<artifactId>modernizer-maven-plugin</artifactId>
<version>1.8.0</version>
<executions>
<execution>
<id>modernizer</id>
<phase>verify</phase>
<goals>
<goal>modernizer</goal>
</goals>
</execution>
</executions>
<configuration>
<javaVersion>1.8</javaVersion>
</configuration>
</plugin>
<dependency>
<groupId>org.gaul</groupId>
<artifactId>modernizer-maven-annotations</artifactId>
<version>1.8.0</version>
</dependency>
On Mon, Sep 30, 2019 at 9:04 PM Enrico Olivelli <eolive...@gmail.com> wrote:
> Tibor
>
> Il lun 30 set 2019, 20:30 Tibor Digana <tibordig...@apache.org> ha
> scritto:
>
> > Robert, you'r really right, there is only 3.7.0-candidate
> > <
> >
> https://issues.apache.org/jira/issues/?jql=project+%3D+MNG+AND+fixVersion+%3D+3.7.0-candidate
> > >
> > version in Jira, see
> >
> >
> https://issues.apache.org/jira/projects/MNG?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
> > So this means MNG-6169 is in this discussion as well as it is 3.7.0.
> > As well as many other issues in the list including the MNG-6548 and
> > MNG-6656 too.
> >
> > Internal code regarding J8 means that you have to rewrite the code to J8.
> > It can be done automatically but that's another topic.
> >
>
> You know that compiling for j8 does not require to use lamdas or whatever,
> don't have to change your code,but only set target=8
>
> Enrico
>
>
> As far as I know the Maven developers they do not always have private spare
> > time to do this job and therefore it is better to write a list of
> > priorities and find the human resources for these issue. I know how
> > difficult it is. This is the main problem.
> > I am not against J8. I only say that we have to deliver important things
> > from the user perspective first and then those less important whishes
> which
> > is called "priorities", nothing special.
> >
> > Cheers
> > Tibor17
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Sep 30, 2019 at 8:14 PM Robert Scholte <rfscho...@apache.org>
> > wrote:
> >
> > > 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
> > >
> > >
> >
>
