PomModuleDescriptorParser fails with nested profile dependency.
---------------------------------------------------------------
Key: IVY-392
URL: https://issues.apache.org/jira/browse/IVY-392
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 1.4.1
Reporter: William Lyvers
I recently started working with struts 2.0 series. Do the complexity of all
the dependent libraries, I thought it would be a good time to test drive ivy as
well. Unfortunately, it was unable to handle one of the struts 2.0 poms found
at
http://people.apache.org/maven-snapshot-repository/org/apache/struts/struts2-core/2.0.2-SNAPSHOT/struts2-core-2.0.2-SNAPSHOT.pom.
A "no groupId found in pom" message was being displayed when trying to
resolve this pom.
After a little debugging and a small refresher course in SAX(its been a while
since using straight SAX :)), I noticed the PomModuleDescriptorParser was
resetting the instance variable prematurely due to nested dependency elements
under a maven build profile. This must not be a common feature in maven, but I
am by no means a maven expert. Anyway, I will attach the patch I applied to
resolve the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
