catalog-classes.bom: don’t specify bundle id/version#253
Merged
asfgit merged 1 commit intoapache:masterfrom Jul 12, 2016
Merged
Conversation
Contributor
Author
|
Merging now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed with @neykov and @Graeme-Miller
Previously the
catalog-classes.bomincluded the Brooklyn version number in which the bundles are to be found. This works well when installing and using Brooklyn, but these bundle version numbers make their way into the persisted state.After upgrading Brooklyn and restarting, it uses the existing persisted state. The bundle with the old Brooklyn version is not in this new karaf install, so it fails with the exception below: