[
https://issues.apache.org/jira/browse/IVY-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181995#comment-16181995
]
Gintas Grigelionis edited comment on IVY-1420 at 10/9/17 8:40 PM:
------------------------------------------------------------------
configurations and dependencies have the same attributes at least since 1.4
according to schema.
Thus, attributes inherited through extend of configurations are set on both
elements (unless configurations have include elements, see below).
include works differently, because attributes are read after configurations
were written.
The way Ivy files are parsed currently, attributes inherited through include
are set on dependencies.
The question is, would it suffice to document current behaviour (somewhat
non-obvious regarding the behaviour of include) or whether Ivy file updater
should be rewritten to cache configurations and publications until the
attributes of dependencies are parsed...
was (Author: gintas):
configurations and dependencies have the same attributes at least since 1.4
according to schema.
Thus, attributes inherited through extend of configurations are set on both
elements (unless configurations have include elements, see below).
include works differently, because attributes are read after configurations
were written.
The way Ivy files are parsed currently, attributes inherited through include
are set on dependencies.
> defaultconfmapping on <configurations/> element is not written to delivered
> ivy file
> ------------------------------------------------------------------------------------
>
> Key: IVY-1420
> URL: https://issues.apache.org/jira/browse/IVY-1420
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3.0
> Reporter: Willem Verstraeten
> Assignee: Gintas Grigelionis
> Fix For: master
>
> Attachments: inherit_default_configuration_mappings.patch
>
>
> When you use the <extends/> element to include the configurations of a parent
> module, the defaultconfmapping described in the <configurations/> element of
> the parent is not present in the delivered ivy file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
