This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Netigso.fakeBundle skips modules without public packages | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | Netigso | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 198248 |
Description
Jesse Glick
2011-05-05 12:53:20 UTC
The reasoning is like this: There is no reason why an OSGi should want to depend on a module without public packages (OSGi does not support implementation dependencies). Thus there is no reason to export modules without public packages. I verify the problem with man.getMainAttributes().putValue("Export-Package", m.getCodeNameBase(). (In reply to comment #1) > There is no reason why an OSGi [bundle?] should want to > depend on a module without public packages Right, it cannot. But the app might expect that such a module is nonetheless loaded by the OSGi framework and activated, which would make an observable difference in case there is some system such as the Eclipse plugin.xml scanner which pays attention to the list of activated bundles (and changes therein). We will fix the problem as soon as it really demonstrates itself. |