ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: Building a meta module
Date Fri, 19 Nov 2010 17:13:33 GMT
It looks like your problem has to do with your specifying this in your
dependent projects:
       <dependency org="jboss" name="jboss-compile-all" rev="4.3.0_CP06">
               <artifact name="jboss-compile-all" type="xml" />

As opposed to this:
       <dependency org="jboss" name="jboss-compile-all" rev="4.3.0_CP06" />

I'm kinda puzzled that Ivy is finding anything for the artifact you're
specifying. It's not like you're secifying a file called
jboss-compile-all.xml on top of the ivy.xml. When you refer to a secondary
file, do you mean the ivy.xml?

As a general best practice, modules should depend on other modules through
confs alone, not through artifacts. Artifacts are an implementation detail;
they're not part of the Ivy module interface.

On Fri, Nov 19, 2010 at 8:41 AM, fnord <> wrote:

> I've been trying to build a meta module without much luck.
> Basically, I built an ivy.xml file listing all of the JBoss dependencies
> necessary to compile stuff for one of our departments and published it to
> our Maven repo. An abbreivated version of it looks like this:
> <ivy-module version="2.0">
>    <info organisation="espn-eng" module="jboss-compile-all"/>
>     <configurations defaultconfmapping="default->default">
>        <conf name="default" />
>     </configurations>
>     <dependencies>
>                  <!-- jboss reference jars -->
>              <dependency org="jboss" name="commons-logging"
> rev="${jboss.reference.version}" conf="default->default"/>
>              <dependency org="jboss" name="jacorb"
> rev="${jboss.reference.version}" conf="default->default"/>
>    </dependencies>
> </ivy-module>
> Then I'm including this as a dependency in the main ivy.xml of a project:
>        <dependency org="jboss" name="jboss-compile-all" rev="4.3.0_CP06">
>                <artifact name="jboss-compile-all" type="xml" />
>        </dependency>
> The problem is that this second file gets pulled into the appropriate
> folder, but it doesn't get resolved. Ivy's not resolving the file, just
> leaving it amongst the other jars.
> Does anyone know how I can get Ivy to resolve this secondary file?
> Thanks,
> fnord
> --
> View this message in context:
> Sent from the ivy-user mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message