Community
Participate
Working Groups
This clears the output directory, rebuild everything. Is unacceptable loss of time if you work on large projects, which I do. I observed this behavior in eclipse-SDK-3.1RC3. This was not a problem in 3.1 M5a.
This happens once the machine date changes. So if you closed the project and opened it the next day, it rebuilds.
Kent - pls investigate. Isn't this simply a consequence of build state (with timestamp addition) to have been changed ? If so, then this should only occur once ever.
Additional usecase: Build Automatically is enabled. You have more than one project open in workspace. In the property of the project, at Java Build Path, exclude some packages on one project. Save the project. Observe that the whole workspace is rebuild, even project that have no dependencies to the one that was changed.
Please provide a reproduceable testcase for your last comment. As for rebuilding a project when it is opened -> we have to since it has not seen any changes since it was closed. If this did not happen in a previous milestone, then it was a bug which has been fixed.
Consider working on five projects, each with 5000+ Java files. The delay to start working is immense. I think this is a bug – the project/workspace should refresh and build, only if resources have changed. Not because “system time” has changed. This was the behavior in the earlier release.
Why are you closing projects frequently? Or do you mean starting up your workspace? If so, then we need a reproduceable testcase since it does not happen to us.
Opening and closing project multiple times during a day is a common IDE use case. Starting the workspace the next day, if your projects were open also results in the similar "rebuild". I have already mentioned additional two use- cases to ease the process.
"Opening and closing project multiple times during a day is a common IDE use case." No its not. Every time you close a project, its the same as if you deleted it from your workspace. When you reopen it, its the same as importing a new project. We need reproduceable testcases that show the other problems you are describing. Please reopen this PR when you attach the testcases.
“Every time you close a project, its the same as if you deleted it from your workspace.” This is wrong approach. Unless you close (and optionally export for backup) and delete the project, it is not termed or treated as deleted. Note that there is a separate action for deleting a project. If you have around two project of 5000 files each, closing one of the project reduces the warnings/errors on the Problem view window and JVM memory usage as well. That is the reason you "must" be allowed to close the project multiple time – which is in sync with Eclipse3.1M5a. Additional observation: Do not close the project and shutdown the Eclipse IDE. Next day start the Eclipse IDE and try to launch an Application (running it) via IDE. The process immediately cleanups the output directory and workspace is rebuild. Therefore, something in the code is triggering the output directory cleanup, when it should not.
Please attach repeatable testcases to demonstrate full builds on startup. As for how close & open projects behave, its been the same for years. If a milestone had a bug that did not rebuild the project, that's irrelevant. It was a bug that has since been fixed.
This bug is (somehow) fixed in 3.1RC4
Closing...
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
