daniellansun opened a new pull request, #3242: URL: https://github.com/apache/groovy/pull/3242
## Summary Joint compilation can keep javac `CLASS_OUTPUT` in memory when `memStub` is enabled ([GROOVY-12711](https://issues.apache.org/jira/browse/GROOVY-12711)). `InMemoryJavaFileManager` wraps a standard file manager and stores class files on the heap. The new joint option `memClassOutput` (`CompilerConfiguration.MEM_CLASS_OUTPUT`) takes effect only together with `memStub`. In that mode `JavaAwareCompilationUnit` does not require `stubDir` or a filesystem target directory: Groovy resolves the javac bytes from memory, and Groovy's own class files are published to the same class loader instead of being written to disk. Disk `stubDir` and target-directory output stay the default when the option is off. `groovy.mem.stub` still enables in-memory stubs only. New API is marked `@since 7.0.0`, matching this line (`7.0.0-SNAPSHOT`). ## Test plan - `./gradlew :test --tests org.codehaus.groovy.tools.javac.MemClassOutputTest` - `./gradlew :test --tests org.codehaus.groovy.classgen.InterfaceTest` - `./gradlew checkstyleGate codenarcGate :binary-compatibility:checkBinaryCompatibility` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
