Bug 28884 - Keep the properties set after <ant> or <antcall>.
Summary: Keep the properties set after <ant> or <antcall>.
Status: REOPENED
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: nightly
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-10 19:13 UTC by Anthony Goubard
Modified: 2020-12-24 16:44 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Goubard 2004-05-10 19:13:07 UTC
At the moment if you have a target that define some properties, the only way to
call it in order to get the values is by using "depends".
 If you use <ant> or <antcall> all properties set in the target are local.
 That's why it would be nice to have a "keepProperties" (or whatever) attribute
to the <ant> and <antcall> task.
  
  Example:
  <antcall target="define-versions" keepProperties="true"/>
 This feature has been discussed on Ant developer mailing list at
http://marc.theaimsgroup.com/?t=108369006500001&r=1&w=2

Note that Dale Anson mailed at
http://marc.theaimsgroup.com/?l=ant-dev&m=108377046631849&w=2
that already several tasks exist in AntContrib and Antelop to perform this feature.
This means that there is a real need for this functionality.
Comment 1 Matt Benson 2004-06-04 18:12:17 UTC
Not only does it mean that there is a real need for this functionality, it also 
means that this functionality is here among us and available via ant-contrib 
and Antelope!  Yay!
Comment 2 J-F Martel 2020-12-24 16:44:46 UTC
- Old bugs
- ProjectHelper Available task, property not set.
- Also Properties Tags inside properties file are not set correctly.
  By alphabet order, set is ok. Also xmlproperties.