RFR: 8338675: javac shouldn't silently change .jar files on the classpath [v3]

Jan Lahoda jlahoda at openjdk.org
Fri Feb 28 17:45:53 UTC 2025


On Fri, 21 Feb 2025 12:18:21 GMT, David Beaumont <duke at openjdk.org> wrote:

>> Modifying `JavacFileManager` to skip creating sibling output class files for source files found in JARs.
>> 
>> This should match older (JDK 8) behavior whereby the JAR was not writable, and results in any newly generated class files being written to the current working directory (the output of class files into current directory isn't good, but it should match the old behavior).
>
> David Beaumont has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Changes based on PR feedback.

I think it would be useful to have an answer to this CSR question:
https://bugs.openjdk.org/browse/JDK-8350492?focusedId=14755916&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14755916

I suspect best would be to have some tests for the Filer methods.

Please note you'll have to mark the CSR Finalized before it is considered again. Thanks!

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23699#issuecomment-2691214687


More information about the compiler-dev mailing list