-
Enhancement
-
Resolution: Duplicate
-
P4
-
6, 8
-
generic
-
generic
> Separately from my change - is there an opportunity to improve this sync
> process? The current version of jni.h in the RE master Hotspot/J2SE are
> not in sync. It seems like there is a potential for changes to fall
> through the cracks here. Shouldn't the Hotspot build export these
> header files and the J2SE build grab them from the Hotspot import
> directory just as it does libjvm.so? Is there a reason exported headers
> need to be under source control in the J2SE workspace?
This is a request for more sanity checking, and hopefully an automated
way to keep these files in lock-step.
###@###.### 2005-1-28 18:52:15 GMT
- duplicates
-
JDK-8167078 Duplicate header files in hotspot and jdk
- Resolved
- relates to
-
JDK-4296917 portability : VM assumes jlong is a scalar type
- Open
-
JDK-5031222 JDK1_1InitArgs no longer supported
- Closed
-
JDK-4904617 JVM_Read needs better documentation
- Closed
-
JDK-6214406 MS VC++ compiler warning at jni.h when using fastcall, enable optimization
- Closed
-
JDK-8167078 Duplicate header files in hotspot and jdk
- Resolved
-
JDK-6220093 Definition of _jobject, _jfieldID, _jmethodID in jni.h causes .NET TypeLoadException on Windows
- Closed
-
JDK-6784084 jvmti.h created during the build differs from file in jdk repo and should not
- Closed
-
JDK-6318532 Hotspot make/Makefile needs to export the version of jni.h they wish to make public
- Closed