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 ensure M2_HOME is absolute
d) Update MavenCli or similar to fix maven.home
Option c) seems to be as easy as
for %%i in ("%M2_HOME%") do set "M2_HOME=%%~fi"
but I haven't fully tried the patch yet.
+1 for fixing c), especially if it is that simple.
Option c) or d) are my favorites as I personally dislike the grid
env for Windows: it's just unnatural, how many Windows users run
Maven with a unix-style home dir? I see ourselves testing an exotic
environment and chasing issues a regular Windows user would never
face. Hence I believe it's worth to get rid of Hudson anomalies at
the front door.
WDYT?
Agreed here too - can the Windows job be reconfigured to a more
natural location?
Trying to understand correctly - how did the version of Maven switch
from 2.1.0-M1 to 2.0.9 to 2.1.0-M1 again? Was this something you
altered the configuration for, or is it happening based on what was
last built?
- Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
