GitHub user sjcorbett opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1063
Api tags support
Supercedes #1039.
@neykov could you review commit 641247f please?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sjcorbett/incubator-brooklyn api-tags-support
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1063.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1063
----
commit d61158860bc5d620024cdbf089a10195df665657
Author: Thomas Bouron <[email protected]>
Date: 2015-11-18T11:32:58Z
Adds support for interfaces tag on catalog items
commit d6eada11975190d44c116bbcc16329aaadae7cca
Author: Sam Corbett <[email protected]>
Date: 2015-11-24T12:10:46Z
Merge branch 'master' into api-tags-support
# Conflicts:
# usage/rest-server/pom.xml
commit 641247fd94b9aca2964aef9e016aabd8951816b7
Author: Sam Corbett <[email protected]>
Date: 2015-11-24T14:38:24Z
Swap catalogue interfaces for catalogue traits
"Interfaces" is too specific for a feature whose purpose is to guide
consumers about the capabilities of a catalogue item and does not lend
itself to the use or addition of other metadata.
Also: InterfacesTag maintains a List<String> rather than List<Class<?>>
and CatalogTransformer.makeTags handles null specs.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
