History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-449
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Shawn Castrianni
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

2.0.1: Add support for ANT style wildcards in subscriptions

Created: 02/Oct/09 08:39 AM   Updated: 02/Oct/09 08:39 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
Suppose I have a very large hierarchy of configurations and that I have subscribed up at the very top level:

root/lgcbuilds descendants:yes condition: always

Now suppose that this hierarchy contains two versions of every module build, version1 and version2 such they are both children configurations of the module named configuration. I want to be able to subscribe to version1 but NOT version2 without having to subscribe to all the individual modules. That would be a lot of work to maintain. That is why I subscribed at the very top level. So if QB2 had wildcard support in subscriptions, I could add 1 more subscription:

root/lgcbuilds/**/version2 descendants:yes condition: never

Combine this wildcard with the include/exclude feature that you just added, I can do what I need with only 2 subscription lines. Any version1 configuration would only match the first subscription line and I would get the email. Any version2 configuration would match BOTH subscriptions lines but since the second subscription line is more specific, it will act as an exclusion and I won't get the email. ** would match any depth while * would only match 1 level down, just like ANT.

Can you do this? I think that will provide all the power that ANT's include/exclude elements provide in an ANT fileset.

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.