. We just have to fool with the env a bit
> more.
>
> The maven version used must have been updated by someone with access,
> it's not updated automatically.
>
> -Original Message-
> From: Brett Porter [mailto:br...@apache.org]
> Sent: Tuesday, December 23,
Brian E. Fox wrote:
However I don't think it's completely useless
Sure, and I never meant to say that. I appreciate the grid as a great
step towards easier cross-platform testing/debugging.
because the testing and building once maven runs is the same.
As I tried to outline, this doesn't
ore.
The maven version used must have been updated by someone with access,
it's not updated automatically.
-Original Message-
From: Brett Porter [mailto:br...@apache.org]
Sent: Tuesday, December 23, 2008 7:08 PM
To: Maven Developers List
Subject: Re: CI Grid, Windows and Paths
On 24/
On 24/12/2008, at 10:58 AM, Benjamin Bentmann wrote:
Now my question, how do we want to handle that smoothly on the grid?
I see three options:
a) Simply avoid using Maven 2.0.x for affected builds
b) Update the path translation in Maven 2.0.x to match 2.1.x
c) Update the *.bat files to ensur
