Performance whitelist test reports that the following class is being loaded on NetBeans startup:
This is considered as NetBeans performance regression. Please remove these classes from NetBeans startup.
Created attachment 70473 [details]
I do not know how, if even reasonably doable, I could lazy initialize the EditorAwareSourceTaskFactory implementation so
it won't be initialized during startup. The original code triggering the class load (SourceTaskFactoryManager) is taken
from Retouche and is a part of GSF infrastructure.
Adding Jan Lahoda and Tor as authors of the code to cc. Can you guys please express your opinion on this issue? I am not
familiar with all the aspects. Thanks.
I think that not loading the class, but keeping the functionality at the same time (and doing it cleanly) would require
big changes (mainly on the infrastructure side), which will be rendered obsolete by the ParsingAPI.
For the record: it might be possible to merge the functionality of the task into an existing task (like
SemanticHighlighter), but I do not think that preventing loading a class is a good enough reason for such an ugliness.
So, I do not think it is reasonable to fix this for 6.5.
I agree, the used solution is correct, I do not see any reason why an 'enhancement' (the original solution was a plain
hack) should be considered as an regression if other instances are ok.
jlahodas's workaround with using different EditorAwareSourceTaskFactory to handle the code is doable, but it similar to
the original unclear solution.
I personaly do not consider this as a problem especially when it is a subject to change in next version by the parsing api.
I fully agree with Marek's resolution.
NetBeans.org Migration: changing resolution from LATER to WONTFIX