ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Duffy <char...@dyfis.net>
Subject Unexpected behavior from *->@ (mapping configurations not like-named)
Date Thu, 13 Jun 2013 20:10:08 GMT
Howdy --

I have a wrapper with the following:

<ivy-module version="1.0">
<info organisation="shims.spring" module="spring-web-servlet"
revision="3.0.5.RELEASE"/>
<configurations>
<conf name="default"/><conf name="master"/><conf name="compile"/>
<conf name="provided"/><conf name="runtime"/><conf name="test"/>
<conf name="system"/><conf name="sources"/><conf name="javadoc"/>
<conf name="optional"/>
</configurations>
<publications/>
<dependencies>
<dependency org="spring" name="spring-webmvc" rev="3.0.5.RELEASE"
conf="*->@"/>
</dependencies>
</ivy-module>

My expectation is that this will map local to remote configurations only
for those which are like-named.

However, this expectation doesn't hold up in reality -- for some reason,
the "compile" configuration in the shim gets mapped to the "optional"
configuration in the target:

== resolving dependencies
shims.spring#spring-web-servlet;3.0.5.RELEASE->spring#spring-webmvc;3.0.5.RELEASE
[compile->optional]
== resolving dependencies spring#spring-webmvc;3.0.5.RELEASE->rome#rome;1.0
[optional->master(*)]

Why could this happen? How can I prevent it?

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