Community
Participate
Working Groups
1. Create a Java Project without any library 2. Import the source for JDK from src.jar in this project with autobuild on 3. At the end of the import, it starts building: you should get errors because the the source is contained in an src folder and the classpath is not set to include this folder yet 4. Wait until you get more than 10000 errors, then press Cancel Updating takes a very long time: in VAJ this had been running for more than 10 minutes before I killed the workbench. NOTES: EG (10/13/00 10:21:27 AM) the Task List View doesn't scale to a large number of entries. Moving to ITPUI NE (04/11/01 3:36:46 PM) Need to check performance with many tasks, in JDK build.
PRODUCT VERSION: jabiru 24
It's unlikely that we will be able to fundamentally change the presentation of the task list in the near future. From the description it looks like the error markers were still generated in spite of the user pressing cancel. Not generating the markers would have a huge impact on the performace. Is this possible?
Would it be possible to not populate the task list with errors if a build has been cancelled?
Markers are created as errors are discovered. So I don't think it is possible. Assigning to Philippe for information.
Markers already got generated when cancel is hit. The time is in the task list updating. Deferring, we would have to change the Java builder to work-around a slow task view.
Closing, number has been reduced when classpath is broken, max problem per unit is also in. Last: task list can cope with large number of problems and will refuse to show them all.
closing
Closed
Verified
