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.
Anyone distributing JavaBeans as a library (as with http://contrib.netbeans.org/beans2nbm ) is likely to have a design-time version of their library for work in the IDE, and a stripped down one without property editors for end users of the library to deploy. Currently there is no way to have the build script bundle a different version of a library for deployment than the one the IDE uses. Not sure where to file this as we don't have a "libraries" category for the java module (shouldn't we?). Anyway, if we're revamping library support for 6.0, this is a requirement to keep in mind.
Are there really enough people doing this to make it worthwhile? I would suggest this be closed as WONTFIX for now, but create a wiki FAQ entry explaining how to modify your build.xml to do it when you need to. BTW Java libraries are covered under java/platform but this is more a request for j2seproject to handle such a special packaging step. In fact j2seproject doesn't currently bundle libs at all so enhancing its future hypothetical bundling logic is not a priority.
Our MiG Calendar component would benefit from such a feature. Our "bean property" version is 1.3 MB and our distributable jar is 0.6MB so there are a lot to gain. Simplicity for the users is the keyword here. To me it looks like a very simple thing to add, but I might be wrong about that. Cheers, Mikael Grev
If we want to encourage Swing components to be distributed via NetBeans plug- ins, well, two versions of the library is the way Swing developers are advised to do it.
Not much of a priority, I think.