You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gerhard Langs (JIRA)" <ji...@codehaus.org> on 2007/07/25 15:29:13 UTC

[jira] Closed: (MANTTASKS-83) Environment variables are not resolved in settings files

     [ http://jira.codehaus.org/browse/MANTTASKS-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Langs closed MANTTASKS-83.
----------------------------------

    Resolution: Duplicate

hmm, again created a duplicate - but now i'm sure that i really pressed save only once in my browser......


> Environment variables are not resolved in settings files
> --------------------------------------------------------
>
>                 Key: MANTTASKS-83
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-83
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>    Affects Versions: 2.0.7
>            Reporter: Gerhard Langs
>
> (Pulled Item 2 of Issue 80 out to this Issue):
> when i use a settings file in antlib like in 
> 	<property name="gs" value="d:/laglap3/HEAD_CI/tools/maven-2.0.7/conf/settings.xml"/>
> 	<install file="target/xxx.jar" settingsFile="${gs}">
> and, in the settings file,  I use a environment variable, like:
>    <localRepository>${env.MPA_ROOT}/mavenrepo</localRepository>
> then this environment variable MPA_ROOT is NOT resolved to its value.
> Note that this is inconsistent to the behaviour of mvn.bat

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira