This is because Java uses it - system property ${user.home}.
I think Maven's current handling is correct as you can override the local
home, plugin dir and repo dir. The only difference should be that
build.properties should also be loaded from MAVEN_HOME_LOCAL - and there is
an issue in JIRA to provide it whenever myself, one of the developers, or
you get the chance to make a patch :)
Cygwin is great for doing a lot of stuff - but java with absolute paths
isn't one of them. The only possibility I see here is to designate all
absolute paths must be specified in ~/build.properties or
$MAVEN_HOME_LOCAL/build.properties, and have the maven shell script running
under cygwin pull it apart, cygpath and absolute paths and pass them on the
command line via -D, but I'm not sure that kind of separation is a good
idea. For now we'll just have to make our absolute paths windows paths :(
Cheers,
Brett
> -----Original Message-----
> From: Joshua Spiewak [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 30 July 2003 6:26 AM
> To: Maven Users List
> Subject: Re: couple of questions
>
>
> Thanks Siegfried,
>
> I think what I found unintuitive was that Maven used
> %USERPROFILE% (which
> is set to c:\Documents and Settings\Joshua) instead of %HOME%
> (which is set
> to c:\jss). Granted, on Windows %USERPROFILE% is set by the
> system, and
> %HOME% is set by me. If it is going to use %USERPROFILE%,
> shouldn't the
> Application Data sub directory be used too? Could Maven
> check if %HOME% is
> set and use that directory first? Setting %MAVEN_LOCAL_HOME%
> takes care of
> the repository and plugin directories (assuming I want them
> in the same
> place), but does it also cause Maven to look for
> project.properties and
> build.properties in that directory, or am I stuck putting them in
> %USERPROFILE% (which, in case you haven't already figured
> out, I would
> prefer not to do)?
>
> -- Josh
>
