weak/Inconsistent handling of settings
--------------------------------------
Key: MANTTASKS-81
URL: http://jira.codehaus.org/browse/MANTTASKS-81
Project: Maven 2.x Ant Tasks
Issue Type: Improvement
Affects Versions: 2.0.7
Reporter: Gerhard Langs
There are some differences between the way that maven itself handles it's
settings, and the way antlib does.
1. Lookup/Load of Settings Files:
- in antlib, I can only specify one settingsFile, like this: <install
file="target/xxx.jar" settingsFile="${gs}">, that means either the global or
the user's one...
- in maven itself, both settings.xml are combined (see
http://maven.apache.org/guides/mini/guide-configuring-maven.html)
It would make life much easier for antlib users to have the same funcitonality
"out of the box", without specifying any settings-file
2. resolving of environment variables in a settings files
(maybe this is a detail or a (negative) consequence of Item 1)
in my global settings file, I have set:
<localRepository>${env.MPA_ROOT}/mavenrepo</localRepository>
- in maven env.MPA_ROOT is resolved to a real directory
- in antlib, it is not.
--
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
