Community
Participate
Working Groups
I20190228-0300 (a 4.11 build). On each start JDT builder insists in "Touching project org.eclipse.e4.ui.workbench.swt due to external jar file change" Sometimes causing a longer build (auto-build on). It's also with that bundle I often have issues after Pulling from Git: the classpath gets corrupted and a referenced JAR is claimed to be missing. Test Case: Enable tracing for the Java builder with those options: org.eclipse.jdt.core/debug=true org.eclipse.jdt.core/debug/builder=true org.eclipse.jdt.core/debug/builder/stats= true NOTE: Due to bug 544887 you must also add -consolelog when starting Eclipse. 1. Start with new workspace 2. Clone platform.ui and import the project mentioned above NOTE: You need a JRE 8 installed for the project to compile 3. Exit 4. Start ==> it will say: Touching project org.eclipse.e4.ui.workbench.swt due to external jar file change and will trigger an unexpected build. You can exit and start again ==> same issue! The trace also shows this: JavaBuilder: New location: Classpath jar file C:\eclipse\drops\eclipse-SDK-I20190228-0300-win32-x86_64\configuration\org.eclipse.osgi\226\0\.cp\lib\annotations.jar != old location: Classpath jar file C:\eclipse\drops\eclipse-SDK-I20190228-0300-win32-x86_64\configuration\org.eclipse.osgi\226\0\.cp\lib\annotations.jar Both locations look exactly the same, at least when printed.
When exiting the workspace it does save the state: Saving build state for project org.eclipse.e4.ui.workbench.swt
OK, so, Touching project org.eclipse.e4.ui.workbench.swt due to external jar file change is correct because the files got rewritten (see below). However, the location did not change. This should be fixed in the trace output. The configuration gets rewritten because I used -Dosgi.clean=true removing that fixes the appearance of the bug. However, in my real workspace this should not happen because I have all bundles imported as binary plug-ins. Digging deeper I found the issue, see bug 544924.
Bulk Move Out of 4.13
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
