Skip to content

ignore start option for fragment bundles. skip fragment bundles during '...#26

Open
dsklyut wants to merge 1 commit intoops4j:masterfrom
dsklyut:feature/ignore-fragment-bundle-start-option
Open

ignore start option for fragment bundles. skip fragment bundles during '...#26
dsklyut wants to merge 1 commit intoops4j:masterfrom
dsklyut:feature/ignore-fragment-bundle-start-option

Conversation

@dsklyut
Copy link
Copy Markdown

@dsklyut dsklyut commented Dec 23, 2014

ignore start option for fragment bundles. skip fragment bundles during 'pax.exam.osgi.unresolved.fail' key check

@hwellmann
Copy link
Copy Markdown
Member

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).

@dsklyut
Copy link
Copy Markdown
Author

dsklyut commented Dec 24, 2014

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants