You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2013/07/23 15:59:49 UTC

[VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

This vote is to cover the minimum required version of Java for Maven Core.

Maven Plugins produced by the Apache Maven Project that are flagged as
compatible with older versions of Maven Core as their baseline will still
require to stick to the minimum Java requirements of that Maven Core
version. In other words, if for example maven-compiler-plugin advertises
compatibility with Maven Core 2.0.11+ then that will still need to be
compiled targeting Java 1.4 and only using dependencies that are aligned
with that runtime requirement.

Additionally patch releases to existing releases of Maven Core will not be
subject to this requirement.

For example [example]*if* this vote passes and *if* on Sep 29th we release
Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
issue that affected all versions of Maven) then only Maven 3.3.0 would be
require Java 6 as a minimum runtime requirement, the 2.0.12 release would
still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
all still require Java 1.5.[/example]

This is not a requirement that 3rd party plugins need use Java 6 as a
minimum. Third party plugins are free to require any Java version >= the
corresponding Maven minimum requirement, though obviously from a users
perspective it is best if plugins try to adhere to our contracts for
corresponding versions of Maven Core.

Justification for the cut-off date:

* Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
extended and sustaining support for existing Oracle customers using Java 5)
* IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
still with support, but there are other Java vendors for other platforms)
* Apple no longer supports any hardware that does not have at least an
Apple Java 6 version available.
* Red Hat is providing support for OpenJDK 6
* HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.

As I see it, that essentially ensures that for the vast majority of
platforms there is a very strong likelihood of a Java 6 compatible version
of Java available for that platform. Toolchains support or forking of the
compiler and surefire can provide support for users who still need to build
with older versions of Java (e.g., as was the case for Java 1.4.2 with
Maven 2.2.1). Additionally users who are forced to use a java version older
than Java 6 also are likely unable to upgrade their version of Maven, so
this change will not affect them

This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
from the PMC) and the majority of votes cast from committers will be
required to pass this vote.

+1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
(This option is equivalent to +1 but provides people the ability to
indicate an additional preference while not contributing to the inevitible
noise)
+1: Yes
0: No opinion
-1: No

-Stephen

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Jeff MAURY <je...@jeffmaury.com>.

+1

Jeff


On Tue, Jul 23, 2013 at 9:40 PM, Michael-O <19...@gmx.net> wrote:

> Am 2013-07-23 15:59, schrieb Stephen Connolly:
>
>  This vote is to cover the minimum required version of Java for Maven Core.
>>
>>
> Given than most companies/folks react only when something has been
> discontinued, I would move to Java 6 as a baseline not before Christman
> 2013. First release in 2014 can ben Java 6+.
>
> E.g., we now have a policy to make all apps run in Java 7 but this will
> take months and even some are not compatible (doesn't concern mine...but).
>
> So -0,
>
> Michael
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Stephen Connolly <st...@gmail.com>.

On Tuesday, 23 July 2013, Michael-O <19...@gmx.net> wrote:

> Am 2013-07-23 15:59, schrieb Stephen Connolly:
>
>> This vote is to cover the minimum required version of Java for Maven Core.
>>
>>
> Given than most companies/folks react only when something has been
> discontinued, I would move to Java 6 as a baseline not before Christman
> 2013. First release in 2014 can ben Java 6+.

We are not changing the date in this vote. If the vote passes the date
stands. If the vote fails we may decide to try again with a different date.

Any date we pick will have objections. Users will be slow picking up new
versions anyway, and this only talks about new major/minor versions of core
after the date... It may be that we have no such release for a while (heck
it took 6+ months to get a very small change set of 3.1.0 out the door)

This vote tries to set a line in the sand against which we can say "fair
notice was given"

My €0.02

>
> E.g., we now have a policy to make all apps run in Java 7 but this will
> take months and even some are not compatible (doesn't concern mine...but).
>
> So -0,
>
> Michael
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

-- 
Sent from my phone

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Michael-O <19...@gmx.net>.

Am 2013-07-23 15:59, schrieb Stephen Connolly:
> This vote is to cover the minimum required version of Java for Maven Core.
>

Given than most companies/folks react only when something has been 
discontinued, I would move to Java 6 as a baseline not before Christman 
2013. First release in 2014 can ben Java 6+.

E.g., we now have a policy to make all apps run in Java 7 but this will 
take months and even some are not compatible (doesn't concern mine...but).

So -0,

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Stevo Slavić <ss...@gmail.com>.

+1 (non-binding)


On Tue, Jul 23, 2013 at 10:59 PM, Dennis Lundberg <de...@apache.org>wrote:

> +1 (binding)
>
> On Tue, Jul 23, 2013 at 3:59 PM, Stephen Connolly
> <st...@gmail.com> wrote:
> > This vote is to cover the minimum required version of Java for Maven
> Core.
> >
> > Maven Plugins produced by the Apache Maven Project that are flagged as
> > compatible with older versions of Maven Core as their baseline will still
> > require to stick to the minimum Java requirements of that Maven Core
> > version. In other words, if for example maven-compiler-plugin advertises
> > compatibility with Maven Core 2.0.11+ then that will still need to be
> > compiled targeting Java 1.4 and only using dependencies that are aligned
> > with that runtime requirement.
> >
> > Additionally patch releases to existing releases of Maven Core will not
> be
> > subject to this requirement.
> >
> > For example [example]*if* this vote passes and *if* on Sep 29th we
> release
> > Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> Maven
> > 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> > issue that affected all versions of Maven) then only Maven 3.3.0 would be
> > require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> > still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> would
> > all still require Java 1.5.[/example]
> >
> > This is not a requirement that 3rd party plugins need use Java 6 as a
> > minimum. Third party plugins are free to require any Java version >= the
> > corresponding Maven minimum requirement, though obviously from a users
> > perspective it is best if plugins try to adhere to our contracts for
> > corresponding versions of Maven Core.
> >
> > Justification for the cut-off date:
> >
> > * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> still
> > extended and sustaining support for existing Oracle customers using Java
> 5)
> > * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> > still with support, but there are other Java vendors for other platforms)
> > * Apple no longer supports any hardware that does not have at least an
> > Apple Java 6 version available.
> > * Red Hat is providing support for OpenJDK 6
> > * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
> >
> > As I see it, that essentially ensures that for the vast majority of
> > platforms there is a very strong likelihood of a Java 6 compatible
> version
> > of Java available for that platform. Toolchains support or forking of the
> > compiler and surefire can provide support for users who still need to
> build
> > with older versions of Java (e.g., as was the case for Java 1.4.2 with
> > Maven 2.2.1). Additionally users who are forced to use a java version
> older
> > than Java 6 also are likely unable to upgrade their version of Maven, so
> > this change will not affect them
> >
> > This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> > from the PMC) and the majority of votes cast from committers will be
> > required to pass this vote.
> >
> > +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> > (This option is equivalent to +1 but provides people the ability to
> > indicate an additional preference while not contributing to the
> inevitible
> > noise)
> > +1: Yes
> > 0: No opinion
> > -1: No
> >
> > -Stephen
>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Dennis Lundberg <de...@apache.org>.

+1 (binding)

On Tue, Jul 23, 2013 at 3:59 PM, Stephen Connolly
<st...@gmail.com> wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen



-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by John Casey <jd...@commonjava.org>.

+1

On 7/23/13 8:59 AM, Stephen Connolly wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen
>


-- 
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
GitHub - http://github.com/jdcasey

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Chris Graham <ch...@gmail.com>.

I'm cool with that.

+1

PS: The EOL date for Java 1.5 was not just for zOS, it applied to all
platforms for the IBM JDK, AIX and Linux included.


On Wed, Jul 24, 2013 at 8:42 AM, Olivier Lamy <ol...@apache.org> wrote:

> +1
>
> 2013/7/23 Stephen Connolly <st...@gmail.com>:
> > This vote is to cover the minimum required version of Java for Maven
> Core.
> >
> > Maven Plugins produced by the Apache Maven Project that are flagged as
> > compatible with older versions of Maven Core as their baseline will still
> > require to stick to the minimum Java requirements of that Maven Core
> > version. In other words, if for example maven-compiler-plugin advertises
> > compatibility with Maven Core 2.0.11+ then that will still need to be
> > compiled targeting Java 1.4 and only using dependencies that are aligned
> > with that runtime requirement.
> >
> > Additionally patch releases to existing releases of Maven Core will not
> be
> > subject to this requirement.
> >
> > For example [example]*if* this vote passes and *if* on Sep 29th we
> release
> > Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> Maven
> > 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> > issue that affected all versions of Maven) then only Maven 3.3.0 would be
> > require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> > still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> would
> > all still require Java 1.5.[/example]
> >
> > This is not a requirement that 3rd party plugins need use Java 6 as a
> > minimum. Third party plugins are free to require any Java version >= the
> > corresponding Maven minimum requirement, though obviously from a users
> > perspective it is best if plugins try to adhere to our contracts for
> > corresponding versions of Maven Core.
> >
> > Justification for the cut-off date:
> >
> > * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> still
> > extended and sustaining support for existing Oracle customers using Java
> 5)
> > * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> > still with support, but there are other Java vendors for other platforms)
> > * Apple no longer supports any hardware that does not have at least an
> > Apple Java 6 version available.
> > * Red Hat is providing support for OpenJDK 6
> > * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
> >
> > As I see it, that essentially ensures that for the vast majority of
> > platforms there is a very strong likelihood of a Java 6 compatible
> version
> > of Java available for that platform. Toolchains support or forking of the
> > compiler and surefire can provide support for users who still need to
> build
> > with older versions of Java (e.g., as was the case for Java 1.4.2 with
> > Maven 2.2.1). Additionally users who are forced to use a java version
> older
> > than Java 6 also are likely unable to upgrade their version of Maven, so
> > this change will not affect them
> >
> > This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> > from the PMC) and the majority of votes cast from committers will be
> > required to pass this vote.
> >
> > +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> > (This option is equivalent to +1 but provides people the ability to
> > indicate an additional preference while not contributing to the
> inevitible
> > noise)
> > +1: Yes
> > 0: No opinion
> > -1: No
> >
> > -Stephen
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> 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: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Olivier Lamy <ol...@apache.org>.

+1

2013/7/23 Stephen Connolly <st...@gmail.com>:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
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: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Tamás Cservenák <ta...@cservenak.net>.

+1 nb
On Jul 23, 2013 4:00 PM, "Stephen Connolly" <st...@gmail.com>
wrote:

> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Paul Benedict <pb...@apache.org>.

+1 non binding.


On Tue, Jul 23, 2013 at 10:33 AM, Jeff Jensen <
jeffjensen@upstairstechnology.com> wrote:

> +1 (non-binding)
>
> On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
> <st...@gmail.com> wrote:
> > This vote is to cover the minimum required version of Java for Maven
> Core.
> >
> > Maven Plugins produced by the Apache Maven Project that are flagged as
> > compatible with older versions of Maven Core as their baseline will still
> > require to stick to the minimum Java requirements of that Maven Core
> > version. In other words, if for example maven-compiler-plugin advertises
> > compatibility with Maven Core 2.0.11+ then that will still need to be
> > compiled targeting Java 1.4 and only using dependencies that are aligned
> > with that runtime requirement.
> >
> > Additionally patch releases to existing releases of Maven Core will not
> be
> > subject to this requirement.
> >
> > For example [example]*if* this vote passes and *if* on Sep 29th we
> release
> > Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> Maven
> > 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> > issue that affected all versions of Maven) then only Maven 3.3.0 would be
> > require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> > still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> would
> > all still require Java 1.5.[/example]
> >
> > This is not a requirement that 3rd party plugins need use Java 6 as a
> > minimum. Third party plugins are free to require any Java version >= the
> > corresponding Maven minimum requirement, though obviously from a users
> > perspective it is best if plugins try to adhere to our contracts for
> > corresponding versions of Maven Core.
> >
> > Justification for the cut-off date:
> >
> > * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> still
> > extended and sustaining support for existing Oracle customers using Java
> 5)
> > * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> > still with support, but there are other Java vendors for other platforms)
> > * Apple no longer supports any hardware that does not have at least an
> > Apple Java 6 version available.
> > * Red Hat is providing support for OpenJDK 6
> > * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
> >
> > As I see it, that essentially ensures that for the vast majority of
> > platforms there is a very strong likelihood of a Java 6 compatible
> version
> > of Java available for that platform. Toolchains support or forking of the
> > compiler and surefire can provide support for users who still need to
> build
> > with older versions of Java (e.g., as was the case for Java 1.4.2 with
> > Maven 2.2.1). Additionally users who are forced to use a java version
> older
> > than Java 6 also are likely unable to upgrade their version of Maven, so
> > this change will not affect them
> >
> > This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> > from the PMC) and the majority of votes cast from committers will be
> > required to pass this vote.
> >
> > +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> > (This option is equivalent to +1 but provides people the ability to
> > indicate an additional preference while not contributing to the
> inevitible
> > noise)
> > +1: Yes
> > 0: No opinion
> > -1: No
> >
> > -Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Cheers,
Paul

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Jeff Jensen <je...@upstairstechnology.com>.

+1 (non-binding)

On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
<st...@gmail.com> wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Stephen Connolly <st...@gmail.com>.

The split verifier should improve cli performance once core and most
plugins are on -target 1.6

Any committer is free to call a vote to up the minimum to 1.7 if they want
to.

>From a build tool perspective there are some advantages in 1.6 as a
baseline (compiler api, scripting api, split verifier for faster initial
classloading, etc).

>From a non build tool perspective, String.isEmpty() is rather paltry though!

On Wednesday, 24 July 2013, Christian Schulte wrote:

> Am 07/24/13 04:00, schrieb jieryn:
> >
> > Move forward or die. If you are stuck on 1.5, you can continue to use
> > a full stack that is already supported. I am so sick of hearing people
> > complain that they will be broken if a JDK migration to a newer
> > version is undertaken. No, you are not broken, you simply can not
> > upgrade. There is a huge difference between being broken and not
> > having an upgrade path.
>
> Upgrade to Java 7 because you make use of the new APIs Java 7 introduces
> or stay with Java 5. Java 6 does not introduce anything interesting to
> Maven core. Java 7 does.
>
> > This form of anti-migration argument has less value than a "without
> > any requirement" argument for not migrating.
>
> I do not argue against migrating. I do argue against migrating without
> any reason.
>
> Since this is a vote thread:
>
> +1000 (non-binding) as long as someone explains why there is any need to
> change '-target 1.5' to '-target 1.6'. Seriously. I don't get it. You
> are really just changing the class file version and nothing else without
> any reason. I would like to know the reasioning. Nothing more.
>
> --
> Christan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>

-- 
Sent from my phone

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Christian Schulte <cs...@schulte.it>.

Am 07/24/13 04:00, schrieb jieryn:
> 
> Move forward or die. If you are stuck on 1.5, you can continue to use
> a full stack that is already supported. I am so sick of hearing people
> complain that they will be broken if a JDK migration to a newer
> version is undertaken. No, you are not broken, you simply can not
> upgrade. There is a huge difference between being broken and not
> having an upgrade path.

Upgrade to Java 7 because you make use of the new APIs Java 7 introduces
or stay with Java 5. Java 6 does not introduce anything interesting to
Maven core. Java 7 does.

> This form of anti-migration argument has less value than a "without
> any requirement" argument for not migrating.

I do not argue against migrating. I do argue against migrating without
any reason.

Since this is a vote thread:

+1000 (non-binding) as long as someone explains why there is any need to
change '-target 1.5' to '-target 1.6'. Seriously. I don't get it. You
are really just changing the class file version and nothing else without
any reason. I would like to know the reasioning. Nothing more.

-- 
Christan


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by jieryn <ji...@gmail.com>.

Greetings,

On Tue, Jul 23, 2013 at 9:52 PM, Christian Schulte <cs...@schulte.it> wrote:
> Why change '-target 1.5' to '-target 1.6' without any requirement to do
> so ? Either stay with '-target 1.5' or introduce something which
> requires '-target 1.6' as a justification. Don't get me wrong. I don't
> get the point.

Move forward or die. If you are stuck on 1.5, you can continue to use
a full stack that is already supported. I am so sick of hearing people
complain that they will be broken if a JDK migration to a newer
version is undertaken. No, you are not broken, you simply can not
upgrade. There is a huge difference between being broken and not
having an upgrade path.

Should we ensure that Apache Maven can fit on a 1.4mb floppy disk,
also?? I mean, we're breaking everyone that runs Apache Maven on a
networkless machine without any USB drive and has to use 1.4mb
floppies to transfer Maven Central, etc.

This form of anti-migration argument has less value than a "without
any requirement" argument for not migrating.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Christian Schulte <cs...@schulte.it>.

Am 07/24/13 03:10, schrieb jieryn:
> Greetings,
> 
> On Tue, Jul 23, 2013 at 8:59 PM, Christian Schulte <cs...@schulte.it> wrote:
>> Why Java 6 ? Seriously. It does not add any value to Maven compared to
>> Java 5. Java 7 is what provides new APIs Maven could benefit from. Why
>> give up on Java 5 in favour of Java 6 ?
> 
> "Politics is a strong and _slow_ boring of hard boards." -- Max Weber
> 
> My emphasis.
> 

Why change '-target 1.5' to '-target 1.6' without any requirement to do
so ? Either stay with '-target 1.5' or introduce something which
requires '-target 1.6' as a justification. Don't get me wrong. I don't
get the point.

-- 
Christian


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by jieryn <ji...@gmail.com>.

Greetings,

On Tue, Jul 23, 2013 at 8:59 PM, Christian Schulte <cs...@schulte.it> wrote:
> Why Java 6 ? Seriously. It does not add any value to Maven compared to
> Java 5. Java 7 is what provides new APIs Maven could benefit from. Why
> give up on Java 5 in favour of Java 6 ?

"Politics is a strong and _slow_ boring of hard boards." -- Max Weber

My emphasis.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Christian Schulte <cs...@schulte.it>.

Why Java 6 ? Seriously. It does not add any value to Maven compared to
Java 5. Java 7 is what provides new APIs Maven could benefit from. Why
give up on Java 5 in favour of Java 6 ?

-- 
Christian


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Barrie Treloar <ba...@gmail.com>.

+1 binding

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Wayne Fay <wa...@gmail.com>.

+1 binding

Wayne

On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
<st...@gmail.com> wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Robert Scholte <rf...@apache.org>.

+1

Op Tue, 23 Jul 2013 15:59:49 +0200 schreef Stephen Connolly  
<st...@gmail.com>:

> This vote is to cover the minimum required version of Java for Maven  
> Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not  
> be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we  
> release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,  
> Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions  
> would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is  
> still
> extended and sustaining support for existing Oracle customers using Java  
> 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible  
> version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to  
> build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version  
> older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the  
> inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Anders Hammar <an...@hammar.net>.

+1 (non-binding)

/Anders (mobile)
Den 23 jul 2013 16:00 skrev "Stephen Connolly" <
stephen.alan.connolly@gmail.com>:

> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Kristian Rosenvold <kr...@gmail.com>.

+1

2013/7/23 Stephen Connolly <st...@gmail.com>:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Arnaud Héritier <ah...@gmail.com>.

+1
Arnaud


On Tue, Jul 23, 2013 at 8:17 PM, Baptiste MATHUS <ml...@batmat.net> wrote:

> +1
> Le 23 juil. 2013 16:30, "Lennart Jörelid" <le...@gmail.com> a
> écrit :
>
> > +1000  .... which is a rather odd number for a vote; blame Stephen
> instead
> > of me.   :)
> >
> > I think we can skip the 1.6 release of the JDK as a Maven basis; JDK 1.6
> is
> > at or near EOL and the step from one
> > minimum JDK version to another (i.e. JDK 1.7) would be just as painful as
> > the step to JDK 1.6 - but with added
> > longevity, feature set and power.
> >
> >
> > 2013/7/23 Fred Cooke <fr...@gmail.com>
> >
> > > +1, unsure if you could have muddied the essentially simple question
> > > much more, but OK. :-p
> > >
> > > On Tue, Jul 23, 2013 at 4:00 PM, Stephen Connolly
> > > <st...@gmail.com> wrote:
> > > > +1 (binding)
> > > >
> > > >
> > > > On 23 July 2013 14:59, Stephen Connolly <
> > stephen.alan.connolly@gmail.com
> > > >wrote:
> > > >
> > > >> This vote is to cover the minimum required version of Java for Maven
> > > Core.
> > > >>
> > > >> Maven Plugins produced by the Apache Maven Project that are flagged
> as
> > > >> compatible with older versions of Maven Core as their baseline will
> > > still
> > > >> require to stick to the minimum Java requirements of that Maven Core
> > > >> version. In other words, if for example maven-compiler-plugin
> > advertises
> > > >> compatibility with Maven Core 2.0.11+ then that will still need to
> be
> > > >> compiled targeting Java 1.4 and only using dependencies that are
> > aligned
> > > >> with that runtime requirement.
> > > >>
> > > >> Additionally patch releases to existing releases of Maven Core will
> > not
> > > be
> > > >> subject to this requirement.
> > > >>
> > > >> For example [example]*if* this vote passes and *if* on Sep 29th we
> > > release
> > > >> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven
> 2.2.2,
> > > Maven
> > > >> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some
> > > security
> > > >> issue that affected all versions of Maven) then only Maven 3.3.0
> would
> > > be
> > > >> require Java 6 as a minimum runtime requirement, the 2.0.12 release
> > > would
> > > >> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1
> versions
> > > would
> > > >> all still require Java 1.5.[/example]
> > > >>
> > > >> This is not a requirement that 3rd party plugins need use Java 6 as
> a
> > > >> minimum. Third party plugins are free to require any Java version >=
> > the
> > > >> corresponding Maven minimum requirement, though obviously from a
> users
> > > >> perspective it is best if plugins try to adhere to our contracts for
> > > >> corresponding versions of Maven Core.
> > > >>
> > > >> Justification for the cut-off date:
> > > >>
> > > >> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> > > still
> > > >> extended and sustaining support for existing Oracle customers using
> > > Java 5)
> > > >> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms
> > are
> > > >> still with support, but there are other Java vendors for other
> > > platforms)
> > > >> * Apple no longer supports any hardware that does not have at least
> an
> > > >> Apple Java 6 version available.
> > > >> * Red Hat is providing support for OpenJDK 6
> > > >> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation
> > available.
> > > >>
> > > >> As I see it, that essentially ensures that for the vast majority of
> > > >> platforms there is a very strong likelihood of a Java 6 compatible
> > > version
> > > >> of Java available for that platform. Toolchains support or forking
> of
> > > the
> > > >> compiler and surefire can provide support for users who still need
> to
> > > build
> > > >> with older versions of Java (e.g., as was the case for Java 1.4.2
> with
> > > >> Maven 2.2.1). Additionally users who are forced to use a java
> version
> > > older
> > > >> than Java 6 also are likely unable to upgrade their version of
> Maven,
> > so
> > > >> this change will not affect them
> > > >>
> > > >> This vote is open for 72 hours. A minimum of three +1 binding votes
> > > (i.e.
> > > >> from the PMC) and the majority of votes cast from committers will be
> > > >> required to pass this vote.
> > > >>
> > > >> +1000: Yes, and when can we have the vote to go for Java 7 as a
> > minimum?
> > > >> (This option is equivalent to +1 but provides people the ability to
> > > >> indicate an additional preference while not contributing to the
> > > inevitible
> > > >> noise)
> > > >> +1: Yes
> > > >> 0: No opinion
> > > >> -1: No
> > > >>
> > > >> -Stephen
> > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> >
> > --
> > +==============================+
> > | Bästa hälsningar,
> > | [sw. "Best regards"]
> > |
> > | Lennart Jörelid
> > | EAI Architect & Integrator
> > |
> > | jGuru Europe AB
> > | Mölnlycke - Kista
> > |
> > | Email: lj@jguru.se
> > | URL:   www.jguru.se
> > | Phone
> > | (skype):    jgurueurope
> > | (intl):     +46 708 507 603
> > | (domestic): 0708 - 507 603
> > +==============================+
> >
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Baptiste MATHUS <ml...@batmat.net>.

+1
Le 23 juil. 2013 16:30, "Lennart Jörelid" <le...@gmail.com> a
écrit :

> +1000  .... which is a rather odd number for a vote; blame Stephen instead
> of me.   :)
>
> I think we can skip the 1.6 release of the JDK as a Maven basis; JDK 1.6 is
> at or near EOL and the step from one
> minimum JDK version to another (i.e. JDK 1.7) would be just as painful as
> the step to JDK 1.6 - but with added
> longevity, feature set and power.
>
>
> 2013/7/23 Fred Cooke <fr...@gmail.com>
>
> > +1, unsure if you could have muddied the essentially simple question
> > much more, but OK. :-p
> >
> > On Tue, Jul 23, 2013 at 4:00 PM, Stephen Connolly
> > <st...@gmail.com> wrote:
> > > +1 (binding)
> > >
> > >
> > > On 23 July 2013 14:59, Stephen Connolly <
> stephen.alan.connolly@gmail.com
> > >wrote:
> > >
> > >> This vote is to cover the minimum required version of Java for Maven
> > Core.
> > >>
> > >> Maven Plugins produced by the Apache Maven Project that are flagged as
> > >> compatible with older versions of Maven Core as their baseline will
> > still
> > >> require to stick to the minimum Java requirements of that Maven Core
> > >> version. In other words, if for example maven-compiler-plugin
> advertises
> > >> compatibility with Maven Core 2.0.11+ then that will still need to be
> > >> compiled targeting Java 1.4 and only using dependencies that are
> aligned
> > >> with that runtime requirement.
> > >>
> > >> Additionally patch releases to existing releases of Maven Core will
> not
> > be
> > >> subject to this requirement.
> > >>
> > >> For example [example]*if* this vote passes and *if* on Sep 29th we
> > release
> > >> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> > Maven
> > >> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some
> > security
> > >> issue that affected all versions of Maven) then only Maven 3.3.0 would
> > be
> > >> require Java 6 as a minimum runtime requirement, the 2.0.12 release
> > would
> > >> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> > would
> > >> all still require Java 1.5.[/example]
> > >>
> > >> This is not a requirement that 3rd party plugins need use Java 6 as a
> > >> minimum. Third party plugins are free to require any Java version >=
> the
> > >> corresponding Maven minimum requirement, though obviously from a users
> > >> perspective it is best if plugins try to adhere to our contracts for
> > >> corresponding versions of Maven Core.
> > >>
> > >> Justification for the cut-off date:
> > >>
> > >> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> > still
> > >> extended and sustaining support for existing Oracle customers using
> > Java 5)
> > >> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms
> are
> > >> still with support, but there are other Java vendors for other
> > platforms)
> > >> * Apple no longer supports any hardware that does not have at least an
> > >> Apple Java 6 version available.
> > >> * Red Hat is providing support for OpenJDK 6
> > >> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation
> available.
> > >>
> > >> As I see it, that essentially ensures that for the vast majority of
> > >> platforms there is a very strong likelihood of a Java 6 compatible
> > version
> > >> of Java available for that platform. Toolchains support or forking of
> > the
> > >> compiler and surefire can provide support for users who still need to
> > build
> > >> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> > >> Maven 2.2.1). Additionally users who are forced to use a java version
> > older
> > >> than Java 6 also are likely unable to upgrade their version of Maven,
> so
> > >> this change will not affect them
> > >>
> > >> This vote is open for 72 hours. A minimum of three +1 binding votes
> > (i.e.
> > >> from the PMC) and the majority of votes cast from committers will be
> > >> required to pass this vote.
> > >>
> > >> +1000: Yes, and when can we have the vote to go for Java 7 as a
> minimum?
> > >> (This option is equivalent to +1 but provides people the ability to
> > >> indicate an additional preference while not contributing to the
> > inevitible
> > >> noise)
> > >> +1: Yes
> > >> 0: No opinion
> > >> -1: No
> > >>
> > >> -Stephen
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
>
> --
> +==============================+
> | Bästa hälsningar,
> | [sw. "Best regards"]
> |
> | Lennart Jörelid
> | EAI Architect & Integrator
> |
> | jGuru Europe AB
> | Mölnlycke - Kista
> |
> | Email: lj@jguru.se
> | URL:   www.jguru.se
> | Phone
> | (skype):    jgurueurope
> | (intl):     +46 708 507 603
> | (domestic): 0708 - 507 603
> +==============================+
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Lennart Jörelid <le...@gmail.com>.

+1000  .... which is a rather odd number for a vote; blame Stephen instead
of me.   :)

I think we can skip the 1.6 release of the JDK as a Maven basis; JDK 1.6 is
at or near EOL and the step from one
minimum JDK version to another (i.e. JDK 1.7) would be just as painful as
the step to JDK 1.6 - but with added
longevity, feature set and power.


2013/7/23 Fred Cooke <fr...@gmail.com>

> +1, unsure if you could have muddied the essentially simple question
> much more, but OK. :-p
>
> On Tue, Jul 23, 2013 at 4:00 PM, Stephen Connolly
> <st...@gmail.com> wrote:
> > +1 (binding)
> >
> >
> > On 23 July 2013 14:59, Stephen Connolly <stephen.alan.connolly@gmail.com
> >wrote:
> >
> >> This vote is to cover the minimum required version of Java for Maven
> Core.
> >>
> >> Maven Plugins produced by the Apache Maven Project that are flagged as
> >> compatible with older versions of Maven Core as their baseline will
> still
> >> require to stick to the minimum Java requirements of that Maven Core
> >> version. In other words, if for example maven-compiler-plugin advertises
> >> compatibility with Maven Core 2.0.11+ then that will still need to be
> >> compiled targeting Java 1.4 and only using dependencies that are aligned
> >> with that runtime requirement.
> >>
> >> Additionally patch releases to existing releases of Maven Core will not
> be
> >> subject to this requirement.
> >>
> >> For example [example]*if* this vote passes and *if* on Sep 29th we
> release
> >> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> Maven
> >> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some
> security
> >> issue that affected all versions of Maven) then only Maven 3.3.0 would
> be
> >> require Java 6 as a minimum runtime requirement, the 2.0.12 release
> would
> >> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> would
> >> all still require Java 1.5.[/example]
> >>
> >> This is not a requirement that 3rd party plugins need use Java 6 as a
> >> minimum. Third party plugins are free to require any Java version >= the
> >> corresponding Maven minimum requirement, though obviously from a users
> >> perspective it is best if plugins try to adhere to our contracts for
> >> corresponding versions of Maven Core.
> >>
> >> Justification for the cut-off date:
> >>
> >> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> still
> >> extended and sustaining support for existing Oracle customers using
> Java 5)
> >> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> >> still with support, but there are other Java vendors for other
> platforms)
> >> * Apple no longer supports any hardware that does not have at least an
> >> Apple Java 6 version available.
> >> * Red Hat is providing support for OpenJDK 6
> >> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
> >>
> >> As I see it, that essentially ensures that for the vast majority of
> >> platforms there is a very strong likelihood of a Java 6 compatible
> version
> >> of Java available for that platform. Toolchains support or forking of
> the
> >> compiler and surefire can provide support for users who still need to
> build
> >> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> >> Maven 2.2.1). Additionally users who are forced to use a java version
> older
> >> than Java 6 also are likely unable to upgrade their version of Maven, so
> >> this change will not affect them
> >>
> >> This vote is open for 72 hours. A minimum of three +1 binding votes
> (i.e.
> >> from the PMC) and the majority of votes cast from committers will be
> >> required to pass this vote.
> >>
> >> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> >> (This option is equivalent to +1 but provides people the ability to
> >> indicate an additional preference while not contributing to the
> inevitible
> >> noise)
> >> +1: Yes
> >> 0: No opinion
> >> -1: No
> >>
> >> -Stephen
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Fred Cooke <fr...@gmail.com>.

+1, unsure if you could have muddied the essentially simple question
much more, but OK. :-p

On Tue, Jul 23, 2013 at 4:00 PM, Stephen Connolly
<st...@gmail.com> wrote:
> +1 (binding)
>
>
> On 23 July 2013 14:59, Stephen Connolly <st...@gmail.com>wrote:
>
>> This vote is to cover the minimum required version of Java for Maven Core.
>>
>> Maven Plugins produced by the Apache Maven Project that are flagged as
>> compatible with older versions of Maven Core as their baseline will still
>> require to stick to the minimum Java requirements of that Maven Core
>> version. In other words, if for example maven-compiler-plugin advertises
>> compatibility with Maven Core 2.0.11+ then that will still need to be
>> compiled targeting Java 1.4 and only using dependencies that are aligned
>> with that runtime requirement.
>>
>> Additionally patch releases to existing releases of Maven Core will not be
>> subject to this requirement.
>>
>> For example [example]*if* this vote passes and *if* on Sep 29th we release
>> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
>> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
>> issue that affected all versions of Maven) then only Maven 3.3.0 would be
>> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
>> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
>> all still require Java 1.5.[/example]
>>
>> This is not a requirement that 3rd party plugins need use Java 6 as a
>> minimum. Third party plugins are free to require any Java version >= the
>> corresponding Maven minimum requirement, though obviously from a users
>> perspective it is best if plugins try to adhere to our contracts for
>> corresponding versions of Maven Core.
>>
>> Justification for the cut-off date:
>>
>> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
>> extended and sustaining support for existing Oracle customers using Java 5)
>> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
>> still with support, but there are other Java vendors for other platforms)
>> * Apple no longer supports any hardware that does not have at least an
>> Apple Java 6 version available.
>> * Red Hat is providing support for OpenJDK 6
>> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>>
>> As I see it, that essentially ensures that for the vast majority of
>> platforms there is a very strong likelihood of a Java 6 compatible version
>> of Java available for that platform. Toolchains support or forking of the
>> compiler and surefire can provide support for users who still need to build
>> with older versions of Java (e.g., as was the case for Java 1.4.2 with
>> Maven 2.2.1). Additionally users who are forced to use a java version older
>> than Java 6 also are likely unable to upgrade their version of Maven, so
>> this change will not affect them
>>
>> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
>> from the PMC) and the majority of votes cast from committers will be
>> required to pass this vote.
>>
>> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
>> (This option is equivalent to +1 but provides people the ability to
>> indicate an additional preference while not contributing to the inevitible
>> noise)
>> +1: Yes
>> 0: No opinion
>> -1: No
>>
>> -Stephen
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Stephen Connolly <st...@gmail.com>.

+1 (binding)


On 23 July 2013 14:59, Stephen Connolly <st...@gmail.com>wrote:

> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Tony Chemit <ch...@codelutin.com>.

On Tue, 23 Jul 2013 14:59:49 +0100
Stephen Connolly <st...@gmail.com> wrote:

+1 (non binding)

tony.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Andreas Gudian <an...@gmail.com>.

+1 non-binding


2013/7/25 Mirko Friedenhagen <mf...@gmail.com>

> +1 non-binding
> On Jul 23, 2013 4:00 PM, "Stephen Connolly" <
> stephen.alan.connolly@gmail.com>
> wrote:
>
> > This vote is to cover the minimum required version of Java for Maven
> Core.
> >
> > Maven Plugins produced by the Apache Maven Project that are flagged as
> > compatible with older versions of Maven Core as their baseline will still
> > require to stick to the minimum Java requirements of that Maven Core
> > version. In other words, if for example maven-compiler-plugin advertises
> > compatibility with Maven Core 2.0.11+ then that will still need to be
> > compiled targeting Java 1.4 and only using dependencies that are aligned
> > with that runtime requirement.
> >
> > Additionally patch releases to existing releases of Maven Core will not
> be
> > subject to this requirement.
> >
> > For example [example]*if* this vote passes and *if* on Sep 29th we
> release
> > Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2,
> Maven
> > 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> > issue that affected all versions of Maven) then only Maven 3.3.0 would be
> > require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> > still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions
> would
> > all still require Java 1.5.[/example]
> >
> > This is not a requirement that 3rd party plugins need use Java 6 as a
> > minimum. Third party plugins are free to require any Java version >= the
> > corresponding Maven minimum requirement, though obviously from a users
> > perspective it is best if plugins try to adhere to our contracts for
> > corresponding versions of Maven Core.
> >
> > Justification for the cut-off date:
> >
> > * Oracle has gone end of life on Java 6 Feb 2013 (note that there is
> still
> > extended and sustaining support for existing Oracle customers using Java
> 5)
> > * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> > still with support, but there are other Java vendors for other platforms)
> > * Apple no longer supports any hardware that does not have at least an
> > Apple Java 6 version available.
> > * Red Hat is providing support for OpenJDK 6
> > * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
> >
> > As I see it, that essentially ensures that for the vast majority of
> > platforms there is a very strong likelihood of a Java 6 compatible
> version
> > of Java available for that platform. Toolchains support or forking of the
> > compiler and surefire can provide support for users who still need to
> build
> > with older versions of Java (e.g., as was the case for Java 1.4.2 with
> > Maven 2.2.1). Additionally users who are forced to use a java version
> older
> > than Java 6 also are likely unable to upgrade their version of Maven, so
> > this change will not affect them
> >
> > This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> > from the PMC) and the majority of votes cast from committers will be
> > required to pass this vote.
> >
> > +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> > (This option is equivalent to +1 but provides people the ability to
> > indicate an additional preference while not contributing to the
> inevitible
> > noise)
> > +1: Yes
> > 0: No opinion
> > -1: No
> >
> > -Stephen
> >
>

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

Posted by Mirko Friedenhagen <mf...@gmail.com>.

+1 non-binding
On Jul 23, 2013 4:00 PM, "Stephen Connolly" <st...@gmail.com>
wrote:

> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen
>