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.
As discussed in http://www.netbeans.org/servlets/ReadMsg?msgId=412036&listName=nbdev for the sake of upgradability (future compatibility) it seems reasonable to allow a module to "export" packages that it imported by from other module. Would be nice to make this enh. till 4.0 so editor module can use it and does not need to overuse the modules/ext mechanism.
I am still queasy about this RFE as it complicates the semantic model for how modules access one another's packages: http://www.netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/classpath.html#public-packages However I have a different idea. As part of issue #29914, I decided to keep the list of automatic dependency upgrades done by NbInstaller in a declarative XML file for easy editing. I think it may be feasible to actually have this list composed from modules rather than all hardcoded in core. (Solvable technical problems here, since the info must be gotten while the module is still disabled...) Then solution #1 in the nbdev message would be unobjectionable.
Prefer solution in issue #30161, q.v.
verifying.