[ 
https://issues.apache.org/jira/browse/IVY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982652#action_12982652
 ] 

Bart Dooms commented on IVY-1206:
---------------------------------

This can have serious problem.
e.g. 
I use an custom attribute e:subsytem which is used in the ivypattern from my 
resolver: [organisation]/[subsystem]/[module]

Because info extends doesn't user the extra attribute the resolve task doesn't 
find the correct ivy.xml file so no extends at all.


> extra attributes lost from info when ivy file is merged with parent
> -------------------------------------------------------------------
>
>                 Key: IVY-1206
>                 URL: https://issues.apache.org/jira/browse/IVY-1206
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.2.0-RC1, 2.2.0
>         Environment: OS: Ubuntu 10.04
> Java: 1.6.0_20-b02
> Ant: 1.8.0
>            Reporter: Timothy Bingaman
>
> This is in relation to the new "extends" functionality in 2.2.0-rc1.
> When publishing an ivy file that extends a parent ivy file (using the default 
> setting of merging the files), any extra attributes get dropped.  This 
> happens regardless of whether the extra attributes are in the child ivy file, 
> parent ivy file, or both.
> Ideally, all extra attributes would undergo the same merge process as all the 
> standard attributes (allowing them to be inherited from parent to child.  But 
> at the very least, they should not be removed from the child ivy file.
> Example:
> info section in original ivy file
> {noformat}
> <info module="core-util" e:sourceurl="${svn.info.url}" 
> e:sourcerev="${svn.info.wcversion}" e:user="${user.name}">
>     <extends organisation="our-organisation" module="our-parent" 
> revision="latest.integration"/>
> </info>
> {noformat}
> info section in published (merged) ivy file
> {noformat}
> <info organisation="our-organisation" module="core-util" branch="trunk" 
> revision="2.2.51-SNAPSHOT.r30249" status="integration" 
> publication="20100714140802">
>     <!-- <extends organisation="our-organisation" module="our-parent" 
> revision="working@mycomputer"/> -->
>     
>     <!-- description inherited from parent -->
>     <description></description>
> </info>
> {noformat}
> As you can see, all the "e:*" attributes have been dropped.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to