[
https://issues.apache.org/jira/browse/FELIX-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409767#comment-13409767
]
Richard S. Hall commented on FELIX-3587:
----------------------------------------
For system bundle extensions, I'm not sure if there is a case that matters
where the resolver won't detect a need for the fragment. Regardless, it makes
the most sense to figure out how to run this through the resolver to determine
if attaching the fragment is possible since trying to detect it requires
knowing something about resolving anyway. All of this is more complicated than
what I can think about right now, but I agree that this is a real issue that
should ultimately be addressed.
> Uses constraint violation due to framework extension bundle
> -----------------------------------------------------------
>
> Key: FELIX-3587
> URL: https://issues.apache.org/jira/browse/FELIX-3587
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Reporter: Sahoo
>
> There seems to be an issue with framework extension bundle and I have not
> checked the spec yet. Felix allows extension bundle to be attached at
> runtime, but that can sometimes lead to uses constraint violation if a
> package exported by the framework extension is also exported by some other
> regular bundle and that package from regular bundle is in use. A
> refreshPackages solves the issue, but that seems to be putting the onus on
> user. Can the framework be smart enough to not attach an extension bundle to
> host when it sees that an extension is exporting a package which is already
> in use?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
