I was readily able to reproduce the problem broached below where ivy:buildlist fails on an absolute path to the parent Ivy module. I created this JIRA issue: https://issues.apache.org/jira/browse/IVY-1364 title: "buildlist task chokes on absolute path to parent Ivy module"
I've attached to the issue an isolated, simple test case, including a "control group" test case where a relative path works. As serious as the "buildlist & two parents" problem is, I think this one presents a more prominent obstacle. On Wed, Jun 27, 2012 at 5:13 PM, Mitch Gitman <[email protected]> wrote: > I've created a JIRA issue with an attached test case for this "buildlist > with two parents" problem: > https://issues.apache.org/jira/browse/IVY-1363 > title: "ivy:buildlist task confused by extends feature using two parents" > > It's going to be three weeks until I'd be able to try working on a patch > myself for this. I'm hoping Jean-Louis or someone else might be interested > in taking this on in the meantime. > > I'm also noticing a broader theme of instability surrounding the > extends/parent feature. > > I mention here that earlier I'd started another ivy-user thread "buildlist > task chokes on absolute path to parent Ivy module" concerning Ivy 2.2.0. It > appeared that this problem went away in Ivy 2.3.0-rc1. However, after I > cleared out my Ivy cache and ran ivy:buildlist, I found it inexplicably > failing on an absolute path to a parent in a single Ivy module: > java.text.ParseException: Problem occurred while parsing ivy file: null in > file: … > … > Caused by: java.lang.NullPointerException > at > org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser$Parser.parseOtherIvyFile(XmlModuleDescriptorParser.java:659) > at > org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser$Parser.extendsStarted(XmlModuleDescriptorParser.java:443) > at > org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser$Parser.startElement(XmlModuleDescriptorParser.java:327) > ... 48 more > > And believe me, the file is there. And strangely, as I suggest above, this > failure only shows up after clearing out the Ivy cache. I'm going to try > narrowing down and isolating this problem. It's odd that I should have to > convert only one ivy.xml's extends@location value to a relative path. > > Plus, it's worth noting that I came across another JIRA issue (reported by > someone else) involving buildlist not working as expected with extends: > https://issues.apache.org/jira/browse/IVY-1345 > title: "ivy:buildlist does not order properly modules that extend module > with revision not matching dependencies" > > And just with the extends/parent feature (without buildlist getting > involved), I encountered another problem that I reported yesterday in JIRA: > https://issues.apache.org/jira/browse/IVY-1359 > "ivy.xml extends feature complains about Windows filesystem path" > >
