JDK-8217412 : deprecate rmic for removal
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.rmi
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-19
  • Updated: 2020-03-16
  • Resolved: 2019-06-04
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 13 JDK 14
13 b24Fixed 14Fixed
Related Reports
CSR :  
JDK-8225025 - deprecate rmic for removal
Relates :  
JDK-8241073 - Pre-generated Stubs for javax.management, Activation, Naming
Sub Tasks
JDK-8225318 :  
Release Note: Deprecated rmic Tool for Removal - Closed
Description
The rmic tool should be deprecated for removal, and eventually removed from the set of public tools delivered with the JDK.

Rmic is the static stub compiler for RMI. Statically compiled stubs have been ordinarily deprecated for some time, including the rmic tool. This was done by JDK-8023863 and JDK-8026020 in Java 8. RMI applications, dynamic generated stubs are functionally equivalent to statically generated stubs. Dynamic stubs have been available since Java 5, so applications should easily be able to cope with the absence of rmic.

There are still uses of static stubs internal to the JDK. These can be fulfilled in a variety of ways that are not impacted by removal of rmic from the publicly delivered set of tools.

This is mostly just a change of deprecation status; no actual functionality will be changed. This will entail:
 * a CSR request;
 * changing the warning message issued by rmic;
 * changing the rmic documentation ("man page") to reflect the changed deprecation status; and
 * a release note.