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.
Since Java Webstart is common practice to bundle the native libraries used by desktop applications in .jar files to be downloaded/updated by Webstart. Should be nice if the library manager of Nebenas will support this feature and allows the running of projects relying on native libraries packed in jars instead of having to install the libs in the system libraries paths. This feature will allow a more straightforward handling of multi platform development and will ensure that the execution enviorment will be more similar possible to the one of webstart applications (including the safety from system tainting).
Not for D. I think there are several items here: 1. Support for mixed-mode (Java + native) development, perhaps using a JNI-oriented project type with some C/C++ support that could be used to make a native-implemented library to be used in other apps. No immediate plans to do this; would be handled as a separate effort that could be added as a module. 2. Support for specifying a list of (precompiled) native lib directories (folders containing *.so or *.dll) in a regular Java library definition (along with the current classpath, sourcepath, and Javadoc path). This would be simple enough, but the trickier part would be making a j2seproject automatically set java.library.path (or something?) to a path constructed from the native paths of all libraries in the runtime classpath. 3. Support for WebStart, with all it entails; see issue #47512. Leaving open here primarily for #2. Needs study.
I intended the request as your #2.
*** Issue 49848 has been marked as a duplicate of this issue. ***
Same here. I am asking for feature #2.
I, too am having woes about this. I'm still struggling to get Mozilla webclient to run right within the Netbeabs IDE. Looks to be all java.library.path / JNI related. I would like to see this feature implemented in some fashion. Perhaps the module could also recursivley examine dependent DLL's / SO's, and give the user the 'level' of dependents to include. (Of course, letting them selectively exclude / include certain modules)
*** Issue 63614 has been marked as a duplicate of this issue. ***
*** Issue 22195 has been marked as a duplicate of this issue. ***
*** Issue 72406 has been marked as a duplicate of this issue. ***
*** Issue 90067 has been marked as a duplicate of this issue. ***
*** Issue 132698 has been marked as a duplicate of this issue. ***
Should be prioritized, please consider estimate of difficulty.