Robert, >>And if we're focusing on the latter, shouldn't the twitter question be
Good remark! I am not against such question on Twitter but I would be interested in one more in comparison to Gradle. *What the Maven should improve to make Maven more attractive against Gradle?* Because I don't think that question about using Java 8 in Maven beats more that the question with Gradle. I know the PMC's answer to Gradle and I am totally with you! I don't use Gradle and never will but the users always like to try some new. On Sun, Sep 10, 2017 at 8:54 PM, Robert Scholte <[email protected]> wrote: > On Sun, 10 Sep 2017 20:21:11 +0200, Stephen Connolly < > [email protected]> wrote: > > On Sun 10 Sep 2017 at 19:04, Tibor Digana <[email protected]> wrote: >> >> Hi All, >>> >>> Are we facing new API regarding networking and security useful in Java 8? >>> >>> When I first saw these options I asked myself what benefit would have the >>> User and Jenkins from Java 8. >>> And second question was whether we would be so flexible to rewrite the >>> code >>> and use Lambda fully anywhere in the code. >>> >> >> >> There is the social aspect. If you are a potential new contributor to >> Maven >> and you look at our heavy Java 1.3 convention codebase (ok, I'm being a >> demagogue, it's had a bit updated to 5.0) are you going to be encouraged >> to >> step forward? >> >> How can you make small improvements and demonstrate you are a safe pair of >> hands to gain the commit bit? >> >> Now if we have the opertunity to make lots of tidy up and you can show you >> are a safe pair of hands, retaining binary compatibility with older >> plugins, making the code more readable, finding file handle leaks, etc... >> well now you have a welcome path to demonstrate your skills.... while >> gaining familiarity with the codebase so that when we turn around to start >> on Maven 5.0.x you can join in the fun. >> >> Now that is not a technical argument, but we are a community first... so >> maybe the technical arguments are not so right to push! >> >> > bq. but we are a community first > > What's the definition of community: the large user group or the few we're > hoping to find who can help working on Maven? > And if we're focusing on the latter, shouldn't the twitter question be: > > I want to become a Maven developer > [] right now! > [] only if Maven requires Java 8 ( so I can use lambda's, etc.) > [] never, let others do the job > [] other... > > > >>> So I kept Java 7 for Maven 3.6 which does not mean that Maven 4 or 5 >>> would >>> not change this. >>> Regarding security everybody can use JDK 8 with old Maven but different >>> story would be enhancements in Networking API. >>> >> >> >> Yes, but shouldn't we stop them using the known bad Java 7 if they want >> the >> latest maven? If they don't care about security, then they'll likely not >> upgrade Maven either... so why worry about keeping Java 7 for them... when >> they do get around to upgrading they'll do it all in bulk anyway... so >> asking them to go Java 8 at that time will not be an issue... plus we do >> them a favour by being another reason to upgrade ;-) >> >> >> >>> >>> On Sun, Sep 10, 2017 at 6:33 PM, Robert Scholte <[email protected]> >>> wrote: >>> >>> > So what would be the conclusion? >>> > >>> > 35% want to keep Java7 as JRE for Maven for a shorter or longer period? >>> > >>> > IMHO that's a lot >>> > >>> > Robert >>> > >>> > On Sun, 10 Sep 2017 11:55:20 +0200, Stephen Connolly < >>> > [email protected]> wrote: >>> > >>> > So poll results: >>> >> >>> >> 493 votes cast >>> >> >>> >> 25% want Java 7,8&9 for Maven 3.6.x >>> >> 65% want Java 8&9 for Maven 3.6.x >>> >> 10% want Java 8&9 for Maven 3.6.x and 6 months of backporting to 3.5.x >>> >> >>> >> On Sat 9 Sep 2017 at 11:50, Stephen Connolly < >>> >> [email protected]> wrote: >>> >> >>> >> https://twitter.com/asfmavenproject/status/906451059966693376 >>> >>> -- >>> >>> Sent from my phone >>> >>> >>> >> >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: [email protected] >>> > For additional commands, e-mail: [email protected] >>> > >>> > >>> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
