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.
- open project properties for some netbeans module - and module dependency on e.g org.eclipse.jgit - the entry created in project.xml will be <dependency> <code-name-base>org.eclipse.jgit</code-name-base> <run-dependency/> </dependency>
Works when I try it on a new standalone module - added a dep on org.apache.commons.logging; created <compile-dependency/> as expected. Same for org.eclipse.jgit. But for a nb.org module org.eclipse.jgit is not listed as an API-exporting module, whereas org.eclipse.core.jobs and a couple other bundles are. Probably an issue with ModuleEntry.getPublicPackages.
...because o.eclipse.core.jobs/nbproject/project.xml specifies some <public-packages> whereas o.eclipse.jgit/nbproject/project.xml does not. When used from a nb.org module, the source project is considered rather than the result JAR, and apisupport.ant does not know anything about what the final JAR will contain beyond what project.xml claims. And an empty <public-packages/> indicates that you need to check "Show Non-API Modules" to add the dep, and when added it will be a runtime-only dependency.