Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/867
Re the last problem, catalog being persisted, I think I'm good with option
(1). I was leery of using something that might have collisions
(`name_version`, as opposed to the unique ID) but I've grown more comfortable
that this isn't an issue in this case. I don't see backwards compatibility
being too much of a problem, apart from the obvious.
I'm not convinced by your argument against 2. We could say to delete from
persistence something if it is a duplicate of a different ID _brooklyn_-managed
bundle, then being simply a karaf cache jar wouldn't be enough to block
persistence. The slight mess is still that the persisted ID for the default
catalog changes on every restart but could live with this if it's easier/safer
than (1).
---
