Re: [commons-release-plugin] Next

2018-05-12 Thread Rob Tompkins
I can hop in and help out with some of those. And probably can put some time 
into the plugin this week. 

> On May 12, 2018, at 11:40 AM, Gary Gregory  wrote:
> 
>> On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins  wrote:
>> 
>> 
>> 
>>> On May 10, 2018, at 12:11 PM, Gary Gregory 
>> wrote:
>>> 
 On Thu, May 10, 2018 at 9:53 AM, Matt Sicker  wrote:
 
> On 10 May 2018 at 09:34, Gary Gregory  wrote:
> 
> Another item would be to have ONE Maven call instead of SIX for:
> 
 
 It would be great to just do "mvn release:prepare release:perform", fill
 out the release candidate version, and then have everything uploaded and
 emailed properly. Unfortunately, I'm not familiar enough with maven to
>> know
 how to automate that sort of thing (in the past, I've usually offloaded
 that part to a CI pipeline script of some sort).
 
>>> 
>>> Right, in a dream world, there would be a simple one-liner for creating
>> an
>>> RC and another for promoting an RC to release.
>> 
>> All steps in that direction. I figure tackle the hard bits first, then
>> sort the remainders out. :-)
>> 
> 
> I'd like to release collections, text, pool, lang soon, so the better the
> plugin, the happier the RM ;-)
> 
> I'm not sure how much time I can devote to helping on the plugin but I am
> around to discuss and test.
> 
> Gary
> 
> 
>>> 
>>> Gary
>>> 
>>> 
 
 
 --
 Matt Sicker 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

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



Re: [DBCP] Drop Ant build?

2018-05-12 Thread Rob Tompkins


> On May 12, 2018, at 2:36 PM, Gary Gregory  wrote:
> 
> Hi All:
> 
> Commons DBCP still has an Ant build. Should we drop it?

+1, given that maven works. 

> 
> Gary

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



Re: [DBCP] Drop Ant build?

2018-05-12 Thread Pascal Schumacher

+1 for droping it

Am 12.05.2018 um 20:36 schrieb Gary Gregory:

Commons DBCP still has an Ant build. Should we drop it?




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



[RESULT][VOTE] Release Apache Commons DBCP 2.3.0 based on RC1

2018-05-12 Thread Gary Gregory
This VOTE passes with three (3) binding votes from the following PMC
members:

- Rob Tompkins (chtompki)
- Gary Gregory (ggregory)
- Oliver Heger (oheger)

I will proceed with the release today...

Gary

On Tue, May 8, 2018 at 6:08 PM, Gary Gregory  wrote:

> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons DBCP 2.2.0 was released, so I would like to release
> Commons DBCP 2.3.0.
>
> Commons DBCP 2.3.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
> 26776)
>
> The tag is here:
> https://git1-us-west.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=
> 830f0bf135ebc94cec7f2700171a2850430f76f7
>
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/
> orgapachecommons-1326/org/apache/commons/commons-dbcp2/2.3.0/
>
> These are the Maven artifacts and their hashes
>
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar.asc
> (SHA1: 61a0593f9e79568a17cdf96a27f35a153661811e)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar
> (SHA1: bbb2876368ecb71f0108af1e09ceeb17b8688176)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar.asc
> (SHA1: 9bd5ef92ff5716ca59afb64c0030d9cd1b08178b)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar
> (SHA1: 92fc4af0d3348c715bd4d78be4fd800a84eca604)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom
> (SHA1: 8baf6f5f0083960ff08b91e173847bf7aaa6ac7c)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-test-sources.jar
> (SHA1: 74bb2457d0b523a8dd7efc2538c705ece5ac53e8)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-sources.jar.asc
> (SHA1: 6ccd175cbbbe583015db4ad3c62e9fed19b7135d)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar
> (SHA1: fbe38b9ccf3e85b7ea712e56b2d31d9bbc775074)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-javadoc.jar.asc
> (SHA1: cc6606a256ec98028a8c357bab47dbacfdd154fe)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-test-sources.jar.asc
> (SHA1: 5b42b57b996266d2b7804d457af094cd00a93a88)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar
> (SHA1: 0ea7fbe2914a272794befb9c98f831cc754b9e04)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom.asc
> (SHA1: e962ee933cfeb18e1b061e3dce5e62487df958d1)
>
> I have tested this with:
>
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_172\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Details of changes since 2.2.0 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/RELEASE-NOTES.txt
> changes-report.html in https://dist.apache.org/repos/
> dist/dev/commons/dbcp/site.zip
>
> Site:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>   (note some *relative* links are broken and the 2.3.0 directories are
>   not yet created - these will be OK once the site is deployed)
>
>   The site contains a CLIRR report but not a JApiCmp report because I
> could not get JApiCmp to work.
>
> Clirr Report (compared to 2.2.0):
> clirr-report.html in https://dist.apache.org/repos/
> dist/dev/commons/dbcp/site.zip
>
> RAT Report:
> rat-report.html in https://dist.apache.org/repos/
> dist/dev/commons/dbcp/site.zip
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 04:00 UTC 31-March 2010
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> Gary Gregory
>


Re: [DBCP] Drop Ant build?

2018-05-12 Thread Oliver Heger


Am 12.05.2018 um 20:36 schrieb Gary Gregory:
> Hi All:
> 
> Commons DBCP still has an Ant build. Should we drop it?

No objections from me. I think we already dropped support for Ant for
most of our components.

Oliver

> 
> Gary
> 

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



[DBCP] Drop Ant build?

2018-05-12 Thread Gary Gregory
Hi All:

Commons DBCP still has an Ant build. Should we drop it?

Gary


Re: [VOTE] Release Apache Commons DBCP 2.3.0 based on RC1

2018-05-12 Thread Oliver Heger


Am 12.05.2018 um 20:16 schrieb Gary Gregory:
> On Sat, May 12, 2018 at 10:37 AM, Oliver Heger > wrote:
> 
>> Build works fine with Java 1.7 and 1.8 - even the ant build seems to
>> work. Artifacts and site look good.
>>
>> The only problem I noticed is that the release notes refer to version
>> "2.3.0-SNAPSHOT", which is confusing.
>>
>> Do you think this requires a new RC or can we live with that?
>>
> 
> I can update that one file on the dist server after the fact. The src zip
> will still contain the snapshot reference.
> 
> I'm not sure this really is a blocker, at least not for me now.

Ok, so +1 from me.

Oliver

> 
> Gary
> 
> 
> Oliver
>>
>> Am 09.05.2018 um 02:08 schrieb Gary Gregory:
>>> We have fixed quite a few bugs and added some significant enhancements
>>> since Apache Commons DBCP 2.2.0 was released, so I would like to release
>>> Commons DBCP 2.3.0.
>>>
>>> Commons DBCP 2.3.0 RC1 is available for review here:
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
>>> 26776)
>>>
>>> The tag is here:
>>>
>>> https://git1-us-west.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=
>> 830f0bf135ebc94cec7f2700171a2850430f76f7
>>>
>>> Maven artifacts are here:
>>>
>>> https://repository.apache.org/content/repositories/
>> orgapachecommons-1326/org/apache/commons/commons-dbcp2/2.3.0/
>>>
>>> These are the Maven artifacts and their hashes
>>>
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar.asc
>>> (SHA1: 61a0593f9e79568a17cdf96a27f35a153661811e)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar
>>> (SHA1: bbb2876368ecb71f0108af1e09ceeb17b8688176)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
>> 0-tests.jar.asc
>>> (SHA1: 9bd5ef92ff5716ca59afb64c0030d9cd1b08178b)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar
>>> (SHA1: 92fc4af0d3348c715bd4d78be4fd800a84eca604)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom
>>> (SHA1: 8baf6f5f0083960ff08b91e173847bf7aaa6ac7c)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
>> 0-test-sources.jar
>>> (SHA1: 74bb2457d0b523a8dd7efc2538c705ece5ac53e8)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
>> 0-sources.jar.asc
>>> (SHA1: 6ccd175cbbbe583015db4ad3c62e9fed19b7135d)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar
>>> (SHA1: fbe38b9ccf3e85b7ea712e56b2d31d9bbc775074)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
>> 0-javadoc.jar.asc
>>> (SHA1: cc6606a256ec98028a8c357bab47dbacfdd154fe)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
>> 0-test-sources.jar.asc
>>> (SHA1: 5b42b57b996266d2b7804d457af094cd00a93a88)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar
>>> (SHA1: 0ea7fbe2914a272794befb9c98f831cc754b9e04)
>>> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom.asc
>>> (SHA1: e962ee933cfeb18e1b061e3dce5e62487df958d1)
>>>
>>> I have tested this with:
>>>
>>> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
>>> 2018-02-24T12:49:05-07:00)
>>> Maven home: C:\Java\apache-maven-3.5.3\bin\..
>>> Java version: 1.8.0_172, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.8.0_172\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>>
>>> Details of changes since 2.2.0 are in the release notes:
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/RELEASE-
>> NOTES.txt
>>> changes-report.html in
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>>>
>>> Site:
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>>>   (note some *relative* links are broken and the 2.3.0 directories are
>>>   not yet created - these will be OK once the site is deployed)
>>>
>>>   The site contains a CLIRR report but not a JApiCmp report because I
>> could
>>> not get JApiCmp to work.
>>>
>>> Clirr Report (compared to 2.2.0):
>>> clirr-report.html in
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>>>
>>> RAT Report:
>>> rat-report.html in
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>>>
>>> KEYS:
>>>   https://www.apache.org/dist/commons/KEYS
>>>
>>> Please review the release candidate and vote.
>>> This vote will close no sooner that 72 hours from now,
>>> i.e. sometime after 04:00 UTC 31-March 2010
>>>
>>>   [ ] +1 Release these artifacts
>>>   [ ] +0 OK, but...
>>>   [ ] -0 OK, but really should fix...
>>>   [ ] -1 I oppose this release because...
>>>
>>> Thanks!
>>>
>>> Gary Gregory
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
> 

-
To unsubscribe, e-mail: 

Re: [VOTE] Release Apache Commons DBCP 2.3.0 based on RC1

2018-05-12 Thread Gary Gregory
On Sat, May 12, 2018 at 10:37 AM, Oliver Heger  wrote:

> Build works fine with Java 1.7 and 1.8 - even the ant build seems to
> work. Artifacts and site look good.
>
> The only problem I noticed is that the release notes refer to version
> "2.3.0-SNAPSHOT", which is confusing.
>
> Do you think this requires a new RC or can we live with that?
>

I can update that one file on the dist server after the fact. The src zip
will still contain the snapshot reference.

I'm not sure this really is a blocker, at least not for me now.

Gary


Oliver
>
> Am 09.05.2018 um 02:08 schrieb Gary Gregory:
> > We have fixed quite a few bugs and added some significant enhancements
> > since Apache Commons DBCP 2.2.0 was released, so I would like to release
> > Commons DBCP 2.3.0.
> >
> > Commons DBCP 2.3.0 RC1 is available for review here:
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
> > 26776)
> >
> > The tag is here:
> >
> > https://git1-us-west.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=
> 830f0bf135ebc94cec7f2700171a2850430f76f7
> >
> > Maven artifacts are here:
> >
> > https://repository.apache.org/content/repositories/
> orgapachecommons-1326/org/apache/commons/commons-dbcp2/2.3.0/
> >
> > These are the Maven artifacts and their hashes
> >
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar.asc
> > (SHA1: 61a0593f9e79568a17cdf96a27f35a153661811e)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar
> > (SHA1: bbb2876368ecb71f0108af1e09ceeb17b8688176)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-tests.jar.asc
> > (SHA1: 9bd5ef92ff5716ca59afb64c0030d9cd1b08178b)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar
> > (SHA1: 92fc4af0d3348c715bd4d78be4fd800a84eca604)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom
> > (SHA1: 8baf6f5f0083960ff08b91e173847bf7aaa6ac7c)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-test-sources.jar
> > (SHA1: 74bb2457d0b523a8dd7efc2538c705ece5ac53e8)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-sources.jar.asc
> > (SHA1: 6ccd175cbbbe583015db4ad3c62e9fed19b7135d)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar
> > (SHA1: fbe38b9ccf3e85b7ea712e56b2d31d9bbc775074)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-javadoc.jar.asc
> > (SHA1: cc6606a256ec98028a8c357bab47dbacfdd154fe)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.
> 0-test-sources.jar.asc
> > (SHA1: 5b42b57b996266d2b7804d457af094cd00a93a88)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar
> > (SHA1: 0ea7fbe2914a272794befb9c98f831cc754b9e04)
> > /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom.asc
> > (SHA1: e962ee933cfeb18e1b061e3dce5e62487df958d1)
> >
> > I have tested this with:
> >
> > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> > 2018-02-24T12:49:05-07:00)
> > Maven home: C:\Java\apache-maven-3.5.3\bin\..
> > Java version: 1.8.0_172, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk1.8.0_172\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> >
> > Details of changes since 2.2.0 are in the release notes:
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/RELEASE-
> NOTES.txt
> > changes-report.html in
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> >
> > Site:
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> >   (note some *relative* links are broken and the 2.3.0 directories are
> >   not yet created - these will be OK once the site is deployed)
> >
> >   The site contains a CLIRR report but not a JApiCmp report because I
> could
> > not get JApiCmp to work.
> >
> > Clirr Report (compared to 2.2.0):
> > clirr-report.html in
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> >
> > RAT Report:
> > rat-report.html in
> > https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> >
> > KEYS:
> >   https://www.apache.org/dist/commons/KEYS
> >
> > Please review the release candidate and vote.
> > This vote will close no sooner that 72 hours from now,
> > i.e. sometime after 04:00 UTC 31-March 2010
> >
> >   [ ] +1 Release these artifacts
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this release because...
> >
> > Thanks!
> >
> > Gary Gregory
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


Re: [commons-release-plugin] Next

2018-05-12 Thread Matt Benson
I'm going to want to release [weaver] soon as well, so I might like to
participate with plugin development.

Matt

On Sat, May 12, 2018, 10:40 AM Gary Gregory  wrote:

> On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins  wrote:
>
> >
> >
> > > On May 10, 2018, at 12:11 PM, Gary Gregory 
> > wrote:
> > >
> > > On Thu, May 10, 2018 at 9:53 AM, Matt Sicker  wrote:
> > >
> > >> On 10 May 2018 at 09:34, Gary Gregory  wrote:
> > >>
> > >>> Another item would be to have ONE Maven call instead of SIX for:
> > >>>
> > >>
> > >> It would be great to just do "mvn release:prepare release:perform",
> fill
> > >> out the release candidate version, and then have everything uploaded
> and
> > >> emailed properly. Unfortunately, I'm not familiar enough with maven to
> > know
> > >> how to automate that sort of thing (in the past, I've usually
> offloaded
> > >> that part to a CI pipeline script of some sort).
> > >>
> > >
> > > Right, in a dream world, there would be a simple one-liner for creating
> > an
> > > RC and another for promoting an RC to release.
> >
> > All steps in that direction. I figure tackle the hard bits first, then
> > sort the remainders out. :-)
> >
>
> I'd like to release collections, text, pool, lang soon, so the better the
> plugin, the happier the RM ;-)
>
> I'm not sure how much time I can devote to helping on the plugin but I am
> around to discuss and test.
>
> Gary
>
>
> > >
> > > Gary
> > >
> > >
> > >>
> > >>
> > >> --
> > >> Matt Sicker 
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>


Re: [VOTE] Release Apache Commons DBCP 2.3.0 based on RC1

2018-05-12 Thread Oliver Heger
Build works fine with Java 1.7 and 1.8 - even the ant build seems to
work. Artifacts and site look good.

The only problem I noticed is that the release notes refer to version
"2.3.0-SNAPSHOT", which is confusing.

Do you think this requires a new RC or can we live with that?
Oliver

Am 09.05.2018 um 02:08 schrieb Gary Gregory:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons DBCP 2.2.0 was released, so I would like to release
> Commons DBCP 2.3.0.
> 
> Commons DBCP 2.3.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
> 26776)
> 
> The tag is here:
> 
> https://git1-us-west.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=830f0bf135ebc94cec7f2700171a2850430f76f7
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1326/org/apache/commons/commons-dbcp2/2.3.0/
> 
> These are the Maven artifacts and their hashes
> 
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar.asc
> (SHA1: 61a0593f9e79568a17cdf96a27f35a153661811e)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar
> (SHA1: bbb2876368ecb71f0108af1e09ceeb17b8688176)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar.asc
> (SHA1: 9bd5ef92ff5716ca59afb64c0030d9cd1b08178b)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar
> (SHA1: 92fc4af0d3348c715bd4d78be4fd800a84eca604)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom
> (SHA1: 8baf6f5f0083960ff08b91e173847bf7aaa6ac7c)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-test-sources.jar
> (SHA1: 74bb2457d0b523a8dd7efc2538c705ece5ac53e8)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar.asc
> (SHA1: 6ccd175cbbbe583015db4ad3c62e9fed19b7135d)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar
> (SHA1: fbe38b9ccf3e85b7ea712e56b2d31d9bbc775074)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar.asc
> (SHA1: cc6606a256ec98028a8c357bab47dbacfdd154fe)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-test-sources.jar.asc
> (SHA1: 5b42b57b996266d2b7804d457af094cd00a93a88)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar
> (SHA1: 0ea7fbe2914a272794befb9c98f831cc754b9e04)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom.asc
> (SHA1: e962ee933cfeb18e1b061e3dce5e62487df958d1)
> 
> I have tested this with:
> 
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_172\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> 
> Details of changes since 2.2.0 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/RELEASE-NOTES.txt
> changes-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> 
> Site:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>   (note some *relative* links are broken and the 2.3.0 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   The site contains a CLIRR report but not a JApiCmp report because I could
> not get JApiCmp to work.
> 
> Clirr Report (compared to 2.2.0):
> clirr-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> 
> RAT Report:
> rat-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
> 
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 04:00 UTC 31-March 2010
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> Gary Gregory
> 

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



Re: [commons-release-plugin] Next

2018-05-12 Thread Gary Gregory
On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins  wrote:

>
>
> > On May 10, 2018, at 12:11 PM, Gary Gregory 
> wrote:
> >
> > On Thu, May 10, 2018 at 9:53 AM, Matt Sicker  wrote:
> >
> >> On 10 May 2018 at 09:34, Gary Gregory  wrote:
> >>
> >>> Another item would be to have ONE Maven call instead of SIX for:
> >>>
> >>
> >> It would be great to just do "mvn release:prepare release:perform", fill
> >> out the release candidate version, and then have everything uploaded and
> >> emailed properly. Unfortunately, I'm not familiar enough with maven to
> know
> >> how to automate that sort of thing (in the past, I've usually offloaded
> >> that part to a CI pipeline script of some sort).
> >>
> >
> > Right, in a dream world, there would be a simple one-liner for creating
> an
> > RC and another for promoting an RC to release.
>
> All steps in that direction. I figure tackle the hard bits first, then
> sort the remainders out. :-)
>

I'd like to release collections, text, pool, lang soon, so the better the
plugin, the happier the RM ;-)

I'm not sure how much time I can devote to helping on the plugin but I am
around to discuss and test.

Gary


> >
> > Gary
> >
> >
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


Re: [VOTE] Release Apache Commons DBCP 2.3.0 based on RC1

2018-05-12 Thread Gary Gregory
May I get more reviews please?

Gary

On Tue, May 8, 2018, 18:08 Gary Gregory  wrote:

> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons DBCP 2.2.0 was released, so I would like to release
> Commons DBCP 2.3.0.
>
> Commons DBCP 2.3.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
> 26776)
>
> The tag is here:
>
> https://git1-us-west.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=830f0bf135ebc94cec7f2700171a2850430f76f7
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1326/org/apache/commons/commons-dbcp2/2.3.0/
>
> These are the Maven artifacts and their hashes
>
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar.asc
> (SHA1: 61a0593f9e79568a17cdf96a27f35a153661811e)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.jar
> (SHA1: bbb2876368ecb71f0108af1e09ceeb17b8688176)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar.asc
> (SHA1: 9bd5ef92ff5716ca59afb64c0030d9cd1b08178b)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-tests.jar
> (SHA1: 92fc4af0d3348c715bd4d78be4fd800a84eca604)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom
> (SHA1: 8baf6f5f0083960ff08b91e173847bf7aaa6ac7c)
>
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-test-sources.jar
> (SHA1: 74bb2457d0b523a8dd7efc2538c705ece5ac53e8)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar.asc
> (SHA1: 6ccd175cbbbe583015db4ad3c62e9fed19b7135d)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-sources.jar
> (SHA1: fbe38b9ccf3e85b7ea712e56b2d31d9bbc775074)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar.asc
> (SHA1: cc6606a256ec98028a8c357bab47dbacfdd154fe)
>
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-test-sources.jar.asc
> (SHA1: 5b42b57b996266d2b7804d457af094cd00a93a88)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0-javadoc.jar
> (SHA1: 0ea7fbe2914a272794befb9c98f831cc754b9e04)
> /org/apache/commons/commons-dbcp2/2.3.0/commons-dbcp2-2.3.0.pom.asc
> (SHA1: e962ee933cfeb18e1b061e3dce5e62487df958d1)
>
> I have tested this with:
>
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_172\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Details of changes since 2.2.0 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/RELEASE-NOTES.txt
> changes-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>
> Site:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>   (note some *relative* links are broken and the 2.3.0 directories are
>   not yet created - these will be OK once the site is deployed)
>
>   The site contains a CLIRR report but not a JApiCmp report because I
> could not get JApiCmp to work.
>
> Clirr Report (compared to 2.2.0):
> clirr-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>
> RAT Report:
> rat-report.html in
> https://dist.apache.org/repos/dist/dev/commons/dbcp/site.zip
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 04:00 UTC 31-March 2010
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> Gary Gregory
>