brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <>
Subject [GitHub] brooklyn-server issue #877: update maven-bundle-plugin to include headers fo...
Date Tue, 07 Nov 2017 12:49:30 GMT
Github user aledsage commented on the issue:
    Agreed this should be safe, and agree it's the right default. Merging.
    For the record, my reasoning is...
    bundles that are shipped in brooklyn will be automatically updated when a new brooklyn
release is shipped. The new distro version will contain the new bundle versions of everything
in brooklyn. They are extremely likely to contain java code, rather than pure yaml .bom files
(for pure-yaml, we can much better handle having multiple versions - we don't need to worry
about java binary compatibility, for which version of Brooklyn it was compiled against). These
bundles should be automatically upgraded.
    We should be careful in Brooklyn about moving entities/policies around between bundles,
or renaming bundles. If we do, then that bundle may need to override the defaults.
    Blueprints are increasingly written by the community (e.g. see contributions to
Their release cadence is different from that of core brooklyn. Moving forwards, the core of
brooklyn is not where we should be writing and maintaining a lot of entity integrations.


View raw message