You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today when a Java source file is saved, it evicts the Java cache of Qute which stores information of Java source and binary classes (ex : Integer String have some methods) to use it with completion.
It means that each time you save a Java file source (in IJ it is not on saved but on change of Java file), it evict the cache from Java sources and binary classes and it compute again the data model from sources and binary (ex : it scans JAR to collect Qute renarde user tags, it collect again methods of String).
You can notice that by seeing LSP console which collect information about String, Collection, etc after a Java source change although the cache should not evict binary classes:
Today when a Java source file is saved, it evicts the Java cache of Qute which stores information of Java source and binary classes (ex : Integer String have some methods) to use it with completion.
It means that each time you save a Java file source (in IJ it is not on saved but on change of Java file), it evict the cache from Java sources and binary classes and it compute again the data model from sources and binary (ex : it scans JAR to collect Qute renarde user tags, it collect again methods of String).
You can notice that by seeing LSP console which collect information about String, Collection, etc after a Java source change although the cache should not evict binary classes:
The evict cache must be improved to evict only data model of Java sources and not of binary when a Java file is saved.
The text was updated successfully, but these errors were encountered: