-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: ECJ appears to flush custom JavaFileManager objects repeatedly #3502
Comments
Please add info how to reproduce, what is the bad consequence and what you expect. |
If you view the linked comment and thread, I have a library at github.com/ascopes/java-compiler-testing that has a feature/v5-ecj branch where I am integrating with ECJ. If you enable |
Why is that a problem? Will you work on a fix? Without selfcontainig reproducer of a problem it is unlikely anybody else will work on it. |
It is not a "problem" but ECJ calling flush 25 times rather than 1 does not feel like it is valid behaviour. Happy to close if it does not constitute an issue. |
Closing as won't fix. Still anyone is invited to propose a PR to improve the code. |
Sadly I cannot reopen it. |
I'll reopen it for now as requested. |
Follow up of #958 (comment), as requested by @stephan-herrmann.
It appears that when using a custom JavaFileManager implementation, the call to
.flush
at the end of the compilation run is repeated numerous times. It seems to vary depending on what the project is doing but for less than a dozen source files, I have observed it being called more than 20 times in a row.The text was updated successfully, but these errors were encountered: