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.
There should be a way to create a Platform Module project that is based on an existing Library project. When the module is compiled, it should compile the library project, and import the resulting jar files. It should also support code-completion based on the library project's current sources. It is very annoying to have to create a module-library project and manually update the jar file every time I modify the associated library project; also, currently, module-library projects have NO support for code-completion.
reassign to apisupport for evaluation
Code completion works for me for library built from sources in NB 6.5, could you try it with 6.5? Regarding manual copying of library jar, there is an easy workaround. Override target "netbeans-extra" in your Library Wrapper's build.xml and copy the library jar from library project to binary-origin in the wrapper project. Like this: <target name="netbeans-extra"> <copy file="../MyLibProject/dist/MyLib.jar" todir="release/modules/ext" /> </target> That way Library Wrapper always uses latest version of the library jar. Maybe we could support copying jar from external location in New Library Wrapper Wizard.
See also issue #66275
See also http://wiki.netbeans.org/DevFaqWrapperModules#section-DevFaqWrapperModules-Using%20a%20wrapper%20module%20for%20an%20existing%20project. *** This issue has been marked as a duplicate of 70894 ***
Yes.