Github user tbouron commented on the issue:
https://github.com/apache/brooklyn-server/pull/485
@geomacy @ahgittin Rebased on the latest master, the build error is gone
(still need to [remove line
63](https://github.com/tbouron/brooklyn-library/blob/d7bf1595127dc96cd63bc845084fd44bad94df94/software/webapp/pom.xml#L63)
though)
Retested on a clean distribution with no persisted state. Create a ZIP with
the following bom:
```
brooklyn.catalog:
symbolicName: test
version: 0.1.0
items:
- id: entity-1
itemType: entity
name: Entity 1
item:
type:
org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
- id: entity-2
itemType: entity
name: Entity 2
item:
type:
org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
```
This fails because of the symbolicName inheritance: both `entity-1` and
`entity-2` have the same `symbolicName` therefore it needs to be overridden on
each item. Not an issue per se, but the error is quite confusing at first:
```
Updating existing catalog entries is forbidden: test:0.1.0. Use forceUpdate
argument to override.
```
I was also wondering why we are introducing the field `symbolicName`?
Effectively, that's the same as the `id` (which internally is referenced as...
`symbolicName`) From a user perspective, it would be easier to require `id` and
most of the blueprints do declare `id`s for each items. WDYT?
---
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.
---
