On 5/6/11 10:55 AM, Phil Steitz wrote:
> OK. This is getting annoying (and not just for us). I am not sure
> how exactly we got this fixed for [pool] but a simple way to fix it
> is to change the commons-proper metadata to point to the 1.x
> branch. I think pool was fixed differently, but I don'
OK. This is getting annoying (and not just for us). I am not sure
how exactly we got this fixed for [pool] but a simple way to fix it
is to change the commons-proper metadata to point to the 1.x
branch. I think pool was fixed differently, but I don't no how to
get the dependencies redirected. D
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-dbcp has an issue affecting its community integration.
This issue
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-dbcp has an issue affecting its community integration.
This issue
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-dbcp has an issue affecting its community integration.
This issue
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-dbcp has an issue affecting its community integration.
This issue
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-dbcp has an issue affecting its community integration.
This issue