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.
> The other one point is also RFE. Now we have rather complex java > project. Some of our classes use native methods. So it would be very > helpful feature to create .h file in the C++ Project (Application or > Library - it doesn`t matter) on the bases of the appropriate .java file > (I mean, using "javah -jni blah-blah-blah") just using a wizard inside > NetBeans IDE or something more simple than that. > > What I should do now to get this .h file in my C++ project? I should: > 1) Compile java file > 2) Go to console and run "javah -jni blah-blah-blah" > 3) Move created .h file to the C++ project`s folder (not mandatory but > it is a right thing to do) > 4) Add this *.h file to the project > So, too many steps...
The best option would be to have this special JNI project be hooked up to a Java project in a way similar to what UML does. E.g. cnd should add a context menu to java projects, something like "Generate JNI", which would be enabled if classes with native methods are present. Upon clicking on it a new C/C++ Library should be created, and all required javah work should be done. After the initial generation, it would be great to have a possibility to refresh JNI headers if java native methods change. Ideally, this should be done automatically by monitoring changes to the java model. And one last notice. Since NetBeans was and is used mostly as a java IDE, easy JNI authoring would be a major plus and driving factor for cnd. Thus I'm really tempted to state that this is a P2 enhancement, if not a P1 one.
not in 7.0