Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.2 final
-
Fix Version/s: 1.2.1
-
Component/s: None
-
Labels:None
Description
Dependency exclusions can be specified via the DSL but are ignored if specified in the POM. I believe that Ivy 2.0.0 is parsing out this information and returning it to Grails but its not making it through to resolution.
A related bug is that if the dependencies are specified in a parent POM, they will also not be processed. In this case, it may be an issue with Ivy which may be addressed in 2.1.0 (see http://issues.apache.org/jira/browse/IVY-974).
Assuming that you don't want to include libraries and have a need to support Maven, you need to replicate the dependencies in both the POM and the DSL. This therefore appears to be a blocker for production use of the POM to specify dependencies. The need to replicate the dependencies in each leaf POM is not optimal but can be worked around but not the exclusions.
please attach an example that reproduces the problem