-
Bug
-
Resolution: Fixed
-
P4
-
6, 9
-
b92
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8143506 | emb-9 | Magnus Ihse Bursie | P4 | Resolved | Fixed | team |
The launcher <jdkhome>[/jre]/java-rmi.exe, new in JDK 6 on Windows, is broken. It behaves just like any 'java.exe' launcher instead. It should also be named 'java-rmi.cgi' according to the JDK 6 build instructions.
The reason is that the JDK 6 build instructions in j2se/make/sun/rmi/cgi/Makefile is incomplete, not explicitly setting FILES_o, causing Program.gmk to override the local definitions of FILES_c, to build from the source at j2se/src/windows/bin/java-rmi.c, with normal java launcher defaults. A probable solution is to explicitly set FILES_o in the same way as has been done in j2se/make/java/jexec/Makefile.
It actually seems as if the rewrite of Program.gmk caused the build of java-rmi.cgi to fail, keeping the name java-rmi.exe, thus causing it to be included in Windows builds that as one of the final build steps in Release.gmk copies *.exe to the target bin directory.
Reading the build it seems the intention is to actually ship a working version of java-rmi.cgi also on Windows, so please update both the java-rmi.cgi build instructions and the Release.gmk packaging script to include it.
The reason is that the JDK 6 build instructions in j2se/make/sun/rmi/cgi/Makefile is incomplete, not explicitly setting FILES_o, causing Program.gmk to override the local definitions of FILES_c, to build from the source at j2se/src/windows/bin/java-rmi.c, with normal java launcher defaults. A probable solution is to explicitly set FILES_o in the same way as has been done in j2se/make/java/jexec/Makefile.
It actually seems as if the rewrite of Program.gmk caused the build of java-rmi.cgi to fail, keeping the name java-rmi.exe, thus causing it to be included in Windows builds that as one of the final build steps in Release.gmk copies *.exe to the target bin directory.
Reading the build it seems the intention is to actually ship a working version of java-rmi.cgi also on Windows, so please update both the java-rmi.cgi build instructions and the Release.gmk packaging script to include it.
- backported by
-
JDK-8143506 remove java-rmi.exe and java-rmi.cgi
-
- Resolved
-
- blocks
-
JDK-8066750 Remove HTTP proxy implementation and tests from RMI
-
- Resolved
-
-
JDK-8155978 Remove HTTP proxy implementation and tests from RMI (again)
-
- Resolved
-
- relates to
-
JDK-7043921 generate java-rmi.cgi on 64 bit platform
-
- Closed
-
-
JDK-4418631 java-rmi.cgi missing on Win32 builds since 1.1.x
-
- Closed
-