You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/08/19 10:34:14 UTC
[jira] Created: (FELIX-1502) Importing, exporting and including
(private-package) a package in a bundle confuses sigil resolver
Importing, exporting and including (private-package) a package in a bundle confuses sigil resolver
--------------------------------------------------------------------------------------------------
Key: FELIX-1502
URL: https://issues.apache.org/jira/browse/FELIX-1502
Project: Felix
Issue Type: Bug
Components: Sigil
Reporter: David Savage
Priority: Minor
Consider the following use case:
Bundle foo provides package org.foo
Bundle bar wants to import org.foo but also include it in it's bundle classpath such that it can be installed without foo, it should therefore also export org.foo to preserve the classspace should foo and bar be installed in the same jvm
Unfortunately this confuses the sigil resolver which now thinks that bar contains the packages org.foo (as it is exporting them) when at compile time it should pull in bundle foo to satisfy the classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1502) Importing, exporting and including
(private-package) a package in a bundle confuses sigil resolver
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage resolved FELIX-1502.
---------------------------------
Resolution: Fixed
Fix Version/s: sigil-1.0.0
Workspace repository now filters package exports during compile time resolution to ensure that projects are not supplied as providers of capabilities that are not available from the source code - avoids messy compile time errors when a project is added as a provider of classes which it doesn't contain until after build time
> Importing, exporting and including (private-package) a package in a bundle confuses sigil resolver
> --------------------------------------------------------------------------------------------------
>
> Key: FELIX-1502
> URL: https://issues.apache.org/jira/browse/FELIX-1502
> Project: Felix
> Issue Type: Bug
> Components: Sigil
> Reporter: David Savage
> Priority: Minor
> Fix For: sigil-1.0.0
>
>
> Consider the following use case:
> Bundle foo provides package org.foo
> Bundle bar wants to import org.foo but also include it in it's bundle classpath such that it can be installed without foo, it should therefore also export org.foo to preserve the classspace should foo and bar be installed in the same jvm
> Unfortunately this confuses the sigil resolver which now thinks that bar contains the packages org.foo (as it is exporting them) when at compile time it should pull in bundle foo to satisfy the classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.