Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1386043605.1249396514967.JavaMail.jira@brutus>
Date: Tue, 4 Aug 2009 07:35:14 -0700 (PDT)
From: "David Savage (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Updated: (FELIX-1448) 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
In-Reply-To: <1388694198.1249380074925.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FELIX-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Savage updated FELIX-1448:
--------------------------------

    Attachment: bundle-builder-patch.txt

Ok found a better fix. bundle-builder-patch.txt now adds !* to end of imports which gives BND rules to deal with packages that are not explicitly imported

> 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, 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.