JDT team,
Does anyone know of a change from Eclipse 4.8 or 4.9 timeframe that would have stopped packages or compilation units from filling the JavaModelCache (managed
by JavaModelManager)? Is there any reason why after compilation of a source file it should not have its java elements cached in the model?
I have been investigating slow down in JUnit launch on and off for some time. There is much more detail in this bug ticket:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=540712
Long story short, Create Type Hierarchy takes very long (over 216 seconds for one of my projects). The second time around, it runs in much less time (~18 seconds) due to something
being cached by the type hierarchy builder. In the case of a larger java project, the time to launch just after compilation is over 20 minutes! And is about 2 minutes for each subsequent launch.
I was finally able to see that JavaModelCache is populated with packages, compilation units, etc. (their children). Something changed between Eclipse Neon (4.7) and Photon (4.9)
-- according to the ticket. I was able to force the population for each compilation unit in AbstractImageBuilder when ClassFiles are accepted and the time went down to match the cached/second run of Run As > JUnit Test.
I appreciate your time in considering this issue. And thanks to all who support JDT.
Eric Milles
Lead Software Engineer - Thomson Reuters
Member - Eclipse Foundation, Apache Foundation
This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain
required legal entity disclosures can be accessed on our website: https://www.thomsonreuters.com/en/resources/disclosures.html