JDK-8289279 : Better handling of classpath jar files in javac
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 19
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2022-06-28
  • Updated: 2023-12-13
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8281316 - javac performance issues with large number of jars on classpath
Description
Currently in javac while reading manifest files and when creating an archive container we open the same jar file twice once in FSInfo class to read manifest attributes and again in JavacFileManager class which reduces the performance of javac. To resolve this we should be creating a cache of file systems after reading a jar file either in FSInfo or JavacFileManager classes.
I'm attaching a test case where the opening of a single jar file multiple times can be observed. I have given rt.jar file as the classpath to test this use case.