I've been experimenting with Sigil and ran into the problem that the
SigilParser does not get invoked when I configure Ivy to look for the
ivy.xml in ${basedir}/build/ivy.xml. When it's in the root directory
(i.e. ${basedir}/ivy.xml), everything works just fine.I'm using org.apache.felix.sigil.ivy.resolver.jar built from the Trunk (2011-03-23). The idea behind that is that I'd like to generate ivy.xml from inside my Ant build since there is a certain redundancy with the rest of the build. My ivy.xml basically looks like this: <ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd";> <info organisation="ch.jm" module="ch.jm.db.jdbc.provider.postgresql"/> </ivy-module> My ivysettings.xml: <ivysettings> <properties file="${ivy.settings.dir}/build.properties" override="false"/> <caches defaultCacheDir="${cache.dir}/all"/> <latest-strategies> <latest-time name="mylatest-time"/> </latest-strategies> <settings defaultResolver="sigil" circularDependencyStrategy="error"/> <typedef name="sigil-parser" classname="org.apache.felix.sigil.ivy.SigilParser"/> <typedef name="sigil" classname="org.apache.felix.sigil.ivy.SigilResolver"/> <parsers> <sigil-parser config="${project-root.dir}/sigil-defaults.properties"/> </parsers> <resolvers> <sigil name="sigil" config="${project-root.dir}/sigil-defaults.properties" extractBCP="true" cache="sigil"/> <chain name="project"> <filesystem name="libraries" changingPattern="^.+-dev.*" latest="mylatest-time"> <artifact pattern="${repository.dir}/[organisation]/[module](-[revision]).[ext]" /> <artifact pattern="${repository.dir}/[organisation]/[module](_[revision]).[ext]" /> </filesystem> </chain> </resolvers> <caches> <cache name="sigil" basedir="${cache.dir}" /> </caches> <modules> <module organisation="*" resolver="sigil"/> </modules> </ivysettings> Any idea what could be wrong? Thanks! Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
