different behavior of bundles loaded from repo (profile) or provided bundle
directory
-------------------------------------------------------------------------------------
Key: PAXRUNNER-356
URL: http://issues.ops4j.org/browse/PAXRUNNER-356
Project: Pax Runner
Issue Type: Bug
Affects Versions: 1.4.0
Reporter: Oliver Lietz
Assignee: Alin Dreghiciu
When {{eclipse.gemini.blueprint/1.0.0.M1}} profile is used,
{{org.eclipse.gemini.blueprint.extender.internal.blueprint.activator.BlueprintTypeCompatibilityChecker#isTypeCompatible(BundleContext
targetContext)}} fails.
(called in
{{org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager.maybeCreateApplicationContextFor(Bundle
bundle)}})
The same jars placed in a bundle directory (provisioning spec) works.
Tested:
{{org.eclipse.gemini.blueprint.extender.internal.blueprint.activator.BlueprintTypeCompatibilityChecker#isTypeCompatible(BundleContext
targetContext)}} changed to return always {{true}} works also (1.0.0.M2).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
