Classpath Scanning task starts too soon at project opening because during the
opening of projects the classpath is modified too soon and this triggers the CP
Setting of classpath should be deffered as late as possible so that first all
the projects are open and after that CP Scanning starts.
Will try to do for 5.0.
Requires an API extension, an support class which collects project's classpaths
and puts them into the GlobalPathRegistry when all projects are opened.
OK. Please, plan this change for next release. According to numbers jlahoda
measured, this would make the project opening significantly faster (the part
with the blocking dialog box). Thanks.
No problem, I have already an implementation, but on Friday there was no 5.1 target.
moving opened issues from TM <= 6.1 to TM=Dev
Created attachment 65260 [details]
The patch looks nice, feel free to integrate.