On 2013-05-21, Adam R. B. Jack wrote:
> I hesitate to reply since I've not contributed in quite some time (and
> yes, that is some *significant* British understatement. ;-)
But your input is still appreciated, don't worry.
> That said, the fact that the burden of metadata maintenance has been
>
à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: Re: Where to go with Gump?
> From
Stefan et al,
I hesitate to reply since I've not contributed in quite some time (and yes,
that is some *significant* British understatement. ;-)
As somebody who found them self sucked away from Gump, I want to express my
appreciation (and admiration) for all the Gump efforts over the years. The
On 2013-05-19, Sander Temme wrote:
> Yes, this makes it seem that we are performing a thankless task.
> Perhaps the right question to ask is who here at the Gump PMC is using
> its facilities to good effect, since we constitute the minimum viable
> community to keep it going.
It's not easy for me
Hi Martin,
I'm not sure I fully understand what you are trying to say.
On 2013-05-20, Martin Gainty wrote:
> Am i the only advocate to converting gump to java?
Gump used to be written in a mix of Java, XSLT and bash. It has been
reimplemented in Python - partly in the hope to attract more deve
ur le contenu fourni.
> From: bode...@apache.org
> To: general@gump.apache.org
> Subject: Where to go with Gump?
> Date: Sun, 19 May 2013 17:22:43 +0200
>
> Hi,
>
> since about christmas last year we had reliability problems with the mvn
> repo proxy. Those problems seem to ha
On May 19, 2013, at 8:22 AM, Stefan Bodewig wrote:
> In January I turned off nagging and nobody ever asked why the nag mails
> stopped. I saw Sebb mention it on Commons' dev list but not because
> anybody had asked for it. Even the Ant folks (including myself) who
> used to watch Gump closely
Hi,
since about christmas last year we had reliability problems with the mvn
repo proxy. Those problems seem to have gone by now. I've been told
Maven Central is using a CDN and some of the nodes had some problems for
a while, so this may explain why it started to work again. Anyway.
In January
