...
Property Collector Namespaces may seem a bit redundant or verbose but they serve an important purpose. Each Action and Repository which use property collectors also define a namespace pattern that is used to determine which property collectors it's interested in. When you create a property collector and give it a namespace which matches the pattern in an Action/Repository, it will show up in the "Using" list of that Action/Repository.
The table tables below shows show the patterns for each Action/Repository and Namespace examples which show up in the 'Using' drop down list of Actions/Repositories.
Note: Patterns are case insensitive.
...
| Plugin | Pattern | Namespace Examples |
|---|---|---|
| Accurev | ^accurev\..* | Accurev.1.88 Accurev.222 accurev.testing |
| File System | ^Robocopy.* | Robocopy.1.33 Robocopy44 robocopy.fixed |
| Bazaar | ^bazaar\..* | Bazaar.2.4 Bazaar.1 bazaar-old |
Git | ^git\..* | Git.1.6 Git.9 git.newest |
| Mercurial | ^mercurial\..* | Mercurial.9.4 Mercurial.Latest mercurial.2 |
| Perforce | ^perforce\..* | Perforce.3.6 Perforce.old perforce.1 |
| Subversion | ^subversion\..* | Subversion.9.77 Subversion.newest subversion.1 |
| SurroundSCM | ^surroundscm\..* | SurroundSCM.1.2 SurroundSCM.testing surroundscm.9 |
| Vault | ^vault\..* | Vault.4.9 Vault.WIN vault.8 |
The picture below shows a Powershell property collector being created. Notice how the namespace value matches the powershell pattern in the Actions table above.
The next picture shows the property collector that was just created in the "Using" list of the PowerShell Action.
