Maven 2.x Ant Tasks

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 2.0.8
• Component/s: None
• Labels:

  None

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.

• Assignee:

  Herve Boutemy

  Reporter:

  Gerhard Langs

• Created:

  25/Jul/07 8:06 AM

  Updated:

  11/Nov/07 7:26 AM

  Resolved:

  11/Nov/07 7:26 AM