ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Yates (JIRA)" <>
Subject [jira] [Commented] (IVY-1371) Incorrect artifact resolution when using nested <conf> elements
Date Sat, 18 Aug 2012 22:43:38 GMT


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?


  <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'/>


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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message