[
https://issues.apache.org/jira/browse/IVY-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437095#comment-13437095
]
Maarten Coene commented on IVY-1371:
------------------------------------
ok, it seems a bug.
You can also workaround it by providing a 'mapped' attribute:
<dependency...>
<conf name="transitive" mapped="default" />
</dependency>
You will have to use this 'mapped' attribute anyway, because if Ivy worked as
documented on this, it would give the 'mapped' attribute a default value of
'transitive', so Ivy would try to resolve the 'transitive' configuration of
'spring-core' which doesn't exist.
> Incorrect artifact resolution when using nested <conf> elements
> ---------------------------------------------------------------
>
> Key: IVY-1371
> URL: https://issues.apache.org/jira/browse/IVY-1371
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.0, 2.3.0-RC1
> Reporter: Danny Yates
> Attachments: build.xml, ivy.xml
>
>
> Please see attached build.xml and ivy.xml
> When resolving the 'transitive' conf, Ivy pulls down Mina, which is not in
> that conf, and it additionally pulls down Mina's transitive dependencies even
> though the conf that Mina is in has transitivity turned off.
> If you use the alternative "inline" syntax for conf mapping, this bug doesn't
> happen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
