I think I recall now that it was holding off for the ever-expectant "1.0" to
manage compatibility expectations - but I don't think 2.0.11 can still
correctly upgrade wagons anyway.
IMO, just do it. :)
On 24/05/2011, at 3:16 AM, Stephen Connolly wrote:
> if the fix targets 2.2.x+ then that's al
if the fix targets 2.2.x+ then that's all 1.5+
if the fix targets 2.0.x+ then that has to remain 1.4+
Our officially supported version is 3.0.3 and 2.2.1, with 2.0.x being
an also ran.
If you take care to create the branch prior to the switch then AFAIK
it's all Nike (Just Do It(tm))
On 23 May 2
#x27;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.
> Date: Mon, 23 May 2011 17:59:18 +0100
> From: strub...@yahoo.de
> Subject: upgrading
Hi folks!
Is there any reason why we still stick with jdk-1.4 in lots of our sub projects?
Even java5 is already dead, dead, dead.. [1]
I would like to upgrade wagon to java5 at least to be able to run with
junit-4.8.2 which is required for our wagon TCK (which is relying on
annotations and in
