You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <GG...@seagullsoftware.com> on 2011/01/24 21:20:12 UTC
[VOTE] Release commons-parent 18
This is a VOTE to release commons-parent 18.
[ ] +1: Yes
[ ] -1: No, because:
The changes since 17 are:
- Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java 1.3 profile.)
- Update plugins for Maven 3 compatibility:
- maven-site-plugin 2.0.1 -> 2.2
- maven-project-info-reports-plugin 2.1.2 -> 2.3.1
- Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with Maven 3.x. See http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html
- Update the commons-parent POM to allow using the apache-wide "apache-release" profile and still be somewhat commons compatible:
- activate the "apache-release" profile when deployment is run
- generate checksums when running install with the apache-release profile
- generate a sources jar for the tests.
(This should actually go into the Apache root POM).
This should allow deprecation and subsequent removal of the "release" and "rc" profiles from the commons parent POM in the long run.
- [COMMONSSITE-29] Use link in <reporting> configuration of the maven-javadoc-plugin
- [COMMONSSITE-29] added a java api link POM property that is configured in the javadoc plugin.
Gary Gregory
Senior Software Engineer
Rocket Software
3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
Tel: +1.404.760.1560
Email: ggregory@seagullsoftware.com
Web: seagull.rocketsoftware.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 18
Posted by sebb <se...@gmail.com>.
There was another change:
Updated maven-assembly-plugin: 2.2-beta-5 => 2.2
Seems OK to me.
+1 to release
On 24 January 2011 21:06, Simone Tripodi <si...@apache.org> wrote:
> I'm +1 for these changes, thanks for taking care of it!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Jan 24, 2011 at 9:59 PM, Gary Gregory
> <GG...@seagullsoftware.com> wrote:
>> My +1
>>
>> Gary
>> ggregory@apache.org
>> GGregory@seagullsoftware.com
>>
>>> -----Original Message-----
>>> From: Gary Gregory [mailto:GGregory@seagullsoftware.com]
>>> Sent: Monday, January 24, 2011 15:20
>>> To: Commons Developers List
>>> Subject: [VOTE] Release commons-parent 18
>>>
>>> This is a VOTE to release commons-parent 18.
>>>
>>> [ ] +1: Yes
>>> [ ] -1: No, because:
>>>
>>> The changes since 17 are:
>>>
>>> - Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java 1.3
>>> profile.)
>>>
>>> - Update plugins for Maven 3 compatibility:
>>> - maven-site-plugin 2.0.1 -> 2.2
>>> - maven-project-info-reports-plugin 2.1.2 -> 2.3.1
>>>
>>> - Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
>>> Maven 3.x. See http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-
>>> 3/maven-3.html
>>>
>>> - Update the commons-parent POM to allow using the apache-wide "apache-
>>> release" profile and still be somewhat commons compatible:
>>> - activate the "apache-release" profile when deployment is run
>>> - generate checksums when running install with the apache-release profile
>>> - generate a sources jar for the tests.
>>> (This should actually go into the Apache root POM).
>>>
>>> This should allow deprecation and subsequent removal of the "release" and
>>> "rc" profiles from the commons parent POM in the long run.
>>>
>>> - [COMMONSSITE-29] Use link in <reporting> configuration of the maven-
>>> javadoc-plugin
>>>
>>> - [COMMONSSITE-29] added a java api link POM property that is configured in
>>> the javadoc plugin.
>>>
>>> Gary Gregory
>>> Senior Software Engineer
>>> Rocket Software
>>> 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
>>> Tel: +1.404.760.1560
>>> Email: ggregory@seagullsoftware.com
>>> Web: seagull.rocketsoftware.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 18
Posted by Simone Tripodi <si...@apache.org>.
I'm +1 for these changes, thanks for taking care of it!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Jan 24, 2011 at 9:59 PM, Gary Gregory
<GG...@seagullsoftware.com> wrote:
> My +1
>
> Gary
> ggregory@apache.org
> GGregory@seagullsoftware.com
>
>> -----Original Message-----
>> From: Gary Gregory [mailto:GGregory@seagullsoftware.com]
>> Sent: Monday, January 24, 2011 15:20
>> To: Commons Developers List
>> Subject: [VOTE] Release commons-parent 18
>>
>> This is a VOTE to release commons-parent 18.
>>
>> [ ] +1: Yes
>> [ ] -1: No, because:
>>
>> The changes since 17 are:
>>
>> - Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java 1.3
>> profile.)
>>
>> - Update plugins for Maven 3 compatibility:
>> - maven-site-plugin 2.0.1 -> 2.2
>> - maven-project-info-reports-plugin 2.1.2 -> 2.3.1
>>
>> - Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
>> Maven 3.x. See http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-
>> 3/maven-3.html
>>
>> - Update the commons-parent POM to allow using the apache-wide "apache-
>> release" profile and still be somewhat commons compatible:
>> - activate the "apache-release" profile when deployment is run
>> - generate checksums when running install with the apache-release profile
>> - generate a sources jar for the tests.
>> (This should actually go into the Apache root POM).
>>
>> This should allow deprecation and subsequent removal of the "release" and
>> "rc" profiles from the commons parent POM in the long run.
>>
>> - [COMMONSSITE-29] Use link in <reporting> configuration of the maven-
>> javadoc-plugin
>>
>> - [COMMONSSITE-29] added a java api link POM property that is configured in
>> the javadoc plugin.
>>
>> Gary Gregory
>> Senior Software Engineer
>> Rocket Software
>> 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
>> Tel: +1.404.760.1560
>> Email: ggregory@seagullsoftware.com
>> Web: seagull.rocketsoftware.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [VOTE] Release commons-parent 18
Posted by Gary Gregory <GG...@seagullsoftware.com>.
My +1
Gary
ggregory@apache.org
GGregory@seagullsoftware.com
> -----Original Message-----
> From: Gary Gregory [mailto:GGregory@seagullsoftware.com]
> Sent: Monday, January 24, 2011 15:20
> To: Commons Developers List
> Subject: [VOTE] Release commons-parent 18
>
> This is a VOTE to release commons-parent 18.
>
> [ ] +1: Yes
> [ ] -1: No, because:
>
> The changes since 17 are:
>
> - Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java 1.3
> profile.)
>
> - Update plugins for Maven 3 compatibility:
> - maven-site-plugin 2.0.1 -> 2.2
> - maven-project-info-reports-plugin 2.1.2 -> 2.3.1
>
> - Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
> Maven 3.x. See http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-
> 3/maven-3.html
>
> - Update the commons-parent POM to allow using the apache-wide "apache-
> release" profile and still be somewhat commons compatible:
> - activate the "apache-release" profile when deployment is run
> - generate checksums when running install with the apache-release profile
> - generate a sources jar for the tests.
> (This should actually go into the Apache root POM).
>
> This should allow deprecation and subsequent removal of the "release" and
> "rc" profiles from the commons parent POM in the long run.
>
> - [COMMONSSITE-29] Use link in <reporting> configuration of the maven-
> javadoc-plugin
>
> - [COMMONSSITE-29] added a java api link POM property that is configured in
> the javadoc plugin.
>
> Gary Gregory
> Senior Software Engineer
> Rocket Software
> 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
> Tel: +1.404.760.1560
> Email: ggregory@seagullsoftware.com
> Web: seagull.rocketsoftware.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[RESULT][VOTE] Release commons-parent 18
Posted by Gary Gregory <GG...@seagullsoftware.com>.
This vote has passed with four +1 votes (four binding from [commons] committers) from the
following people:
Gary Gregory
Simone Tripodi
Sebastian Bazley
Luc Maisonobe
Gary
> -----Original Message-----
> From: Gary Gregory [mailto:GGregory@seagullsoftware.com]
> Sent: Monday, January 24, 2011 15:20
> To: Commons Developers List
> Subject: [VOTE] Release commons-parent 18
>
> This is a VOTE to release commons-parent 18.
>
> [ ] +1: Yes
> [ ] -1: No, because:
>
> The changes since 17 are:
>
> - Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java 1.3
> profile.)
>
> - Update plugins for Maven 3 compatibility:
> - maven-site-plugin 2.0.1 -> 2.2
> - maven-project-info-reports-plugin 2.1.2 -> 2.3.1
>
> - Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
> Maven 3.x. See http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-
> 3/maven-3.html
>
> - Update the commons-parent POM to allow using the apache-wide "apache-
> release" profile and still be somewhat commons compatible:
> - activate the "apache-release" profile when deployment is run
> - generate checksums when running install with the apache-release profile
> - generate a sources jar for the tests.
> (This should actually go into the Apache root POM).
>
> This should allow deprecation and subsequent removal of the "release" and
> "rc" profiles from the commons parent POM in the long run.
>
> - [COMMONSSITE-29] Use link in <reporting> configuration of the maven-
> javadoc-plugin
>
> - [COMMONSSITE-29] added a java api link POM property that is configured in
> the javadoc plugin.
>
> Gary Gregory
> Senior Software Engineer
> Rocket Software
> 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
> Tel: +1.404.760.1560
> Email: ggregory@seagullsoftware.com
> Web: seagull.rocketsoftware.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 18
Posted by lu...@free.fr.
----- "Gary Gregory" <GG...@seagullsoftware.com> a écrit :
> This is a VOTE to release commons-parent 18.
>
> [ ] +1: Yes
+1
Luc
> [ ] -1: No, because:
>
> The changes since 17 are:
>
> - Update to Surefire 2.7.1 (from the 2.5 default and 2.2 for the Java
> 1.3 profile.)
>
> - Update plugins for Maven 3 compatibility:
> - maven-site-plugin 2.0.1 -> 2.2
> - maven-project-info-reports-plugin 2.1.2 -> 2.3.1
>
> - Use maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x
> with Maven 3.x. See
> http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html
>
> - Update the commons-parent POM to allow using the apache-wide
> "apache-release" profile and still be somewhat commons compatible:
> - activate the "apache-release" profile when deployment is run
> - generate checksums when running install with the apache-release
> profile
> - generate a sources jar for the tests.
> (This should actually go into the Apache root POM).
>
> This should allow deprecation and subsequent removal of the
> "release" and "rc" profiles from the commons parent POM in the long
> run.
>
> - [COMMONSSITE-29] Use link in <reporting> configuration of the
> maven-javadoc-plugin
>
> - [COMMONSSITE-29] added a java api link POM property that is
> configured in the javadoc plugin.
>
> Gary Gregory
> Senior Software Engineer
> Rocket Software
> 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
> Tel: +1.404.760.1560
> Email: ggregory@seagullsoftware.com
> Web: seagull.rocketsoftware.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org