Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B94BC104AC for ; Sun, 8 Mar 2015 18:41:19 +0000 (UTC) Received: (qmail 7990 invoked by uid 500); 8 Mar 2015 18:41:14 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 7912 invoked by uid 500); 8 Mar 2015 18:41:14 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 7900 invoked by uid 99); 8 Mar 2015 18:41:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Mar 2015 18:41:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stephen.alan.connolly@gmail.com designates 209.85.218.48 as permitted sender) Received: from [209.85.218.48] (HELO mail-oi0-f48.google.com) (209.85.218.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Mar 2015 18:40:48 +0000 Received: by oigh136 with SMTP id h136so25708408oig.1 for ; Sun, 08 Mar 2015 11:38:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nZmM7bRXTrEoIfl9eAwcKMWqBWnNitHoHoOSqtM/gF8=; b=Mq7kKgBreL26fZUZsCWRBNh2cdmkJKcVmLdeS21Dpv6y2HzZNtkLDlzEJJdd+MyZEy W66fvbMZ3Sz3MCVEBQoXOwyp9ZcP6xvu9IhntLAMjLaHxLLnD0A8lIqBYKMbWIDZbkgi YUGmD95roQ1ZSwYDutfs2oFZnSw+b89qhbwtba62qDAkE7sjYDPMdPX0vUPuo8kpcoUp 40/R2eELJs+BT9P7vIxrVuqCua4RCl4E9+UV4JhJfdAPHSroFm6xvi1PUVHoMUHL2wek S9BrJFqSh+k1yY5mK5KsS9wtREIDf3ekNyIdxQn2w/vv+cezy/XdzJYHtZHY5LF3m1C2 LYaQ== MIME-Version: 1.0 X-Received: by 10.182.227.132 with SMTP id sa4mr18910753obc.40.1425839911648; Sun, 08 Mar 2015 11:38:31 -0700 (PDT) Received: by 10.60.42.204 with HTTP; Sun, 8 Mar 2015 11:38:31 -0700 (PDT) In-Reply-To: <2755801.vAFOJAXGu8@herve-desktop> References: <54F849BF.4030908@ifedorenko.com> <1616999.DRxun3rpEm@herve-desktop> <2755801.vAFOJAXGu8@herve-desktop> Date: Sun, 8 Mar 2015 18:38:31 +0000 Message-ID: Subject: Re: move maven core to java 7? From: Stephen Connolly To: Maven Developers List Content-Type: multipart/alternative; boundary=001a11c2ee9e70c3680510cb39d8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2ee9e70c3680510cb39d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have a biased data point to throw into the mix: The Jenkins project would really like to ditch support for running on Java 6. When Maven releases a version that requires Java 7, and Olivier updates the "evil" plugin to use the new Maven dependencies, then Jenkins can force through dropping support for Java 6. If all this can happen before May's LTS this year then I will be very happy because that means in May 2016 I will no longer have to support CloudBees customers running Java 6. To get into the LTS that means we need a Maven release this month to allow sufficient soak. I don't buy Dennis' arg re wait until 3.4.0. To my mind if we are not bumping to Java 7 then this release should be 3.2.6 not 3.3.0... If we are calling it 3.3.0 then it should be Java 7+ in my mind On Sunday, March 8, 2015, Herv=C3=A9 BOUTEMY wrote: > Le dimanche 8 mars 2015 16:17:39 Dennis Lundberg a =C3=A9crit : > > On Sat, Mar 7, 2015 at 1:06 PM, Herv=C3=A9 BOUTEMY > wrote: > > >> There is nothing stoping you from releasing 3.3.0 on Java 6 now, and > > >> 3.4.0 > > >> on Java 7 in a few weeks. > > > > > > what I don't like with this plan is that it is exactly what happened > with > > > 3.1.1 then 3.2.1: we never did any bugfix for 3.1.1, 3.1.1 was a dead > > > branch for start. 3.2.2 bugfixes could/should have been backported to > > > 3.1.1, but who will ever do that? (not me...) > > > > That is the normal state in open source software. Not many people will > > volunteer to backport bugfixes to older release lines. It's a matter > > of putting your limited resources where it does most good, and also > > where your itch is. Usually this means working on HEAD. > > > > > I agree that the lack of schedule can be a problem if we decide to ma= ke > > > the > > > release this week-end: but if we take one week to integrate Java 7 > > > improvements (ie mostly syntax for better maintainability and a few n= ew > > > APIs) and take one week after that to test the result, IMHO we get a > > > better plan: a new Maven version, with features and the assurance we'= ll > > > do bugfix releases on it (the fact that it has upgraded Java > requirement > > > is just a fact on release notes) > > > > I'm not concerned that switching to Java 7 will introduce any new bugs > > in core, at least not until we start using new Java 7 features. > > > > What we should do is think about what is best for our users. Let's > > look at the pros and cons of the two alternatives: > > > > 1. Switch to Java 7 for Maven 3.3.0 > > > > Bad: Users that are restricted to Java 6 for some reason will not be > > able to benefit from the bug fixes and new features in 3.3.0 > > Good: One less release to make > Good: people (few?) who really need new Maven features on old Java will > learn > to use Toolchains > > > > > 2. Switch to Java 7 for Maven 3.4.0 > > > > Bad: One more release to make > > Good: Users that are restricted to Java 6 for some reason will benefit > > from the bug fixes and new features in 3.3.0, even though they might > > not get any more bugfixes on that release line, because work focus > > move to 3.4.0-SNAPSHOT as soon as 3.3.0 has been released > > > > > Regards, > > > > > > Herv=C3=A9 > > > > > > Le samedi 7 mars 2015 12:04:15 Dennis Lundberg a =C3=A9crit : > > >> Hi Kristian, > > >> > > >> Please note that I am not opposed to using Java 7 in the core. What = I > am > > >> objecting to is the planning, or rather the lack of it. > > >> > > >> We currently have core ready to be released on Java 6. Then just > before > > >> it > > >> is about to be released someone says, hey lets switch Java version = as > > >> well. IMO that is something you should plan for before work is even > > >> started > > >> on the next release. > > >> > > >> Then there is the agreement we made regarding Java versions and thei= r > > >> EOL. > > >> > > >> Switching to Java 7 before the release will mean that a fewer number > of > > >> users will be able to reap the benefits of the bugfixes and features > in > > >> Maven 3.3.0. > > >> > > >> There is nothing stoping you from releasing 3.3.0 on Java 6 now, and > > >> 3.4.0 > > >> on Java 7 in a few weeks. > > >> > > >> Weighing in all of this I don't see any reason to change the Java > version > > >> for 3.3.0. > > >> Den 6 mar 2015 13:54 skrev "Kristian Rosenvold" < > > >> > > >> kristian.rosenvold@gmail.com >: > > >> > I already have the full jdk7 port in a branch in github, so that > > >> > assumption > > >> > does not hold :) > > >> > > > >> > Kristian > > >> > > > >> > 2015-03-06 13:50 GMT+01:00 Dennis Lundberg >: > > >> > > Hi, > > >> > > > > >> > > If we are going to release 3.3.0 very soon, like this week or th= e > > >> > > next, there won't be any time to start using Java 7 features in > the > > >> > > 3.3.0 release. Therefor I would prefer to go with Java 6 for 3.3= .0 > > >> > > and > > >> > > announce, in the 3.3.0 release notes, that the 3.3.x line is the > last > > >> > > line that will work with Java 6. Depending on what the core > > >> > > developers > > >> > > want to focus on after the 3.3.0 release is done, the core can > either > > >> > > go 3.3.1-SNAPSHOT with Java 6 or 3.4.0-SNAPSHOT with Java 7. Thi= s > > >> > > would also be consistent with our policy [1] for > plugins/components > > >> > > wanting to move to a higher major Java version, in that we shoul= d > > >> > > release what we currently have in trunk before upgrading to a > higher > > >> > > major Java version. > > >> > > > > >> > > My votes are: > > >> > > -1 for Java 7 in 3.3.0 > > >> > > +1 for Java 7 in 3.4.0 > > >> > > > > >> > > > > >> > > [1] http://maven.apache.org/developers/java6.html > > >> > > > > >> > > On Thu, Mar 5, 2015 at 1:19 PM, Igor Fedorenko < > igor@ifedorenko.com > > > >> > > > > >> > > wrote: > > >> > > > With maven core version change to 3.3.0 on master, any > objections I > > >> > > > change compile source/target to java 7? > > >> > > > > > >> > > > -- > > >> > > > Regards, > > >> > > > Igor > > >> > > > > > >> > > > > ------------------------------------------------------------------- > > >> > > > -- > > >> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > > > >> > > > For additional commands, e-mail: dev-help@maven.apache.org > > > >> > > > > >> > > -- > > >> > > Dennis Lundberg > > >> > > > > >> > > > --------------------------------------------------------------------- > > >> > > 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 > > --=20 Sent from my phone --001a11c2ee9e70c3680510cb39d8--