I am sorry. Looks like some kind soul must have fixed this in Gump
land. I will try changing it back...
Phil
On 3/28/11 7:02 PM, Gump wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.
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-pool has an issue affecting its community integration.
This issue
On 3/27/11 5:06 PM, Konstantin Kolinko wrote:
> 2011/3/28 Phil Steitz :
>> I can't remember how to fix this. The problem is that I changed the jar
>> goal in the Ant build to produce an artifact with the version number in the
>> jar name and I guess Gump expects the old versionless name. Anyone
2011/3/28 Phil Steitz :
> I can't remember how to fix this. The problem is that I changed the jar goal
> in the Ant build to produce an artifact with the version number in the jar
> name and I guess Gump expects the old versionless name. Anyone know how to
> fix this?
Regarding
https://svn.a
I can't remember how to fix this. The problem is that I changed the jar goal
in the Ant build to produce an artifact with the version number in the jar name
and I guess Gump expects the old versionless name. Anyone know how to fix this?
On Mar 27, 2011, at 11:58 AM, Gump wrote:
> To whom i
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-pool 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-pool has an issue affecting its community integration.
This issue
