Bug 51044 - Allow a <propertyset> in an <expandproperties> filter
Summary: Allow a <propertyset> in an <expandproperties> filter
Status: VERIFIED FIXED
Alias: None
Product: Ant
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.8.2
Hardware: All All
: P2 enhancement (vote)
Target Milestone: 1.8.3
Assignee: Ant Notifications List
URL:
Keywords:
: 9481 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-08 09:10 UTC by rich
Modified: 2012-02-08 02:15 UTC (History)
2 users (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rich 2011-04-08 09:10:27 UTC 
I would like to be able to use a <properyset> in an <expandproperties> filter, something like:

<expandproperties>
   <propertyset prefix="foo">
</expandproperties>

This request is similar to 9481 but is more general and flexible.
Comment 1 Matt Benson 2011-04-08 09:17:10 UTC 
Let's abstract this to:  allow user to specify 0..n resourceCollections to the expandproperties filter, of which only PropertyResource elements will influence the filter's operation (propertyset implements ResourceCollection).
Comment 2 Matt Benson 2011-04-08 13:31:36 UTC 
Now that PropertySet can potentially return MappedResources as well as PropertyResources (see http://svn.apache.org/viewvc?view=revision&revision=1090354), using PropertySet at the level of ExpandProperties seems more appropriate after all.
Comment 3 Matt Benson 2011-04-08 16:27:45 UTC 
Committed revision 1090431.
Comment 4 Matt Benson 2011-04-08 16:30:28 UTC 
*** Bug 9481 has been marked as a duplicate of this bug. ***
Comment 5 Jesse Glick 2012-02-08 02:15:45 UTC 
Verified by reporter ("Re: [VOTE] Release Ant 1.8.3").