ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From buzzterrier <>
Subject RE: Configurations really hard to understand
Date Mon, 02 Jun 2008 19:29:46 GMT

Thx Ruel,

I created a "runtime" conf on the servlet-api dependency on my coreTools
api. I then added coreTools api as a dependency in my web app, but gave it a
"compile" conf. Since the web app was using a "compile" configuration, I
thought that it would ignore the "runtime" dependency on coreTools api.

for example, here is the coreTools api:

<ivy-module version="1.0">
    <info organisation="" module="coreTools"/>
	<configurations defaultconfmapping="runtime->runtime(*)">
	  <conf name="runtime" description="Run Time dependencies"/>
        <dependency org="javax.servlet" name="servlet-api" rev="2.4"

and here is the web app using a compile conf:

<ivy-module version="1.0">
    <info organisation="" module="reports"/>
	<configurations defaultconfmapping="compile->compile(*)">
	  <conf name="compile" description="Build Time dependencies"/>

    	<dependency name="coreTools" rev="latest.integration" conf="compile"/>


But building the reports module still pulls down servlet-api from coreTools.

[ivy:retrieve]  confs: [compile]
[ivy:retrieve]  found;10 in projects
[ivy:retrieve]  [10];latest.integration
[ivy:retrieve]  found javax.servlet#servlet-api;2.4 in libraries

ruel loehr wrote:
> Yes,  I struggled with it too at first.
> In my main project, I usually publish a directory config called runtime
> which just has the absolute necessary runtime dependencies.
> Then for any project which consumes my original one, I define a compile
> configuration which "eat" the runtime one.
> conf="compile->runtime"

View this message in context:
Sent from the ivy-user mailing list archive at

View raw message