Plugin testing

[Jason van Zyl]

Hi,

I updated the plugin-testing tools to work with Maven 3.1.0 to help Manfred get 
the Android Maven Plugin's test harness working with 3.1.0. A couple things:

1. There is an @Override for a method implemented for an interface which you 
can only start doing in Java 1.6 and the compiler was defaulting to 1.5 because 
no target/source were being specific. So I'm not sure if this is a mistake but 
I set the source/target to 1.6 so that I didn't have to remove the annotation. 

2. I should probably bump the version to 3.0.0-SNAPSHOT instead of the 
2.2-SNAPSHOT, any thoughts here?

3. And now that I'm working on this I'd like to get it out of Subversion and 
push it over to Git, any objections? I'd prefer to do that before making a 
branch for the older version.

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

Script timed out

Re: Plugin testing

[Fred Cooke]

1) No opinion.
2) No opinion.
3) HUGE +1

Thanks for your efforts! :-)

On Tue, Jul 23, 2013 at 1:54 PM, Jason van Zyl ja...@tesla.io wrote:
 Hi,

 I updated the plugin-testing tools to work with Maven 3.1.0 to help Manfred 
 get the Android Maven Plugin's test harness working with 3.1.0. A couple 
 things:

 1. There is an @Override for a method implemented for an interface which you 
 can only start doing in Java 1.6 and the compiler was defaulting to 1.5 
 because no target/source were being specific. So I'm not sure if this is a 
 mistake but I set the source/target to 1.6 so that I didn't have to remove 
 the annotation.

 2. I should probably bump the version to 3.0.0-SNAPSHOT instead of the 
 2.2-SNAPSHOT, any thoughts here?

 3. And now that I'm working on this I'd like to get it out of Subversion and 
 push it over to Git, any objections? I'd prefer to do that before making a 
 branch for the older version.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder,  Apache Maven
 http://twitter.com/jvanzyl
 -

 Script timed out







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

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

[Stephen Connolly]

+1 (binding)


On 23 July 2013 14:59, Stephen Connolly stephen.alan.conno...@gmail.comwrote:

 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

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

[Stephen Connolly]

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+

[Tony Chemit]

On Tue, 23 Jul 2013 14:59:49 +0100
Stephen Connolly stephen.alan.conno...@gmail.com wrote:

+1 (non binding)

tony.

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

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

[Fred Cooke]

+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
stephen.alan.conno...@gmail.com wrote:
 +1 (binding)


 On 23 July 2013 14:59, Stephen Connolly 
 stephen.alan.conno...@gmail.comwrote:

 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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Lennart Jörelid]

+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 fred.co...@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
 stephen.alan.conno...@gmail.com wrote:
  +1 (binding)
 
 
  On 23 July 2013 14:59, Stephen Connolly stephen.alan.conno...@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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 

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

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

[Stephen Connolly]

On 23 July 2013 15:29, Lennart Jörelid lennart.jore...@gmail.com wrote:

 +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.


I am not against holding a vote for Java 1.7 *after* we have got up to Java
1.6. OpenJDK6 is an open source implementation of Java 6 that essentially
means that it is possible to fix issues with Java 6 going forward. It is
not possible to do that with Java 5 as there is no open source release.

Let's get the baseline moved... the Jenkins project recently moved to Java
1.6 as the minimum runtime requirement (while keeping animal-sniffer so
that only Java 1.5 APIs are permitted in Jenkins core... in case there is a
backlash)... hopefully if we set a date, other projects will line up on
that date (I know Kohsuke would be keen to see Jenkins drop the Java 1.5
API requirements on Jenkins and IBM EOLing JDK 5 for z/OS seems like a fine
justification to cull JDK 5)

-Stephen

Maven archetype plugin - issue # 409

[Gilles Seghaier]

Hi all,

First of all STFB.

My name is Gilles Seghaier, I'm a 25 years old french computer engineer
working for TIBCO Sofware Inc. at Paris (France).
I have developed with Maven since 2012, implementing some custom plugins to
integrate my company solutions into Maven's ecosystem, helping developers
in their daily tasks.

I'm contacting you via this mailing list, because I didn't find another way
to share with some Maven's developers (through JIRA for example).

I would like to talk with you about Maven archetype plugin, especialy about
a JIRA issue (#409 http://jira.codehaus.org/browse/ARCHETYPE-409).
To summarize, this problem is about Maven partial archetype and integration
testing with the specific goal provided by Maven archetype plugin.

I have seen this issue is open for a while, and it's not expected to fix it
in next releases. I would like to know if I might help you resolving this
issue that do not require a big effort of coding.


Thanks you all for the great job that have been already done on Maven :)


Sincerly yours,


Gilles Seghaier
Direct: +33 (0)6 30 08 36 86
gsegh...@tibco.com / gilles.segha...@gmail.com

Re: Maven archetype plugin - issue # 409

[Anders Hammar]

Sure, go for it. Create a patch and attach it to the jira ticket.

/Anders (mobile)
Den 23 jul 2013 16:58 skrev Gilles Seghaier gilles.segha...@gmail.com:

 Hi all,

 First of all STFB.

 My name is Gilles Seghaier, I'm a 25 years old french computer engineer
 working for TIBCO Sofware Inc. at Paris (France).
 I have developed with Maven since 2012, implementing some custom plugins to
 integrate my company solutions into Maven's ecosystem, helping developers
 in their daily tasks.

 I'm contacting you via this mailing list, because I didn't find another way
 to share with some Maven's developers (through JIRA for example).

 I would like to talk with you about Maven archetype plugin, especialy about
 a JIRA issue (#409 http://jira.codehaus.org/browse/ARCHETYPE-409).
 To summarize, this problem is about Maven partial archetype and integration
 testing with the specific goal provided by Maven archetype plugin.

 I have seen this issue is open for a while, and it's not expected to fix it
 in next releases. I would like to know if I might help you resolving this
 issue that do not require a big effort of coding.


 Thanks you all for the great job that have been already done on Maven :)


 Sincerly yours,


 Gilles Seghaier
 Direct: +33 (0)6 30 08 36 86
 gsegh...@tibco.com / gilles.segha...@gmail.com

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

[Anders Hammar]

+1 (non-binding)

/Anders (mobile)
Den 23 jul 2013 16:00 skrev Stephen Connolly 
stephen.alan.conno...@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+

[Jeff Jensen]

+1 (non-binding)

On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
stephen.alan.conno...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Paul Benedict]

+1 non binding.


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

 +1 (non-binding)

 On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
 stephen.alan.conno...@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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Cheers,
Paul

Re: Maven archetype plugin - issue # 409

[Wayne Fay]

 First of all STFB.

I just have to ask... what is STFB? :) I can think of a few things
that might work but none seem appropriate.

Wayne

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

Re: [VOTE] Retire maven-idea-plugin

[Dennis Lundberg]

+1 from me as well.

On Fri, Jul 19, 2013 at 7:01 PM, Dennis Lundberg denn...@apache.org wrote:
 Hi

 It has been almost five years since I made the last release of
 maven-idea-plugin. The features in IDEA to integrate Maven has been greatly
 improved since then, making our own plugin obsolete. I therefor propose that
 we retire maven-idea-plugin.

 If this vote is successful I will make one final release of the plugin,
 making it clear on the plugin site that it has been retired. After that the
 source code will be moved into the retired area in Subversion.

 This is AFAIK the first vote to follow our process for retiring a plugin.
 For those interested, the process  is described here:
 http://maven.apache.org/developers/retirement-plan-plugins.html


 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

[RESULT] [VOTE] Retire maven-idea-plugin

[Dennis Lundberg]

Hi,

The vote has passed with the following result:

+1 (binding): Arnaud Héritier, Robert Scholte, Stéphane Nicoll, Ralph
Goers, Stephen Connolly, Olivier Lamy, Kristian Rosenvold, Wayne Fay,
Brett Porter, Dennis Lundberg
+1 (non binding): Lennart Jörelid, Anders Hammar, Baptiste Mathus, Chris Graham

I will continue with the steps required to retire this plugin.

On Fri, Jul 19, 2013 at 7:01 PM, Dennis Lundberg denn...@apache.org wrote:
 Hi

 It has been almost five years since I made the last release of
 maven-idea-plugin. The features in IDEA to integrate Maven has been greatly
 improved since then, making our own plugin obsolete. I therefor propose that
 we retire maven-idea-plugin.

 If this vote is successful I will make one final release of the plugin,
 making it clear on the plugin site that it has been retired. After that the
 source code will be moved into the retired area in Subversion.

 This is AFAIK the first vote to follow our process for retiring a plugin.
 For those interested, the process  is described here:
 http://maven.apache.org/developers/retirement-plan-plugins.html


 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

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

[Baptiste MATHUS]

+1
Le 23 juil. 2013 16:30, Lennart Jörelid lennart.jore...@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 fred.co...@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
  stephen.alan.conno...@gmail.com wrote:
   +1 (binding)
  
  
   On 23 July 2013 14:59, Stephen Connolly 
 stephen.alan.conno...@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-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 


 --

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

[VOTE] Release Apache Maven IDEA Plugin version 2.2.1

[Dennis Lundberg]

Hi,

This is the final release of this plugin. After this release it will
be retired, see separate vote thread for more info on that.

We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135styleName=Htmlversion=14478

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11135status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-008/
https://repository.apache.org/content/repositories/maven-008/org/apache/maven/plugins/maven-idea-plugin/2.2.1/maven-idea-plugin-2.2.1-source-release.zip

For those interested, the SCM URL can be found in the pom.xml that is
in the staging repo.

Staging site:
http://maven.apache.org/plugins-archives/maven-idea-plugin-2.2.1/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

-- 
Dennis Lundberg

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

Re: [VOTE] Retire Maven One Plugin

[Dennis Lundberg]

+1 from me.

On Sat, Jul 20, 2013 at 11:13 AM, Dennis Lundberg denn...@apache.org wrote:
 Hi,

 Now that we have Maven 1 at End-Of-Life, I think it's time to retire
 Maven One Plugin as well. It has been almost six years since the last
 release. I therefor propose that we retire maven-one-plugin.

 http://maven.apache.org/plugins/maven-one-plugin/

 If this vote is successful I will make one final release of the
 plugin, making it clear on the plugin site that it has been retired.
 After that the source code will be moved into the retired area in
 Subversion.

 The process for retiring a plugin is described here, and is being improved:
 http://maven.apache.org/developers/retirement-plan-plugins.html

 The vote is open for 72 hours.

 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

Re: [VOTE] Retire Maven Model Converter

[Dennis Lundberg]

+1 from me.

On Sat, Jul 20, 2013 at 7:26 PM, Dennis Lundberg denn...@apache.org wrote:
 Hi,

 The only consumer of Maven Model Converter we have left at the Apache
 Maven project is Maven One Plugin. If the vote for the retirement of
 Maven One Plugin succeeds we should also retire Maven Model Converter.
 The last release was made almost six years ago. Last time I checked
 Maven Model Converter was also used by the Apache Archiva project. The
 retirement plan is to move the component to the Apache Archiva
 project, if they want it.

 http://maven.apache.org/shared/maven-model-converter/

 I therefor propose that we retire maven-model-converter.

 If this vote is successful I will make one final release of the
 component (there are some issues that have been fixed) making it clear
 on the component site that it has been retired. After that the source
 code will be moved to the Apache Archiva project in Subversion, or if
 they do not want it to the retired area in Subversion.

 The process for retiring a plugin is described here:
 http://maven.apache.org/developers/retirement-plan-plugins.html

 The vote is open for 72 hours.

 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

[RESULT] [VOTE] Retire Maven Model Converter

[Dennis Lundberg]

Hi,

The vote has passed with the following result:

+1 (binding): Arnaud Héritier, Hervé Boutemy, Wayne Fay, Stephen
Connolly, Ralph Goers, Brett Porter, Dennis Lundberg
+1 (non binding): Lennart Jörelid, Baptiste Mathus

I will continue with the steps required to retire this shared component.

On Sat, Jul 20, 2013 at 7:26 PM, Dennis Lundberg denn...@apache.org wrote:
 Hi,

 The only consumer of Maven Model Converter we have left at the Apache
 Maven project is Maven One Plugin. If the vote for the retirement of
 Maven One Plugin succeeds we should also retire Maven Model Converter.
 The last release was made almost six years ago. Last time I checked
 Maven Model Converter was also used by the Apache Archiva project. The
 retirement plan is to move the component to the Apache Archiva
 project, if they want it.

 http://maven.apache.org/shared/maven-model-converter/

 I therefor propose that we retire maven-model-converter.

 If this vote is successful I will make one final release of the
 component (there are some issues that have been fixed) making it clear
 on the component site that it has been retired. After that the source
 code will be moved to the Apache Archiva project in Subversion, or if
 they do not want it to the retired area in Subversion.

 The process for retiring a plugin is described here:
 http://maven.apache.org/developers/retirement-plan-plugins.html

 The vote is open for 72 hours.

 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

[RESULT] [VOTE] Retire Maven One Plugin

[Dennis Lundberg]

Hi,

The vote has passed with the following result:

+1 (binding): Olivier Lamy, Robert Scholte, Arnaud Héritier, Hervé
Boutemy, Wayne Fay, Stephen Connolly, Ralph Goers, Brett Porter,
Stephane Nicoll, Dennis Lundberg
+1 (non binding): Anders Hammar, Lennart Jörelid, Baptiste Mathus

I will continue with the steps required to retire this plugin.

On Sat, Jul 20, 2013 at 11:13 AM, Dennis Lundberg denn...@apache.org wrote:
 Hi,

 Now that we have Maven 1 at End-Of-Life, I think it's time to retire
 Maven One Plugin as well. It has been almost six years since the last
 release. I therefor propose that we retire maven-one-plugin.

 http://maven.apache.org/plugins/maven-one-plugin/

 If this vote is successful I will make one final release of the
 plugin, making it clear on the plugin site that it has been retired.
 After that the source code will be moved into the retired area in
 Subversion.

 The process for retiring a plugin is described here, and is being improved:
 http://maven.apache.org/developers/retirement-plan-plugins.html

 The vote is open for 72 hours.

 [ ] +1 Yes, it's about time
 [ ] -1 No, because...

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

Re: [VOTE] Release Apache Maven IDEA Plugin version 2.2.1

[Dennis Lundberg]

+1 from me.

On Tue, Jul 23, 2013 at 8:23 PM, Dennis Lundberg
dennisl.apa...@gmail.com wrote:
 Hi,

 This is the final release of this plugin. After this release it will
 be retired, see separate vote thread for more info on that.

 We solved 1 issue:
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135styleName=Htmlversion=14478

 There are still a couple of issues left in JIRA:
 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11135status=1

 Staging repo:
 https://repository.apache.org/content/repositories/maven-008/
 https://repository.apache.org/content/repositories/maven-008/org/apache/maven/plugins/maven-idea-plugin/2.2.1/maven-idea-plugin-2.2.1-source-release.zip

 For those interested, the SCM URL can be found in the pom.xml that is
 in the staging repo.

 Staging site:
 http://maven.apache.org/plugins-archives/maven-idea-plugin-2.2.1/

 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

Re: Issue management and documentation for Apache resources, such as apache-jar-resource-bundle

[Dennis Lundberg]

Just realized that this might have got stuck in moderation since I
used the wrong From address...

On Sun, Jul 21, 2013 at 4:01 PM, Dennis Lundberg
dennisl.apa...@gmail.com wrote:
 Hi,

 I had a look at, and fixed https://jira.codehaus.org/browse/MRRESOURCES-69

 When I first saw the issue I thought, hey this is in the wrong JIRA
 project and went about trying to move it to the correct one. But there
 is no IssueManagement in any of the POMs at
 https://svn.apache.org/viewvc/maven/resources/trunk/

 There is a component apache-jar-resource-bundle that has been used
 on a couple of occasions at https://issues.apache.org/jira/browse/MPOM
 but it does feel like the right place for it either. I think we should
 set up a new separate JIRA project for these resource bundles in the
 ASF JIRA instance. Any suggestions for a name for it? I can take it to
 infra once we agree and have come up with a good name.

 Another thing is documentation. Currently there is a web site at
 http://maven.apache.org/apache-resource-bundles/ which kind of
 documents a couple of the resource bundles, but not all of them. The
 site (one page only) is currently published using the aggregator POM
 for the resource bundles. There is also a sample project called
 resources-bundles-sample that has a real POM that can be used to try
 out the different resource bundles. There is documentation inside that
 POM which is then duplicated in the site for the aggregator. It would
 be nice if we could have just one copy of the examples... We need to
 get something in place similar to what we have for our parent POMs.

 Since there is no JIRA-link from the site there is also no way, except
 by looking in svn, to find out what has happened in a particular
 release.

 By the way there is an issue about this at
 https://issues.apache.org/jira/browse/MPOM-28

 Thoughts and opinions?

 --
 Dennis Lundberg



-- 
Dennis Lundberg

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

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

[Arnaud Héritier]

+1
Arnaud


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

 +1
 Le 23 juil. 2013 16:30, Lennart Jörelid lennart.jore...@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 fred.co...@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
   stephen.alan.conno...@gmail.com wrote:
+1 (binding)
   
   
On 23 July 2013 14:59, Stephen Connolly 
  stephen.alan.conno...@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-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
  
 
 
  --
 
  --
  +==+
  | Bästa hälsningar,
  | [sw. Best regards]
  |
  | Lennart Jörelid
  | EAI Architect  Integrator
  |
  | jGuru Europe AB
  | Mölnlycke - Kista
  |
  | Email: l...@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+

[Tamás Cservenák]

+1 nb
On Jul 23, 2013 4:00 PM, Stephen Connolly stephen.alan.conno...@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+

[Michael-O]

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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Jeff MAURY]

+1

Jeff


On Tue, Jul 23, 2013 at 9:40 PM, Michael-O 1983-01...@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.**orgdev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@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

[VOTE] Release Apache Maven Model Converter version 2.3

[Dennis Lundberg]

Hi,

This will be the final release of this shared component. After this
release it will retire from the Apache Maven project and move to the
Apache Archiva project. See separate vote thread about that.

We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=14389

There are no issues left in JIRA (except for the one to retire, which
I'll close later):
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761component=13272status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-010/
https://repository.apache.org/content/repositories/maven-010/org/apache/maven/shared/maven-model-converter/2.3/maven-model-converter-2.3-source-release.zip

Staging site (not synced yet):
http://maven.apache.org/shared-archives/maven-model-converter-2.3/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

-- 
Dennis Lundberg

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

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

[Stephen Connolly]

On Tuesday, 23 July 2013, Michael-O 1983-01...@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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org



-- 
Sent from my phone

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

[Fred Cooke]

BIG +1 for 6, and small -1 for 7 for my own selfish reasons. The old
versions will always be available, and are forkable for anyone that needs a
fix, hence small -1 and not crying and moaning.

On Tue, Jul 23, 2013 at 4:51 PM, Stephen Connolly 
stephen.alan.conno...@gmail.com wrote:

 On 23 July 2013 15:29, Lennart Jörelid lennart.jore...@gmail.com wrote:

  +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.
 
 
 I am not against holding a vote for Java 1.7 *after* we have got up to Java
 1.6. OpenJDK6 is an open source implementation of Java 6 that essentially
 means that it is possible to fix issues with Java 6 going forward. It is
 not possible to do that with Java 5 as there is no open source release.

 Let's get the baseline moved... the Jenkins project recently moved to Java
 1.6 as the minimum runtime requirement (while keeping animal-sniffer so
 that only Java 1.5 APIs are permitted in Jenkins core... in case there is a
 backlash)... hopefully if we set a date, other projects will line up on
 that date (I know Kohsuke would be keen to see Jenkins drop the Java 1.5
 API requirements on Jenkins and IBM EOLing JDK 5 for z/OS seems like a fine
 justification to cull JDK 5)

 -Stephen

Re: [VOTE] Release Apache Maven IDEA Plugin version 2.2.1

[Stephen Connolly]

+1

On Tuesday, 23 July 2013, Dennis Lundberg wrote:

 Hi,

 This is the final release of this plugin. After this release it will
 be retired, see separate vote thread for more info on that.

 We solved 1 issue:

 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135styleName=Htmlversion=14478

 There are still a couple of issues left in JIRA:

 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11135status=1

 Staging repo:
 https://repository.apache.org/content/repositories/maven-008/

 https://repository.apache.org/content/repositories/maven-008/org/apache/maven/plugins/maven-idea-plugin/2.2.1/maven-idea-plugin-2.2.1-source-release.zip

 For those interested, the SCM URL can be found in the pom.xml that is
 in the staging repo.

 Staging site:
 http://maven.apache.org/plugins-archives/maven-idea-plugin-2.2.1/

 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 --
 Dennis Lundberg

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:;
 For additional commands, e-mail: dev-h...@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+

[Dennis Lundberg]

+1 (binding)

On Tue, Jul 23, 2013 at 3:59 PM, Stephen Connolly
stephen.alan.conno...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Stevo Slavić]

+1 (non-binding)


On Tue, Jul 23, 2013 at 10:59 PM, Dennis Lundberg denn...@apache.orgwrote:

 +1 (binding)

 On Tue, Jul 23, 2013 at 3:59 PM, Stephen Connolly
 stephen.alan.conno...@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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

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

[Wayne Fay]

+1 binding

Wayne

On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly
stephen.alan.conno...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Barrie Treloar]

+1 binding

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

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

[Kristian Rosenvold]

+1

2013/7/23 Stephen Connolly stephen.alan.conno...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Olivier Lamy]

+1

2013/7/23 Stephen Connolly stephen.alan.conno...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Chris Graham]

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 stephen.alan.conno...@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-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

SCM Providers

[Chris Graham]

Hey All.

In the RTC/Jazz forum, a request came up for the ability to associate a
Work Item with the commits that the SCM plugin does.

On the Jazz side, I think that I've worked things out.

However, I am unsure as to how to best do this on the maven and scm
provider side.

The generic question boils down to:

How can we supply a scm specific parameter to a specific scm provider?

One that is not applicable to all providers.

I really do not want to add a -D option. :-)

Thoughts/comments/suggestions?

-Chris

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

[Christian Schulte]

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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[jieryn]

Greetings,

On Tue, Jul 23, 2013 at 8:59 PM, Christian Schulte c...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Christian Schulte]

Am 07/24/13 03:10, schrieb jieryn:
 Greetings,
 
 On Tue, Jul 23, 2013 at 8:59 PM, Christian Schulte c...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[jieryn]

Greetings,

On Tue, Jul 23, 2013 at 9:52 PM, Christian Schulte c...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Christian Schulte]

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-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Model Converter version 2.3

[Olivier Lamy]

+1

2013/7/24 Dennis Lundberg denn...@apache.org:
 Hi,

 This will be the final release of this shared component. After this
 release it will retire from the Apache Maven project and move to the
 Apache Archiva project. See separate vote thread about that.

 We solved 6 issues:
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=14389

 There are no issues left in JIRA (except for the one to retire, which
 I'll close later):
 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761component=13272status=1

 Staging repo:
 https://repository.apache.org/content/repositories/maven-010/
 https://repository.apache.org/content/repositories/maven-010/org/apache/maven/shared/maven-model-converter/2.3/maven-model-converter-2.3-source-release.zip

 Staging site (not synced yet):
 http://maven.apache.org/shared-archives/maven-model-converter-2.3/

 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 --
 Dennis Lundberg

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




-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven IDEA Plugin version 2.2.1

[Olivier Lamy]

+1

2013/7/24 Dennis Lundberg dennisl.apa...@gmail.com:
 Hi,

 This is the final release of this plugin. After this release it will
 be retired, see separate vote thread for more info on that.

 We solved 1 issue:
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135styleName=Htmlversion=14478

 There are still a couple of issues left in JIRA:
 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11135status=1

 Staging repo:
 https://repository.apache.org/content/repositories/maven-008/
 https://repository.apache.org/content/repositories/maven-008/org/apache/maven/plugins/maven-idea-plugin/2.2.1/maven-idea-plugin-2.2.1-source-release.zip

 For those interested, the SCM URL can be found in the pom.xml that is
 in the staging repo.

 Staging site:
 http://maven.apache.org/plugins-archives/maven-idea-plugin-2.2.1/

 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 --
 Dennis Lundberg

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




-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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