Le 25/02/2014 18:43, Gary Gregory a écrit :
> All of the @author tags need to be removed to follow ASF guidelines. And
> no, you do not need 'permission' from the @author to do this ;)
It doesn't *need* to, it's simply discouraged. And I find it really rude
to remove it without asking.
Emmanuel B
Done
However I'm still seeing JMX test warnings; I'll start a new thread
On 25 February 2014 18:02, Gary Gregory wrote:
> @Sebb: Can you please go ahead with these clean ups?
> Thank you,
> Gary
>
> On Tue, Feb 25, 2014 at 12:55 PM, sebb wrote:
>
>> Perhaps update to CP33 ?
>>
>
>> Also org.apa
@Sebb: Can you please go ahead with these clean ups?
Thank you,
Gary
On Tue, Feb 25, 2014 at 12:55 PM, sebb wrote:
> Perhaps update to CP33 ?
>
> Also org.apache.geronimo.modules:geronimo-transaction ... 1.2-beta ->
> 2.2.1 ?
>
> The following plugin updates are available:
> maven-checkstyle-
Just tried "mvn site -Pcobertura -Pjacoco" with CP33 and dropping the
cobertura entries from the DBCP pom.
Both coverage tools seemed to work OK, however there was a test failure:
testRepeatedBorrowAndReturn(org.apache.commons.dbcp2.TestPoolingDriver)
Time elapsed: 0.047 sec <<< ERROR!
java.lan
Perhaps update to CP33 ?
Also org.apache.geronimo.modules:geronimo-transaction ... 1.2-beta -> 2.2.1 ?
The following plugin updates are available:
maven-checkstyle-plugin ... 2.9.1 -> 2.11
maven-pmd-plugin . 2.7.1 -> 3.0.1
org.
All of the @author tags need to be removed to follow ASF guidelines. And
no, you do not need 'permission' from the @author to do this ;)
Gary
On Tue, Feb 25, 2014 at 7:36 AM, Mark Thomas wrote:
> I have, finally, worked my way though the Jira backlog for DBCP. The
> remaining issues are all li
I have, finally, worked my way though the Jira backlog for DBCP. The
remaining issues are all likely to be resolved as WONTFIX.
I will, therefore, be starting to work my way through the release
process later today. I'm not sure when I'll get to the point of creating
the tag and RC. I hope it will