[
https://issues.apache.org/jira/browse/IVY-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437404#comment-13437404
]
Maarten Coene commented on IVY-1371:
------------------------------------
The documentation says that if no mapped attribute is specified, it will be
mapped to the same configuration as specified with the name attribute. This
doesn't seem to work, so this is a bug. A quick look at the parser shows me
that in some cases (like yours), the <conf> element is completely ignored and
your dependency will receive the '%->default' configuration, which could
explain your observation. I think we can fix this bug in the 2.3.0 release.
Beside this bug, you are requesting a new feature: if the mapped attribute
isn't specified, the value of the defaultconfmapping attribute should be
considered. This is a new feature request, which will probably not make it into
the 2.3.0 release since we are already in the stage of release candidates which
means we don't add new features anymore. In addition, this change of default
value could break existing ivy files, so we have to think about this in more
detail, although I agree that using the defaultconfmapping as default seems
like a good idea.
> 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
