[
https://issues.apache.org/jira/browse/FELIX-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage updated FELIX-1448:
--------------------------------
Attachment: (was: bundle-builder-patch.txt)
> Combining require bundle with import package fails due to BND validation that
> all imports are provided, when some packages would be provided by required
> bundles
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-1448
> URL: https://issues.apache.org/jira/browse/FELIX-1448
> Project: Felix
> Issue Type: Bug
> Components: Sigil
> Reporter: David Savage
> Attachments: bundle-builder-patch.txt
>
>
> If we have bundles foo, bar and baz that contain the following info:
> #foo/sigil.properties
> -bundles: org.example.foo
> -exports: org.example.foo
> #bar/sigil.properties
> -bundles: org.example.bar
> -exports: org.example.bar
> #baz/sigil.properties
> -bundles: org.example.baz
> -imports: org.example.foo
> -requires: org.example.bar
> We will get a error message from BND when generating baz if classes from the
> package org.example.bar are used by baz as BND expects to have an import
> statement but the classes are supplied by the require-bundle dependency.
> In most cases this is a non issue as require-bundle could easilly be swapped
> for import-package but this fails if org.example.bar is fragmented across
> several bundles, then we have to use requires in order to maintain the
> correct class space. The uber answer is to use mandatory export flags but
> this will only work if the supplying bundle provides these - if not we have
> to fall back to require-bundle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
