use correct case for Brooklyn-Catalog-* manifest headers
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/31eda46b Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/31eda46b Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/31eda46b Branch: refs/heads/master Commit: 31eda46b073c2dbfd334fed5a3d59361793832b8 Parents: 4e5a532 Author: Alex Heneveld <[email protected]> Authored: Sat Nov 4 10:55:33 2017 +0000 Committer: Alex Heneveld <[email protected]> Committed: Sat Nov 4 10:55:33 2017 +0000 ---------------------------------------------------------------------- guide/ops/upgrades/_blueprints.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/31eda46b/guide/ops/upgrades/_blueprints.md ---------------------------------------------------------------------- diff --git a/guide/ops/upgrades/_blueprints.md b/guide/ops/upgrades/_blueprints.md index 45b644b..f525c1d 100644 --- a/guide/ops/upgrades/_blueprints.md +++ b/guide/ops/upgrades/_blueprints.md @@ -14,23 +14,23 @@ not compatible with the newer version of Brooklyn. To add these definitions, use the following headers in the bundle's OSGi `META-INF/MANIFEST.MF`: -* `brooklyn-catalog-force-remove-bundles` -* `brooklyn-catalog-force-remove-legacy-items` -* `brooklyn-catalog-upgrade-for-bundles` -* `brooklyn-catalog-upgrade-for-types` +* `Brooklyn-Catalog-Force-Remove-Bundles` +* `Brooklyn-Catalog-Force-Remove-Legacy-Items` +* `Brooklyn-Catalog-Upgrade-For-Bundles` +* `Brooklyn-Catalog-Upgrade-For-Types` The most common patterns are to indicate that a bundle can replace all previous versions of itself and all types thereing with types in the current bundle of the same name, using: ``` -brooklyn-catalog-upgrade-for-bundles: * +Brooklyn-Catalog-Upgrade-For-Bundles: * ``` And you can indicate that previous bundles should be uninstalled, forcing the above upgrades, with: ``` -brooklyn-catalog-force-remove-bundles: * +Brooklyn-Catalog-Force-Remove-Bundles: * ``` The above items can also take a range syntax, e.g. `"*:[1,2)"` when releasing a `2.0.0` to restrict to
