weak/Inconsistent handling of settings

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>$

/mavenrepo</localRepository>

• in maven env.MPA_ROOT is resolved to a real directory
• in antlib, it is not.