[jira] [Commented] (IVY-1315) Ant ivy:publish task generates incomplete ivy.xml

["Matthias Toggweiler (JIRA)" <ji...@apache.org>]

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

Matthias Toggweiler commented on IVY-1315:
------------------------------------------

I have the same issue with ivy 2.4.0 and can therefore support this issue. The attributes on an included <configurations> element seem to be respected for resolving the current module, but once the ivy.xml is published (where the <configurations> gets inlined) these attributes are not included, therefore a transitive resolving can give unexpected results.

Our current workaround is to use the "defaultconf" attribute (and the other two) only on the <dependencies> element.

> Ant ivy:publish task generates incomplete ivy.xml
> -------------------------------------------------
>
>                 Key: IVY-1315
>                 URL: https://issues.apache.org/jira/browse/IVY-1315
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.2.0
>         Environment: Windows 7, Ivy 2.2.0 - 20100923230623, 
>            Reporter: Robert McAuliffe
>            Priority: Minor
>
> We have a configurations element in each of our Ivy files that looks like:
> <configurations>
>   <include file="${user.home}/.some_ivy_folder/ivyconfigurations.xml"/>
> </configurations>
> The referenced configurations xml file contains a single configurations element with a 'defaultconf' attribute and a number of 'conf' elements.  A given project will build/test fine, but a dependant project won't work because the ivy.xml file generated by the Ant ivy:publish task does not contain the 'defaultconf' element. This is despite the fact that it correctly contains the imported 'conf' elements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)