[
https://issues.apache.org/jira/browse/IVY-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437428#comment-13437428
]
Danny Yates commented on IVY-1371:
----------------------------------
Thanks Maarten.
My understanding was that break an inline conf mapping into <conf> elements was
essentially the same as splitting on ';', and then getting the name and mapped
attrs was the same as splitting on '->'. Does that make sense?
So
<dependency conf='a->b;c;d->e' ... />
would be the same as
<dependency ...>
<conf name='a' mapped='b'/>
<conf name='c'>
<conf name='d' mapped='e'/>
No?
But in the former case the defaultconfmapping would get applied to conf 'c' but
it wouldn't in the latter?
> 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
