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: | Need for a Platform Module project based on a standard Library project | ||
---|---|---|---|
Product: | apisupport | Reporter: | plymouthjason <plymouthjason> |
Component: | Project | Assignee: | rmichalsky <rmichalsky> |
Status: | VERIFIED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
plymouthjason
2008-03-25 14:49:15 UTC
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. |