As explain in the settings references, env variable are used with the prefix
"env", otherwise it's considered as a property. For example, ${env.PATH}
contains the $path environment variable.
Have you try ? I'm not sure that this will fix your problem, but I'm using the
same mirror declaration, but with properties, without problem. A workaround can
be to set a new property in your settings.xml instead to use an env variable.
_______________________________________________________________________________
Christophe DENEUX / Capgemini Sud / Méditerranée
Integration Architect / OW2 PEtALS Comitter
Tel: + 33 4 93 95 55 92 / www.capgemini.com <http://www.capgemini.com/>
Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE
Join the Collaborative Business Experience
_______________________________________________________________________________
Please consider the environment and do not print this email unless absolutely
necessary. Capgemini encourages environmental awareness.
________________________________
De: Nord, James [mailto:jn...@nds.com]
Date: mer. 28/01/2009 13:54
À: users@maven.apache.org
Objet : Release plugin development.
Is the release plugin development ongoing or is this an orphand plugin.
I ask as I and others have a showstopper with it not inheriting the
process environment when doing release:perform.
http://jira.codehaus.org/browse/MRELEASE-406
Or does anyone have any bright ideas how to work around this?
Regards,
/James
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the
intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this
message.
