You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2007/03/05 22:33:51 UTC

[jira] Commented: (FELIX-28) Implement require-bundle functionality

    [ https://issues.apache.org/jira/browse/FELIX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478167 ] 

Richard S. Hall commented on FELIX-28:
--------------------------------------

I have committed support for "private" as well as "re-export" require-bundle dependencies. I have run the TCK on these changes and it appears to be doing better than the previous version, so I take that as a good sign. This only leaves support for optional require-bundle dependencies to be implemented.

I also expect that I might need to revisit some class load delegation ordering issues...the R4.1 spec is more clear about how require-bundle works and I changed our implementation to reflect that, but I may have been too aggressive in one of my assumptions about class load delegation order...right now it ignores order since R4.1 says that exported packages from required bundles should not overlap, but perhaps this is too optimistic and will need to be more strict in order. I will investigate this issue.

> Implement require-bundle functionality
> --------------------------------------
>
>                 Key: FELIX-28
>                 URL: https://issues.apache.org/jira/browse/FELIX-28
>             Project: Felix
>          Issue Type: New Feature
>          Components: Framework, Specification compliance
>    Affects Versions: 0.8.0
>            Reporter: Richard S. Hall
>         Assigned To: Richard S. Hall
>             Fix For: 1.0.0
>
>
> This issue is described in section 3.13 of the OSGi R4 specification. The main jist is that bundles can now express explicit dependencies on other named bundles. This means that the depending bundle imports everything that the target bundle exports. It is also possible to re-export imported packages. This issue impacts the resolver algorithm and will likely have some impacts on the run-time class loading search order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.