TL;DR - Windows Defender adds 1.5 minutes or more to Eclipse launch
Lately, I've heard some colleagues grumbling about how Eclipse startup seems slower. I'll admit that I'm recently back on Windows after years on Mac and was surprised. Some quick metrics:
0:05 - time to extract 354mb JEE 2019-06 RC1 zip
1:28 - time spent by Windows Defender before Eclipse workspace prompt
A similar slowdown is observed after Eclipse updates, either itself or when adding plugins.
I'm running on a fast laptop (latest Intel i7, 32gb ram, etc.). A colleague had a large Eclipse setup blocked for 11 minutes before he got the workspace prompt, though likely had some other load on the box at the time.
I've been googling around trying to find ways to submit/pre-approve plugins, etc. but so far Windows Defender doesn't seem to have ways that other virus software does. My assumption is it is scanning all jar files as "potential malicious executables."
Is this something others have observed/already pursued solutions for? Yes, there is a workaround of just turning off/excluding folders from Windows Defender, but as plugin makers, we're concerned about the perceived impact of "Eclipse is slow" that this gives.
Tim
