[
https://issues.apache.org/jira/browse/FELIX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617338#action_12617338
]
Alin Dreghiciu commented on FELIX-648:
--------------------------------------
I could find workarounds for my case. In this case just adding the
resolution:=optional will suffice.
Just curious what are the consideration to not include them as the other
frameworks? Size? I made the change locally and the difference is 16kb.
I always had the impression that I can rely on the framework implementation to
export all the packages defined in the core specs.
Anyhow is not an hard issue.
> Make system bundle export org.osgi.service.permissionadmin/condpermadmin
> ------------------------------------------------------------------------
>
> Key: FELIX-648
> URL: https://issues.apache.org/jira/browse/FELIX-648
> Project: Felix
> Issue Type: New Feature
> Components: Framework
> Reporter: Alin Dreghiciu
> Priority: Trivial
>
> As org.osgi.service.permissionadmin and condpermadmin package is part of core
> OSGi spec I'm thinking that the system bundle of Felix should also export
> those packages even if there is no actual service implementation of those
> services.
> As an use case I have some bundles that import those packages (non optional)
> but those bundles could function if actual services are not present.
> In order to this on the current code base is just a matter of changing the
> maven bundle plugin <Export-Package> to include this packages while building
> the framework bundle and add them to the property
> "org.osgi.framework.system.packages" in main/conf.properties. I can provide a
> patch if required.
> As comparison, Equinox/Knopflerfish use the same approach. Export the
> packages but do not actually implement the service and I guess that Felix
> does not do that as there are no implementations of this services built in
> into framework. I guess that the other implementations provide those packages
> as they export all the packages from osgi core spec.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
