ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] Created: (IVY-818) Ivy ibiblio resolver chokes on variables while checking descriptor consistency
Date Sun, 18 May 2008 17:00:55 GMT
Ivy ibiblio resolver chokes on variables while checking descriptor consistency

                 Key: IVY-818
             Project: Ivy
          Issue Type: Bug
          Components: Maven Compatibility
    Affects Versions: 2.0-RC1
         Environment: Ubuntu 8.04, ivy svn rev: 657553
            Reporter: Robert Newson

The ibiblio resolver in trunk has a new facility for parsing maven-metadata.xml in order to
find the latest snapshots. Unfortunately it doesn't work if the version numbers in the poms
are variables, that is, our pom's have ${subproject-version} in them.

When encountering these, Ivy throws this;

java.text.ParseException: inconsistent module descriptor file found in '<removed>/1.2.0-RQA2-20080518.055623-736.pom':
bad revision: expected='1.2.0-RQA2-SNAPSHOT' found='${subproject-version}'; 
	at org.apache.ivy.plugins.resolver.BasicResolver.checkDescriptorConsistency(
	at org.apache.ivy.plugins.resolver.BasicResolver.getDependency(
	at org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(
	at org.apache.ivy.plugins.resolver.ChainResolver.getDependency(
	at org.apache.ivy.core.resolve.IvyNode.loadData(
	at org.apache.ivy.core.resolve.VisitNode.loadData(
	at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
	at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(
	at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
	at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(
	at org.apache.ivy.core.resolve.ResolveEngine.resolve(
	at org.apache.ivy.core.resolve.ResolveEngine.resolve(
	at org.apache.ivy.Ivy.resolve(
	at org.apache.ivy.ant.IvyResolve.doExecute(
	at org.apache.ivy.ant.IvyTask.execute(

It seems Ivy verifies that the pom matches the metadata file, laudable in itself, but doesn't
know that ${subproject-version} expands to the expected value. Setting that as a property
did not help.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message