Community
Participate
Working Groups
20030107 with autobuild off the sequence - close a binary project (that your sources refer to) - reopen - build all takes 10 seconds because build results (correctly) in a no-op with autobuild off, after reopening the project you still get errors in the task list build all does not help you have to make a no-op change in a file and save it - this removes the errors but the whole thing takes 10x as much time
Please provide a more concrete example. Also note that a closed project must be rebuilt in full since some information is discarded when its closed, thus making it impossible to handle the close/reopen case optimally.
Moreover, when a project is closed, no indication is provided when it reopens in case it did change in the meantime on the file system. This is why we cannot trust a closed project to not have changed since last time we saw it.
strange, i cannot reproduce anymore (it's fast now in the autobuild-on case) the concrete example was 'close org.eclipse.core.update' (binary) in self hosting workspace (with all binary except for jdt.ui, jdt.ui.test, jdt.ui.tests.refactoring in source) if nothing can be done (and i cannot reproduce), then ok for me to close
Closing
