I agree that DBCP should support callable statement pooling and the
patch attached to DBCP-204 is a reasonable way to do it. What I am
concerned about is that adding callable statements to the prepared
statement pool with the current implementation may break some
applications by causing them to go
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-fmt-test has an issue affecting its community
integrat
Siegfried Goeschl wrote:
> Hi folks,
>
> I would like to call a vote for releasing commons-email-1.2 based on RC3.
>
> This release candidate has the following changes compared to RC2
>
> +) using an "RC" tag for the M2 release plugin
> +) removed commons-logging testing dependency since it is a
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jaxme contains errors.
The current state of this projec
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-xmlunit contains errors.
The current state of this proj
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
