JDK-6387310 : include/jvmpi.h is missed
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmpi
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2006-02-17
  • Updated: 2010-04-02
  • Resolved: 2006-02-18
Related Reports
Relates :  
JDK-6266948 - deploy/src/plugin/win32/jpishare/CJavaJNI.cpp depends on jvmpi.h, which was removed in 6260810
Relates :  
JDK-4914266 - Remove JVMPI in Dolphin/JDK7/Java7
Relates :  
JDK-6265756 - Remove JVMDI
Relates :  
JDK-6260810 - Remove jvmdi.h and jvmpi.h from j2se workspace and JDK include directory
Description
Mustang still provides JVMPI support via -XX:+UseUnsupportedDeprecatedJVMPI option of VM
but JVMPI header files is removed from the JDK bundle and as result existing JVMPI based
clients cannot be recompiled for Mustang. While JVMPI is supported by VM it would be good
to provide corresponding jvmpi.h in the JDK for example in a special "deprecated" directory:
include/deprecated/jvmpi.h. 

BTW, I cannot find a CCC request that approves this removal.
Is there such one?
Comments
EVALUATION The jvmpi.h file was removed in Mustang-B37 as part of the following bug fix: 6260810 2/2 Remove jvmdi.h and jvmpi.h from j2se workspace and JDK include directory The original plan was to remove both JVM/DI and JVM/PI from Mustang (4914266 & 6265756) and that plan was approved by Mustang Core. However, due to time constraints only JVM/DI was removed. JVM/PI will be removed early in Dolphin. The jvmpi.h file should not be restored. We do not want to encourage anyone to continue using this interface. If there is a legitimate need for the jvmpi.h file, then a project should include a local copy of the file in their own code base (e.g., 6266948). It is my intention to close this bug as "will not fix" after consulting with the submitter.
17-02-2006