Hi,
I started to prepare 0.4.0 release [1] at a RC branch [1]. But then I facea
with an unexpected problem: I have no permissions to write at the Commons'
dist area.
That's because I shouldn't. After graduation, the Commons RDF PPMC wasn't
never voted for full Commons PMC (I think Stian was befor
It's been a while since I looked at that, but from what I can tell, if the
method name needs to be tracked as well as the class name, then the
SecurityManager solution isn't practical at all. Pre Java 9 would need to
use a Throwable no matter what, while Java 9+ can use StackWalker.
On 29 October
On Oct 29, 2017 02:21, "Pascal Schumacher" wrote:
Am 29.10.2017 um 09:09 schrieb Mark Thomas:
> On 29 October 2017 03:54:40 GMT+00:00, "Bruno P. Kinoshita" <
> brunodepau...@yahoo.com.br.INVALID> wrote:
>
>> Hi Gary,
>>
>> Started the tests in Maven command line, found which tests failed.
>> Exe
Github user coveralls commented on the issue:
https://github.com/apache/commons-pool/pull/3
[](https://coveralls.io/builds/13939784)
Coverage increased (+0.03%) to 85.291% when pulling
**cdc2992de32e2b6d9e7cdb
Github user coveralls commented on the issue:
https://github.com/apache/commons-pool/pull/3
[](https://coveralls.io/builds/13939746)
Coverage decreased (-0.1%) to 85.121% when pulling
**cdc2992de32e2b6d9e7cdb0
Thanks for looking into it Mark. And thanks Pascal for going through the
changes set.
Fix for checkstyles from the ps here:
https://github.com/apache/commons-pool/pull/3 but happy to postpone merging it
or rebase it later in case it makes it simpler to review the changes and/or
modify anything
GitHub user kinow opened a pull request:
https://github.com/apache/commons-pool/pull/3
Fix checkstyle errors
The RAT report was enabled and configured for build, but not for reporting.
The licence header was being verified by both, but inconsistently. Checkstyle
complained about sp
Am 29.10.2017 um 09:09 schrieb Mark Thomas:
On 29 October 2017 03:54:40 GMT+00:00, "Bruno P. Kinoshita"
wrote:
Hi Gary,
Started the tests in Maven command line, found which tests failed.
Executed the tests in Eclipse, found which class was related to the
failure. Then did a diff between both
On 29 October 2017 03:54:40 GMT+00:00, "Bruno P. Kinoshita"
wrote:
>Hi Gary,
>
>Started the tests in Maven command line, found which tests failed.
>Executed the tests in Eclipse, found which class was related to the
>failure. Then did a diff between both tags.
>
>git diff POOL_2_4_2 POOL_2.4.3-RC
