ignore start option for fragment bundles. skip fragment bundles during '... #26
Conversation
This file contains 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
…g 'pax.exam.osgi.unresolved.fail' key check
|
See https://ops4j1.jira.com/browse/PAXEXAM-472. I think it's ok to change the defaults for fragments, but then this should apply to all OSGi containers (i.e. also Forked and Karaf Container). |
|
Forked container uses pax-swissbox-framework to query state of the bundle. So another method should be added to the RemoteFramework interface in pax-swissbox-framework to check if the bundle is a fragment. As for Karaf - this container does not check "pax.exam.osgi.unresolved.fail" key at all. I believe that karaf is in charge of managing bundle start up. |
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.
ignore start option for fragment bundles. skip fragment bundles during 'pax.exam.osgi.unresolved.fail' key check