Sébastien Lesaint
added a comment - 26/Jan/09 10:41 AM I have the same issue, on the same version (beta-8).
I am using maven 2.1-M1.
When invoking goal release:perform, the build fails because the file "$
{user.home}
/.ssh/id_dsa" can not be resolved.
This files stores the ssh private key used to upload the release to the remote nexus repository via scp.
It looks like variable $user.home is not passed on to the forked process.

as you've identified, this was related to the documented Maven change.

You should use $

{env.*}

if you require an environment variable. However, you might better consider using it as a property, in which case you'd set it with MAVEN_OPTS="-DsomeProperty=someValue" instead of using an env. variable.

Brett Porter
added a comment - 17/Sep/10 10:30 PM as you've identified, this was related to the documented Maven change.
You should use $
{env.*}
if you require an environment variable. However, you might better consider using it as a property, in which case you'd set it with MAVEN_OPTS="-DsomeProperty=someValue" instead of using an env. variable.

I tried this with Maven 2.0.10 + 2.0-beta-8; 2.0.10 + 2.0; 3.0-RC3 + 2.0 - no problems on any of them.

I put your settings.xml into ~/.m2, removed the local repository, and ran the command you gave against the POM. I had to modify the settings to user /internal instead of /central as I'm using Archiva, but the env var was used. In the POM I used a different SVN repository in the SCM element and I changed the deployment URL to $

{env.proxyURL}

/test which worked for deployment too.

There's a possibility this is Windows specific, so I'll have to try it there. Have you tried with more recent versions of Maven and/or the release plugin?

Brett Porter
added a comment - 29/Sep/10 10:03 AM I tried this with Maven 2.0.10 + 2.0-beta-8; 2.0.10 + 2.0; 3.0-RC3 + 2.0 - no problems on any of them.
I put your settings.xml into ~/.m2, removed the local repository, and ran the command you gave against the POM. I had to modify the settings to user /internal instead of /central as I'm using Archiva, but the env var was used. In the POM I used a different SVN repository in the SCM element and I changed the deployment URL to $
{env.proxyURL}
/test which worked for deployment too.
There's a possibility this is Windows specific, so I'll have to try it there. Have you tried with more recent versions of Maven and/or the release plugin?