You could try to change your dependency into: "* -> #" Probably the configurations in the ivy.xml file of the "spring-webmvc" module gives more information about why ivy takes the configuration "optional" from spring-webmvc. It may be caused by one configuration extending the other.
Marc Charles Duffy wrote > 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? -- View this message in context: http://apache-ivy.996301.n3.nabble.com/Unexpected-behavior-from-mapping-configurations-not-like-named-tp9491p9492.html Sent from the ivy-user mailing list archive at Nabble.com.
