You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Gary Gregory <ga...@gmail.com> on 2019/09/28 12:08:23 UTC
Re: [DISCUSS] Maven 3.7.0
I would say that fixing the Tycho issue comes first.
Gary
On Sat, Sep 28, 2019 at 8:04 AM Robert Scholte <rf...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Maven 3.7.0
Posted by Stephen Connolly <st...@gmail.com>.
+1 on Java 8 requirement for Maven runtime (note this still lets you
compile with Java 7 if you are prepared to use toolchains... the complexity
of using toolchains is an argument for improving/revisiting toolchains)
+1 on getting the place for filtering the pom.xml to produce the consumer
pom.xml, but I would go one step further. Enable it by default, but allow
opt-out. Also I would suggest to pick up a feature-flagging technique to
allow a project to opt out just by declaring the `maven.experimental.___`
property in the `pom.xml`. We should be clear that such flags will stop
working once the feature is confirmed solid, but NOBODY will turn the
experimental flag on, especially if it is a system property only flag...
and if we do not have confidence that the feature will work with both the
shade plugin and the gpg plugin then - quite frankly - the feature is not
ready
On Tue, 1 Oct 2019 at 18:31, Robert Scholte <rf...@apache.org> wrote:
> https://github.com/apache/maven/pull/286
>
> On Tue, 01 Oct 2019 13:49:25 +0200, Enrico Olivelli <eo...@gmail.com>
>
> wrote:
>
> > Robert,
> > Can you create a PR?
> >
> > Enrico
> >
> > Il mar 1 ott 2019, 07:19 Sylwester Lachiewicz <sl...@gmail.com> ha
> > scritto:
> >
> >> +1 for Java 8 - let's kill 7 faster ;-))
> >>
> >> Sylwester
> >>
> >> wt., 1 paź 2019, 02:41 użytkownik Olivier Lamy <ol...@apache.org>
> >> napisał:
> >>
> >> > +1 for Java 8
> >> > it's time now and we will probably having more contributions as
> >> young/cool
> >> > kids prefer using modern tools
> >> > Yup the world is not only made with Old Grumpy grand dad working only
> >> with
> >> > Java 5 :P )
> >> >
> >> > On Tue, 1 Oct 2019 at 04:14, Robert Scholte <rf...@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 <
> >> tibordigana@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
> >> <garydgregory@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 <
> >> rfscholte@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-unsubscribe@maven.apache.org
> >> > > >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> > > >> >
> >> > > >> >
> >> > >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> > > For additional commands, e-mail: dev-help@maven.apache.org
> >> > >
> >> > >
> >> >
> >> > --
> >> > Olivier Lamy
> >> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Maven 3.7.0
Posted by Robert Scholte <rf...@apache.org>.
https://github.com/apache/maven/pull/286
On Tue, 01 Oct 2019 13:49:25 +0200, Enrico Olivelli <eo...@gmail.com>
wrote:
> Robert,
> Can you create a PR?
>
> Enrico
>
> Il mar 1 ott 2019, 07:19 Sylwester Lachiewicz <sl...@gmail.com> ha
> scritto:
>
>> +1 for Java 8 - let's kill 7 faster ;-))
>>
>> Sylwester
>>
>> wt., 1 paź 2019, 02:41 użytkownik Olivier Lamy <ol...@apache.org>
>> napisał:
>>
>> > +1 for Java 8
>> > it's time now and we will probably having more contributions as
>> young/cool
>> > kids prefer using modern tools
>> > Yup the world is not only made with Old Grumpy grand dad working only
>> with
>> > Java 5 :P )
>> >
>> > On Tue, 1 Oct 2019 at 04:14, Robert Scholte <rf...@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 <
>> tibordigana@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
>> <garydgregory@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 <
>> rfscholte@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-unsubscribe@maven.apache.org
>> > > >> > For additional commands, e-mail: dev-help@maven.apache.org
>> > > >> >
>> > > >> >
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>> > >
>> > >
>> >
>> > --
>> > Olivier Lamy
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Maven 3.7.0
Posted by Enrico Olivelli <eo...@gmail.com>.
Robert,
Can you create a PR?
Enrico
Il mar 1 ott 2019, 07:19 Sylwester Lachiewicz <sl...@gmail.com> ha
scritto:
> +1 for Java 8 - let's kill 7 faster ;-))
>
> Sylwester
>
> wt., 1 paź 2019, 02:41 użytkownik Olivier Lamy <ol...@apache.org> napisał:
>
> > +1 for Java 8
> > it's time now and we will probably having more contributions as
> young/cool
> > kids prefer using modern tools
> > Yup the world is not only made with Old Grumpy grand dad working only
> with
> > Java 5 :P )
> >
> > On Tue, 1 Oct 2019 at 04:14, Robert Scholte <rf...@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 <
> tibordigana@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 <garydgregory@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 <
> rfscholte@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-unsubscribe@maven.apache.org
> > > >> > For additional commands, e-mail: dev-help@maven.apache.org
> > > >> >
> > > >> >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>
Re: [DISCUSS] Maven 3.7.0
Posted by Sylwester Lachiewicz <sl...@gmail.com>.
+1 for Java 8 - let's kill 7 faster ;-))
Sylwester
wt., 1 paź 2019, 02:41 użytkownik Olivier Lamy <ol...@apache.org> napisał:
> +1 for Java 8
> it's time now and we will probably having more contributions as young/cool
> kids prefer using modern tools
> Yup the world is not only made with Old Grumpy grand dad working only with
> Java 5 :P )
>
> On Tue, 1 Oct 2019 at 04:14, Robert Scholte <rf...@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 <tibordigana@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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
> > >> > For additional commands, e-mail: dev-help@maven.apache.org
> > >> >
> > >> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: [DISCUSS] Maven 3.7.0
Posted by Olivier Lamy <ol...@apache.org>.
+1 for Java 8
it's time now and we will probably having more contributions as young/cool
kids prefer using modern tools
Yup the world is not only made with Old Grumpy grand dad working only with
Java 5 :P )
On Tue, 1 Oct 2019 at 04:14, Robert Scholte <rf...@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 <ti...@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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >
> >> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] Maven 3.7.0
Posted by Robert Scholte <rf...@apache.org>.
> Then why you are setting target to 1.8 without the code?
As said: there *are* Java 8 specific code changes:
https://github.com/apache/maven/compare/MNG-6656?expand=1#diff-becf9d362b95e48f9ca0f2ab76ca9f8fR54
(and every other method in this class)
https://github.com/apache/maven/compare/MNG-6656?expand=1#diff-97970a066f1696b603d96aad18b0f016R30
https://github.com/apache/maven/compare/MNG-6656?expand=1#diff-42c7d5b776fd974f21918f6d7ff2ab24R82-R94
https://github.com/apache/maven/compare/MNG-6656?expand=1#diff-3af5d63445648bbb61fddf8863a53888R36-R62
Even though all these classes live in the new maven-xml module, if you try
to only compile this module with Java 8, and let maven-core depend on it
with an @Inject for the BuildPomXMLFilterFactory, Maven simple won't start
on Java 7 anymore. Trying to keep Maven Java 7 compatible including these
files will introduce unmaintainable and unreadable code.
Hence why I started this [discuss] topic.
Up until now most people see this as the right opportunity to require Java
8.
Robert
On Mon, 30 Sep 2019 21:15:47 +0200, Tibor Digana <ti...@apache.org>
wrote:
> 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 <eo...@gmail.com>
> wrote:
>
>> Tibor
>>
>> Il lun 30 set 2019, 20:30 Tibor Digana <ti...@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 <rf...@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 <
>> tibordigana@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
>> <garydgregory@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 <
>> rfscholte@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-unsubscribe@maven.apache.org
>> > > >> > For additional commands, e-mail: dev-help@maven.apache.org
>> > > >> >
>> > > >> >
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>> > >
>> > >
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Maven 3.7.0
Posted by Tibor Digana <ti...@apache.org>.
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 <eo...@gmail.com> wrote:
> Tibor
>
> Il lun 30 set 2019, 20:30 Tibor Digana <ti...@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 <rf...@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 <
> tibordigana@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 <garydgregory@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 <
> rfscholte@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-unsubscribe@maven.apache.org
> > > >> > For additional commands, e-mail: dev-help@maven.apache.org
> > > >> >
> > > >> >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] Maven 3.7.0
Posted by Enrico Olivelli <eo...@gmail.com>.
Tibor
Il lun 30 set 2019, 20:30 Tibor Digana <ti...@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 <rf...@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 <tibordigana@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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
> > >> > For additional commands, e-mail: dev-help@maven.apache.org
> > >> >
> > >> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: [DISCUSS] Maven 3.7.0
Posted by Tibor Digana <ti...@apache.org>.
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.
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 <rf...@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 <ti...@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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >
> >> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSS] Maven 3.7.0
Posted by Robert Scholte <rf...@apache.org>.
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 <ti...@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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSS] Maven 3.7.0
Posted by Tibor Digana <ti...@apache.org>.
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 <ga...@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 <rf...@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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>