Github user geomacy commented on the issue:
https://github.com/apache/brooklyn-server/pull/485
I'd have thought there should not be a clash in the above example - from
Alex's email
[here](https://lists.apache.org/thread.html/ca13cfbc334725a6865bdb9e02a97d1a72af98fcdf04f5a58e32038c@%3Cdev.brooklyn.apache.org%3E)
the idea is
> That is, the fields symbolic-name and version are _required_ under the
> `brooklyn.catalog` when POSTing a ZIP to the catalog endpoint, and are
> used to define the bundle. The version (and icon, etc) are then
> inherited by default by items defined therein. If the ZIP is a JAR
> which contains a MANIFEST.MF, the bundle information (symbolic name and
> version) must match exactly.
my understanding here was that the symbolicName wasn't involved in the
definition of entity-1 and 2, just in the naming of the bundle?
---
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.
---
