You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Gintas Grigelionis (JIRA)" <ji...@apache.org> on 2018/01/09 15:55:00 UTC

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

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

Gintas Grigelionis commented on IVY-1315:
-----------------------------------------

Since the behaviour of Ivy is underspecified, I'll use the principle of smallest code change: the attributes are taken into account, but written in dependencies element. The suggested usage/workaround is using extension instead of inclusion; then the attributes are processed early.

> 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
>            Assignee: Gintas Grigelionis
>            Priority: Minor
>
> We have a configurations element in each of our Ivy files that looks like:
> {code:xml}
> <configurations>
>   <include file="${user.home}/.some_ivy_folder/ivyconfigurations.xml"/>
> </configurations>
> {code}
> 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.4.14#64029)