As mentioned in #1774 (comment), we need to look into the AOT usage and output to see what can be done to further improve the AOT cache usage and reduce the number of classes that can't be cached.
For now, it looks like some JAR file signing of the Eclipse JARs prevent the Leyden AOT cache implementation from caching data for those classes, so we might need to remove the signatures (as a first idea).
As mentioned in #1774 (comment), we need to look into the AOT usage and output to see what can be done to further improve the AOT cache usage and reduce the number of classes that can't be cached.
For now, it looks like some JAR file signing of the Eclipse JARs prevent the Leyden AOT cache implementation from caching data for those classes, so we might need to remove the signatures (as a first idea).