Thanks for the report: it's unfortunate that we needed to fork the ivy parsing code, and now we're suffering the ramifications. I think the ideal solution is for us to be more tolerant of unexpected content in ivy files, and just consume the details that we actually care about.
I've raised http://issues.gradle.org/browse/GRADLE-2743 to track this issue. On 7 April 2013 18:48, Jeremy Maness <jwman...@gmail.com> wrote: > With Gradle 1.4 and 1.5 (and possibly some earlier versions), the follow > error occurs when resolving dependencies from an Ivy repository if the > module descriptor contains an ivyauthor tag: > > java.text.ParseException: [unknown tag ivyauthor in > http://MY_IVY_REPO/com.google/guava/r09/ivy-guava-r09.xml > > According to the XSD at http://ant.apache.org/ivy/schemas/ivy.xsd and the > documentation at > https://ant.apache.org/ivy/history/2.3.0/ivyfile/info.html, zero or more > ivyauthor tags should be allowed. It looks like the repository element > should also be allowed as a child of the info element too. > > I noticed that > org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser > was originally copied from > http://svn.apache.org/repos/asf/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/xml/XmlModuleDescriptorParser.javabut > doesn't contain > > } else if (state == State.INFO && "ivyauthor".equals(qName)) { > // nothing to do, we don't store this > } else if (state == State.INFO && "repository".equals(qName)) > { > // nothing to do, we don't store this > } > > > in startElement(String uri, String localName, String qName, Attributes > attributes). > > Would it make sense just to add these lines to Gradle's > IvyXmlModuleDescriptorParser? > > > > Thanks, > Jeremy > > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
