ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (IVY-904) support ant properties propagation to ant build with ant-build trigger
Date Fri, 12 Sep 2008 16:57:46 GMT

     [ https://issues.apache.org/jira/browse/IVY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xavier Hanin updated IVY-904:
-----------------------------

    Issue Type: Improvement  (was: Bug)
       Summary: support ant properties propagation to ant build with ant-build trigger  (was:
ant properties are not propogated to ant build with ant-build trigger)

Indeed, I don't think it's a bug but a change request. Both propagation should be supported,
either with a list of propagated properties, or with an inheritAll or sg.

> support ant properties propagation to ant build with ant-build trigger
> ----------------------------------------------------------------------
>
>                 Key: IVY-904
>                 URL: https://issues.apache.org/jira/browse/IVY-904
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>    Affects Versions: 2.0-RC1
>            Reporter: Steve Benigan
>             Fix For: 2.0-RC1
>
>
> An ant-build trigger calls a target in an ant build file but does not propogate properties
to the ant build.
> ant-call does propogate them - well I'm not sure it's doing anything special but b/c
it's calling a target within the current ant build they are propogated by the nature of ant.
> If possible, some ivy properties should be propogated such as the ivy.cache.dir.${settingsRef}
properties as well as all of the other properties set in the current build due to settings,
resolve, etc.  Otherwise, the ant-build trigger is limited in what it can do based on the
context in which it was called.
> The workaround is to use ant-call and then within the called target use "ant" task to
call the desired target in an external ant file.  This is not ideal since it means this target
needs to be in every build file or at least in an imported build file.
> PS This may be a Change Request rather than an actual bug.

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


Mime
View raw message