Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC1

[Phil Steitz]

Looking more carefully at the extent of impact, I am -1 (non-binding) on
this change.  I understand what you are trying to do, but a) I don't see
that the solution actually does it (see comments by Michael in PR) and b)
it is going to create a lot of pain for users who have to modify factories,
etc. when in fact many / most of them throw unchecked if any exceptions.  I
would be +1 for removing the throws entirely in 3.0.  It does not make
sense to me to have a "generic" checked exception type assigned at the pool
level.  What the different factory and pool methods throw may be
different.  Even after your change, for example,  borrowObject throws NSE.
You are changing the signature to make it look like if you catch "E"
whatever that is, it will not go bang.  But it will if you have replaced
"Exception" with a checked exception class. You are just replacing
"Exception" with something that looks "cleaner" but is not.  Clients will
either have to ignore it and just instantiate with "Exception" or create a
gratuitous "FooException" to root a hierarchy of their own making (and
separately catch the NSEs) when in fact what they throw now are standard
exceptions.  Remember pool is very widely used so you are asking  *many*
developers to spend time making changes that many will consider a waste of
time. Is the idea that they all just parameterize with "Exception"?  Can
IDEs do that automatically for them?  Please let's get some input from
downstream users before surprising them with this.

Phil

On Mon, Jun 26, 2023 at 3:55 PM Phil Steitz  wrote:

>
>
> On Mon, Jun 26, 2023 at 3:43 PM Gary Gregory 
> wrote:
>
>> Hi Phil,
>>
>> YW and thank you for the review.
>>
>> Yes, you are right that this is about POOL-269. While binary compatibility
>> is preserved 100%, source compatibility is not. This is one of those rare
>> cases where you can't make an omelette without breaking some eggs ;-)
>> Since
>> binary compatibility is preserved, I don't think this is worth going to a
>> new major release.
>>
>
> We should definitely add a *loud* statement in the release notes then and
> directions for how to work around because I am sure a lot of downstream
> builds will fail due to this as DBCP did.  Is there no way that we can
> somehow keep the source compatability?  Pool is widely used and a lot of
> builds will break IIUC what is going on here.
>
> Phil
>
>>
>> I have POOL projects that will benefit (greatly IMO) from cleaner
>> exception
>> handling and avoid having to throw/propagate Exception or catch/rethrow
>> Exception as a domain Exception, and will now instead be able to use
>> domain
>> specific exception for resources being pooled from the get go.
>>
>> I'll obviously adjust DBCP for this as soon as possible (IOW,
>> post-release).
>>
>> For the other items, I will try and reproduce. My tests builds were ok on
>> Windows 10 and macOS latest with Java 8. Maybe by hardware is too slow or
>> too fast compared to yours, hard to say.
>>
>> Gary
>>
>> On Mon, Jun 26, 2023, 16:53 Phil Steitz  wrote:
>>
>> > Hi Gary, First, thanks for doing this.  There are a lot of good fixes in
>> > here.
>> >
>> > I checked the build, sigs et al on a couple of platforms and did not
>> > find anything major except one item.  I will start with the
>> > show-stopper (IMO) and then the other smaller things.
>> >
>> > 1.  I get compilation failure when I try to compile the latest DBCP
>> > release with this code.  I think it may have something to do with
>> > POOL-269.  Here is one example:
>> >
>> > [*ERROR*]
>> >
>> /Users/psteitz/Downloads/commons-dbcp2-2.9.0-src/src/main/java/org/apache/commons/dbcp2/PoolableConnectionFactory.java:[45,70]
>> > wrong number of type arguments; required 2
>> >
>> > This should not happen in a dot release.
>> >
>> > 2. On MacOS 13.4.1, OpenJDK 20.0.1, I got the following test failure
>> > just one time and can't reproduce:
>> >
>> > java.util.concurrent.ExecutionException:
>> > java.lang.NullPointerException: Cannot invoke
>> >
>> >
>> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
>> > because the return value of "java.util.Map.get(Object)" is null
>> >
>> > at
>> > java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
>> > at
>> > java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
>> > at
>> >
>> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$2(TestGenericKeyedObjectPool.java:1056)
>> > ... 71 more
>> > Caused by: java.lang.NullPointerException: Cannot invoke
>> >
>> >
>> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
>> > because the return value of "java.util.Map.get(Object)" is null
>> > at
>> >
>> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addIdleObject(GenericKeyedObjectPool.java:307)
>> > at
>> >
>> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:332)

Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC1

[Phil Steitz]

On Mon, Jun 26, 2023 at 3:43 PM Gary Gregory  wrote:

> Hi Phil,
>
> YW and thank you for the review.
>
> Yes, you are right that this is about POOL-269. While binary compatibility
> is preserved 100%, source compatibility is not. This is one of those rare
> cases where you can't make an omelette without breaking some eggs ;-) Since
> binary compatibility is preserved, I don't think this is worth going to a
> new major release.
>

We should definitely add a *loud* statement in the release notes then and
directions for how to work around because I am sure a lot of downstream
builds will fail due to this as DBCP did.  Is there no way that we can
somehow keep the source compatability?  Pool is widely used and a lot of
builds will break IIUC what is going on here.

Phil

>
> I have POOL projects that will benefit (greatly IMO) from cleaner exception
> handling and avoid having to throw/propagate Exception or catch/rethrow
> Exception as a domain Exception, and will now instead be able to use domain
> specific exception for resources being pooled from the get go.
>
> I'll obviously adjust DBCP for this as soon as possible (IOW,
> post-release).
>
> For the other items, I will try and reproduce. My tests builds were ok on
> Windows 10 and macOS latest with Java 8. Maybe by hardware is too slow or
> too fast compared to yours, hard to say.
>
> Gary
>
> On Mon, Jun 26, 2023, 16:53 Phil Steitz  wrote:
>
> > Hi Gary, First, thanks for doing this.  There are a lot of good fixes in
> > here.
> >
> > I checked the build, sigs et al on a couple of platforms and did not
> > find anything major except one item.  I will start with the
> > show-stopper (IMO) and then the other smaller things.
> >
> > 1.  I get compilation failure when I try to compile the latest DBCP
> > release with this code.  I think it may have something to do with
> > POOL-269.  Here is one example:
> >
> > [*ERROR*]
> >
> /Users/psteitz/Downloads/commons-dbcp2-2.9.0-src/src/main/java/org/apache/commons/dbcp2/PoolableConnectionFactory.java:[45,70]
> > wrong number of type arguments; required 2
> >
> > This should not happen in a dot release.
> >
> > 2. On MacOS 13.4.1, OpenJDK 20.0.1, I got the following test failure
> > just one time and can't reproduce:
> >
> > java.util.concurrent.ExecutionException:
> > java.lang.NullPointerException: Cannot invoke
> >
> >
> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
> > because the return value of "java.util.Map.get(Object)" is null
> >
> > at
> > java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> > at
> > java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> > at
> >
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$2(TestGenericKeyedObjectPool.java:1056)
> > ... 71 more
> > Caused by: java.lang.NullPointerException: Cannot invoke
> >
> >
> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
> > because the return value of "java.util.Map.get(Object)" is null
> > at
> >
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addIdleObject(GenericKeyedObjectPool.java:307)
> > at
> >
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:332)
> > at
> >
> org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:136)
> > at
> >
> org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:113)
> > at
> >
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$0(TestGenericKeyedObjectPool.java:1036)
> > at
> >
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
> > at
> > java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> > at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> > at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> > at java.base/java.lang.Thread.run(Thread.java:1623)
> >
> > This one is driving me crazy because the NPE should not be possible
> > due to key registration guarding.  I will keep digging on this.
> >
> > 3.
> >
> > I see this one on every run, both config above and Ubuntu 20.0.4 /
> > OpenJDK 11.0.19
> >
> > Exception in thread "Thread-1305" org.opentest4j.AssertionFailedError
> >
> > at
> > org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:34)
> >
> > at org.junit.jupiter.api.Assertions.fail(Assertions.java:116)
> >
> > at
> >
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testClearUnblocksWaiters$3(TestGenericKeyedObjectPool.java:1237)
> >
> > at java.base/java.lang.Thread.run(Thread.java:1623)
> >
> > The test that causes it doesn't fail because it happens in a thread
> > that the test spawns and the test does not 

Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC1

[Gary Gregory]

Hi Phil,

YW and thank you for the review.

Yes, you are right that this is about POOL-269. While binary compatibility
is preserved 100%, source compatibility is not. This is one of those rare
cases where you can't make an omelette without breaking some eggs ;-) Since
binary compatibility is preserved, I don't think this is worth going to a
new major release.

I have POOL projects that will benefit (greatly IMO) from cleaner exception
handling and avoid having to throw/propagate Exception or catch/rethrow
Exception as a domain Exception, and will now instead be able to use domain
specific exception for resources being pooled from the get go.

I'll obviously adjust DBCP for this as soon as possible (IOW, post-release).

For the other items, I will try and reproduce. My tests builds were ok on
Windows 10 and macOS latest with Java 8. Maybe by hardware is too slow or
too fast compared to yours, hard to say.

Gary

On Mon, Jun 26, 2023, 16:53 Phil Steitz  wrote:

> Hi Gary, First, thanks for doing this.  There are a lot of good fixes in
> here.
>
> I checked the build, sigs et al on a couple of platforms and did not
> find anything major except one item.  I will start with the
> show-stopper (IMO) and then the other smaller things.
>
> 1.  I get compilation failure when I try to compile the latest DBCP
> release with this code.  I think it may have something to do with
> POOL-269.  Here is one example:
>
> [*ERROR*]
> /Users/psteitz/Downloads/commons-dbcp2-2.9.0-src/src/main/java/org/apache/commons/dbcp2/PoolableConnectionFactory.java:[45,70]
> wrong number of type arguments; required 2
>
> This should not happen in a dot release.
>
> 2. On MacOS 13.4.1, OpenJDK 20.0.1, I got the following test failure
> just one time and can't reproduce:
>
> java.util.concurrent.ExecutionException:
> java.lang.NullPointerException: Cannot invoke
>
> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
> because the return value of "java.util.Map.get(Object)" is null
>
> at
> java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at
> java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$2(TestGenericKeyedObjectPool.java:1056)
> ... 71 more
> Caused by: java.lang.NullPointerException: Cannot invoke
>
> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
> because the return value of "java.util.Map.get(Object)" is null
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addIdleObject(GenericKeyedObjectPool.java:307)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:332)
> at
> org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:136)
> at
> org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:113)
> at
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$0(TestGenericKeyedObjectPool.java:1036)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
> at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> at java.base/java.lang.Thread.run(Thread.java:1623)
>
> This one is driving me crazy because the NPE should not be possible
> due to key registration guarding.  I will keep digging on this.
>
> 3.
>
> I see this one on every run, both config above and Ubuntu 20.0.4 /
> OpenJDK 11.0.19
>
> Exception in thread "Thread-1305" org.opentest4j.AssertionFailedError
>
> at
> org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:34)
>
> at org.junit.jupiter.api.Assertions.fail(Assertions.java:116)
>
> at
> org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testClearUnblocksWaiters$3(TestGenericKeyedObjectPool.java:1237)
>
> at java.base/java.lang.Thread.run(Thread.java:1623)
>
> The test that causes it doesn't fail because it happens in a thread
> that the test spawns and the test does not wait for the threads it
> starts to finish.  Digging into it, I realize this is my sloppiness as
> I committed this test case.  I will make a PR to fix it.  I don't
> think that it indicates a bug.
>
> 4. I forgot to add since tag on the new version of GKOP clear that
> adds reuseCapacity parm.  Will fix in the same PR.
>
> 5. Small nit.  There is a vestigal paragraph in the release notes
> template that I think should be dropped:
>
>
> No client code changes are required to migrate from versions 2.0-2.3
> to version 2.4.3.
>
> Users of version 1.x should consult the migration guide on the Commons
> Pool web site.
>
> Phil

Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC1

[Phil Steitz]

Hi Gary, First, thanks for doing this.  There are a lot of good fixes in here.

I checked the build, sigs et al on a couple of platforms and did not
find anything major except one item.  I will start with the
show-stopper (IMO) and then the other smaller things.

1.  I get compilation failure when I try to compile the latest DBCP
release with this code.  I think it may have something to do with
POOL-269.  Here is one example:

[*ERROR*] 
/Users/psteitz/Downloads/commons-dbcp2-2.9.0-src/src/main/java/org/apache/commons/dbcp2/PoolableConnectionFactory.java:[45,70]
wrong number of type arguments; required 2

This should not happen in a dot release.

2. On MacOS 13.4.1, OpenJDK 20.0.1, I got the following test failure
just one time and can't reproduce:

java.util.concurrent.ExecutionException:
java.lang.NullPointerException: Cannot invoke
"org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
because the return value of "java.util.Map.get(Object)" is null

at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at 
org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$2(TestGenericKeyedObjectPool.java:1056)
... 71 more
Caused by: java.lang.NullPointerException: Cannot invoke
"org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getIdleObjects()"
because the return value of "java.util.Map.get(Object)" is null
at 
org.apache.commons.pool2.impl.GenericKeyedObjectPool.addIdleObject(GenericKeyedObjectPool.java:307)
at 
org.apache.commons.pool2.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:332)
at 
org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:136)
at 
org.apache.commons.pool2.KeyedObjectPool.addObjects(KeyedObjectPool.java:113)
at 
org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testConcurrentBorrowAndClear$0(TestGenericKeyedObjectPool.java:1036)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)

This one is driving me crazy because the NPE should not be possible
due to key registration guarding.  I will keep digging on this.

3.

I see this one on every run, both config above and Ubuntu 20.0.4 /
OpenJDK 11.0.19

Exception in thread "Thread-1305" org.opentest4j.AssertionFailedError

at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:34)

at org.junit.jupiter.api.Assertions.fail(Assertions.java:116)

at 
org.apache.commons.pool2.impl.TestGenericKeyedObjectPool.lambda$testClearUnblocksWaiters$3(TestGenericKeyedObjectPool.java:1237)

at java.base/java.lang.Thread.run(Thread.java:1623)

The test that causes it doesn't fail because it happens in a thread
that the test spawns and the test does not wait for the threads it
starts to finish.  Digging into it, I realize this is my sloppiness as
I committed this test case.  I will make a PR to fix it.  I don't
think that it indicates a bug.

4. I forgot to add since tag on the new version of GKOP clear that
adds reuseCapacity parm.  Will fix in the same PR.

5. Small nit.  There is a vestigal paragraph in the release notes
template that I think should be dropped:


No client code changes are required to migrate from versions 2.0-2.3
to version 2.4.3.

Users of version 1.x should consult the migration guide on the Commons
Pool web site.

Phil

On Sat, Jun 24, 2023 at 6:27 PM Gary Gregory  wrote:

> We have fixed quite a few bugs and added some enhancements since
> Apache Commons Pool 2.11.1 was released, so I would like to release
> Apache Commons Pool 2.12.0.
>
> Apache Commons Pool 2.12.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1
> (svn revision 62626)
>
> The Git tag commons-pool-2.12.0-RC1 commit for this RC is
> e5dae53e0ce1211b40680e7dccf601c3c3897378 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=e5dae53e0ce1211b40680e7dccf601c3c3897378
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-pool.git
> --branch 
> commons-pool-2.12.0-RC1 commons-pool-2.12.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1640/org/apache/commons/commons-pool2/2.12.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sat Jun 24 21:12:18 EDT 2023
>
> 

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.13 based on RC1

[Rob Tompkins]

+1

> On Jun 25, 2023, at 11:30 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Build Plugin Maven Mojo 1.12 was released, so I would like to
> release Apache Commons Build Plugin Maven Mojo 1.13.
> 
> Apache Commons Build Plugin Maven Mojo 1.13 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1
> (svn revision 62637)
> 
> The Git tag commons-build-plugin-1.13-RC1 commit for this RC is
> 6c99abd8ae378dcfa4154b0ff1787de6b4bff968 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-build-plugin.git;a=commit;h=6c99abd8ae378dcfa4154b0ff1787de6b4bff968
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git
> --branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1641/org/apache/commons/commons-build-plugin/1.13/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jun 25 11:20:14 EDT 2023
> commons-build-plugin-1.13-javadoc.jar=6e9f9b5fed3816149388a325f1adb2fb1596531deb94ab63c306eac3efcda6069328b3718399c7a616e82781bfb01cf24ea33d52a24d6d6497fbe2b5bc07b0ee
> commons-build-plugin-1.13-test-sources.jar=02ebcf44d442fae28042cc5609319813d03cc4cf22dba195c40fd95cb5cc6ea3e5dec077cc809160378a6fe4da8d6ce9bab156f90b1cdcab9d3b3a739d96934e
> commons-build-plugin-1.13-src.tar.gz=b8d91116c8e5994d3b13f59a2b18971132e63b6ced0ff53004f21d45c601c7abd2e7912574f1fd545821f9c2c82ff27eb41417a38795db2448a1621316db44d0
> commons-build-plugin-1.13-bom.xml=91012ce5998e626e71605641020b6a21fdb03c859b423bec40b22d417faf362c315c1c50226fe9be5189cfeca86a9ce618d08b61a8be24b01f08683fd61d9c76
> org.apache.commons_commons-build-plugin-1.13.spdx.json=e967bb2644b460058c5b6d2d9ffa429b6c1f1c3e67cb6d3c06c86ef03054a6401b1d364e737630bf69c2a50174cc40ca4f11d6fb13b5ac7f2a06cd0471ce52b5
> commons-build-plugin-1.13-tests.jar=f6e9d604557354d0da8efe7c1a43f01c636154f280757d009dc7546b75d14653f53379aac8f62225c92f53a4841c0f536be3031b8663efbeb397a9f979ce9411
> commons-build-plugin-1.13-bom.json=90f202a9dc7f6214882f8ae71ac4668b9bacf5e67362bb310b693cefb1fc56b3088e109575ad2decf6bff00f736ec42c7ee10882f48394f824ddbd08709b72df
> commons-build-plugin-1.13-src.zip=e6ef7fe0f581f2d29e8c28dbd272ac52a7f28ea58bd6cfa879fb84650c889dddfb22d1e6f5014b77576b3a96052d37546d616a5f13b5b7517374b215e686e435
> commons-build-plugin-1.13-sources.jar=b94b27a41492ffdfdaf96f182411efcc5ce6ed1582ad76d65b8db7d5fda87421caa148b43ee9f64d464bd05c4b0a18c105453308e500e8d1ce7c373e83bc3790
> 
> I have tested this with:
> 
> mvn -V -Duser.name=$my_apache_id -Prelease -Ptest-deploy -P jacoco -P
> japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 11.0.19, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.12 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/index.html
>(note some *relative* links are broken and the 1.13 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Thank you,
> 
> Gary Gregory,
> Release Manager (using key 86fdc7e2a11262cb)
> 
> For following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, Maven.
> 
> You can validate a release from a release candidate (RC) tag as follows.
> 
> 1) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git
> --branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
> cd commons-build-plugin-1.13-RC1
> 
> 2) Check Apache licenses
> 
> This step is not required if the site includes a RAT report page which
> you then must check.
> 
> mvn apache-rat:check
> 
> 3) 

Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.8.1 based on RC1

[Rob Tompkins]

+1

> On Jun 25, 2023, at 3:13 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs since Apache Commons Release Plugin 1.7 was
> released, so I would like to release Apache Commons Release Plugin
> 1.8.1.
> 
> Apache Commons Release Plugin 1.8.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1
> (svn revision 62638)
> 
> The Git tag commons-release-plugin-1.8.1-RC1 commit for this RC is
> 0de47206a633016ff26422063275f5d7de6650c9 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=0de47206a633016ff26422063275f5d7de6650c9
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
> --branch commons-release-plugin-1.8.1-RC1
> commons-release-plugin-1.8.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1642/org/apache/commons/commons-release-plugin/1.8.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jun 25 15:02:45 EDT 2023
> commons-release-plugin-1.8.1-bin.tar.gz=6867de0615c5ca4ad8f15052e689fd5548725c6dca342ddfe9168910f5f99a845b56a41716fcdf1bde3a8c90965b76351d46eae7fcd8910c63c9b8d9dcf1118b
> org.apache.commons_commons-release-plugin-1.8.1.spdx.json=4274329e50b9bf2a0b82890fd77fb4f2f37f0649be918c03b8d40d8928804e874ed11ca261c82090abb2234fc4fa55ac5a10a769252be2118fd890c605946b2e
> commons-release-plugin-1.8.1-bin.zip=96ee13f0e0f73e4c1981b5e945a2c69a8f7269ba8a5ddbebe1b45919b20ad4b3774021531ffc1d18582646e5e252a202a3c5c88b12edbd9167a7ab4d728716d5
> commons-release-plugin-1.8.1-tests.jar=ac6cf663046c5104dc73e47985ce97dfd100bf744aa889c3030e346f4ea24096632b83b1d36b169da3af8ded6a14f71a52eb93f0147619b22551085ca5c2807f
> commons-release-plugin-1.8.1-test-sources.jar=e71ad8e23016dc0c5c4624452dda87cc7258ecda04c1b38c00f52249a83f1551c159b2018554505760853573c54e3ebe513a50b2d4c427953acc0cf94882d524
> commons-release-plugin-1.8.1-src.tar.gz=26bf9b9045332446aad04792bc8e6a0d641f5d2aaae71f5a339639ff2018dea02e9d46e0cf0d18abe8520c0c924baa6a4cc97f7850859f4a74a0b188cc51e450
> commons-release-plugin-1.8.1-javadoc.jar=60c7afdc296cfe6afb3a5c36a10ad1ec4b4d3ac7fe370c611babef59681e9aaeb268f3d5755bdde8ec2f7fe6c45c46d5f88e54ceb9e053c95c0335a0359b8f75
> commons-release-plugin-1.8.1-src.zip=bbae4dd7ffd360190734a36359a4ad5cd3922e010482e32f7b5ba5789455cae9adb126a64634a1722d6f280d6ab1adea0d1b74ee409ca7719351da2c15076fe1
> commons-release-plugin-1.8.1-bom.xml=c08a3001b8a98fb4d9faacc97be706df53e97e4150a47f8b1866eacdfd7a4de0e371cf144d6dab2d3aef5c096c2139aafa7bb10c350816d89da04a8b67a80a3a
> commons-release-plugin-1.8.1-bom.json=3754e0997788777b15447cf049ef400073052dccbea6dd28a0ac12dd390e19a8f80411514f6e55c90a1368315d0a6c852c47b753a802833f82653e983814e518
> commons-release-plugin-1.8.1-sources.jar=2080248fccd261dd7b8770fe74c331d75b19290cf6bd58fbfd83d82cbbac7249b63fcc753d9332391cdeab4208b5406b64361997efa91ff212e7f454f4a2fac1
> 
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 11.0.19, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.7 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Thank you,
> 
> Gary Gregory,
> Release Manager (using key 86fdc7e2a11262cb)
> 
> For following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, Maven.
> 
> 

Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC1

[Bruno Kinoshita]

   [x] +1 Release these artifacts

Building OK from tag on

Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.7, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-75-generic", arch: "amd64", family:
"unix"

Site reports look good. Only one PMD issue, and it's actually annotated
with NOPMD (maybe on the wrong line of the while-statement?)

Thanks!

Bruno


On Sun, 25 Jun 2023 at 03:27, Gary Gregory  wrote:

> We have fixed quite a few bugs and added some enhancements since
> Apache Commons Pool 2.11.1 was released, so I would like to release
> Apache Commons Pool 2.12.0.
>
> Apache Commons Pool 2.12.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1
> (svn revision 62626)
>
> The Git tag commons-pool-2.12.0-RC1 commit for this RC is
> e5dae53e0ce1211b40680e7dccf601c3c3897378 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=e5dae53e0ce1211b40680e7dccf601c3c3897378
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-pool.git
> --branch 
> commons-pool-2.12.0-RC1 commons-pool-2.12.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1640/org/apache/commons/commons-pool2/2.12.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sat Jun 24 21:12:18 EDT 2023
>
> commons-pool2-2.12.0-bin.tar.gz=e16b3a81c98feae6f9855a9bd2f2226dae51558c6e7bb77ee626e58853420ccc59d0943a594bba27ab7147524eca823cac47484e304ebaf14bd724b96bbffc25
>
> commons-pool2-2.12.0-bin.zip=29339f89a8efaa4ad3efbe656d610b8951be1a2a005ba7cb58ae356660331af9d473e8ada8bcdedd3d765c54d1dcfee8779ccb3902f0220de7e92e3039f95b8d
>
> commons-pool2-2.12.0-bom.json=adb3e197d360dc7f53ab116c8fa8b1699d60560fcf977cae613c4cb493168a130ca8041d4ca475e75386f281688819fa5f5111e4aa937b24390a6de8e779f507
>
> commons-pool2-2.12.0-bom.xml=d964e9ec5ed51c10591093bdd0e174f8eb354a447f710e8c3749100fdbda7456e3922846a7190180e5044fe46e571cbc600aaea1b8f64a37c12c5deaa2f1662a
>
> commons-pool2-2.12.0-javadoc.jar=356891b25f2e0367b74a7c4070c26d3cec7a3e608b6e47205e5ffeface590c9717187cb1fa72ebb4c484adaac2c7634ff1944c88282ba9c6551ab5abb58c87f4
>
> commons-pool2-2.12.0-sources.jar=6d955b437496d7af6f94844010a1df15efc04e2b9c15fadc1001777c54a60433570744605b0625a21adf53f03ce9e339809977384c562ad357a98370749c8ee6
>
> commons-pool2-2.12.0-src.tar.gz=eed0575d8357349c908fe8539db2c8ef23234c306f373d203d3d2d9a4ee1ae51cb6bdb2f86163e2296ac90f67a27c7d8cfde239cdfc8ab4966c6239b63f5984e
>
> commons-pool2-2.12.0-src.zip=d8158fd14ee393a99dd0abcb55448b699182a50e0ea114cd3a2681799c9f5e58161f71a2420d0605d1ea39efb08c31be1f7a38531c169fd2c69cc604458ee184
>
> commons-pool2-2.12.0-test-sources.jar=db4fabab1fae77e5dcf8af35397635738c6296ebc25065be9a73725d6b837179c3973ae3ea531aa40056459f011ff90e3c2ef16ad2fa77114dacaa5709e3bf57
>
> commons-pool2-2.12.0-tests.jar=81af180ba6d2a5ce12064c9cc4eda4bc25d072fef55a3dc7ce48506571d40aceb6636c80202c31eff867eb8fd1971a44e0c2c2979019a1e32f43005d70cf2f5e
>
> org.apache.commons_commons-pool2-2.12.0.spdx.json=ed49a8ca7a776ede454f8765f1bd71b5d6a2da35b8bd46ebe930f663127fbd6f248c27059b417ca578665295113ca56a0f0e6486c92436b7b9af7984e3f111db
>
> I have tested this with:
>
> mvn -V -Duser.name=$my_apache_id
> -Dcommons.release-plugin.version=$commons_release_plugin_version
> -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
>
> using:
>
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 1.8.0_372, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8
> /1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun
>  8 22:22:22 PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
>
> Details of changes since 2.11.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1/site/index.html
> (note some *relative* links are broken and the 2.12.0 directories
> are not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 2.11.1):
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1/site/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC1/site/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This