brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] brooklyn-server issue #867: BROOKLYN-546: fix rebind of system bundles
Date Tue, 24 Oct 2017 23:05:51 GMT
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).


---

Mime
View raw message