JDK-6854695 : remove support for undocumented LLNI format and related switches
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javah
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2009-06-24
  • Updated: 2017-05-16
  • Resolved: 2010-10-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6572945 - javah should be written as an annotation processor, not a doclet
Description
javah has a mostly undocumented feature to generate LLNI headers instead of standard JNI headers. It is proposed to remove this feature, as it being no longer used or necessary.

The code appears in JDK 1.2, when javah was converted from C to Java. At that point, the undocumented switch was -Xllni. By 1.4, -llni was accepted as well as -Xllni, but still not documented in the -help usage message.

A Google search for LLNI mostly brings up some SunLabs papers in 1998.
Comments
EVALUATION LLNI was dropped from command line support in the anno-processor rewrite. The internal classes can be removed at a later date.
29-10-2010
EVALUATION No specification for the feature can be found. Relevant references on Google are over 10 years old. Checked with the hotspot-dev folk, who confirm this feature can be removed.
26-06-2009