Community
Participate
Working Groups
I20070213-0907 Each time I start up my dev workspace where all binary plug-ins are imported and no PDE projects are selected, the JDT Core trace shows that jdt.ui has a delta and needs to be built incrementally. Found source delta for: org.eclipse.jdt.ui Clearing last state : State for org.eclipse.jdt.ui (#1 @ Tue Feb 20 18:14:04 CET 2007) INCREMENTAL build Recording new state : State for org.eclipse.jdt.ui (#2 @ Tue Feb 20 18:14:04 CET 2007) Finished build of org.eclipse.jdt.ui @ Wed Feb 21 10:01:27 CET 2007 jdt.ui is the only project where that happens. Q: why is the timestamp on 'Recording new state' the old one? NOTE: this is not a major issue as this incremental build happens very quickly.
So, just to demonstrate the issue: the next time I start up it says: Found source delta for: org.eclipse.jdt.ui Clearing last state : State for org.eclipse.jdt.ui (#2 @ Tue Feb 20 18:14:04 CET 2007) INCREMENTAL build Recording new state : State for org.eclipse.jdt.ui (#3 @ Tue Feb 20 18:14:04 CET 2007) Finished build of org.eclipse.jdt.ui @ Wed Feb 21 10:10:06 CET 2007
Created attachment 59456 [details] Complete debug log
This might be related to the correction of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=172444
(In reply to comment #3) after further investigation, bug 172444 seems unrelated
Dani, the naive tests I ran could not reproduce your problem. Do you still see it? If yes, could you please give me more details? My answer to the question 'why is the timestamp on 'Recording new state' the old one?' would be that the time we see there is the time of the last structural build, which is only affected when something changes in dependencies, if I got it well. In other words, it is not expected to reflect the last time the builder changed something (which could be considered as the 'latest significant build'), but the last time a higher order build happened. The build states bear a build number that provides further information, which shows up as #1, #2 etc. in the trace. What I could not tell you without reproducing the test case is: - whether the delta we see in the trace is right or wrong; presumably, if you're in autobuild, and you get it just because you restart, it should be wrong; - whether the fact that it results into a new version of the build state to happen is right or wrong; questions here are around the delta bearing significant changes or not, and really resulting in output changes or not. Kent, any comments?
> if >you're in autobuild, and you get it just because you restart, it should be >wrong; As the test cases starts with a fresh workspace auto-build is on. Could it be possible that the saved build state is locale dependent?
(In reply to comment #6) > Could it be possible that the saved build state is locale dependent? Do you mean that changing the locale is part of the scenario? I haven't the slightest idea for now, but this may be - I am not sure that access rules messages don't go there for example. I will check. Kent, do you have the answer at hand?
>Do you mean that changing the locale is part of the scenario? No.
>As the test cases starts with a fresh workspace auto-build is on. Sorry I had a the full build on start bug in mind when I wrote this. But yes, auto-build is on. Let me check whether I still see the bug with the latest build.
I can no longer reproduce using I20070327-0800. I get the trace below. OK to close. java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode) Install location: file:/c:/eclipse/drops/I20070327-0800/ Configuration file: file:/c:/eclipse/drops/I20070327-0800/configuration/config.ini loaded Configuration location: file:/c:/eclipse/drops/I20070327-0800/configuration/ Framework located: file:/c:/eclipse/drops/I20070327-0800/plugins/org.eclipse.osgi_3.3.0.v20070326.jar Framework classpath: file:/c:/eclipse/drops/I20070327-0800/plugins/org.eclipse.osgi_3.3.0.v20070326.jar Debug options: file:/C:/eclipse/drops/I20070327-0800/.options loaded Time to load bundles: 70 Starting application: 2995 Application Started: 18537
Thx for checking. Closing as WORKSFORME.
Already verified for 3.3M7. See comment 10.
