Community
Participate
Working Groups
While starting to run our tests for Gerrit changes, we got two test failures which were caused by the missing 'org.eclipse.core.runtime.compatibility' bundle. I replaced the deprecated code that caused the failures, but we have to investigate whether other stuff is used from the compatibility layer.
Sarika, we should do this for RC1, so that we can delete the compatibility layer in 4.6.
(In reply to Dani Megert from comment #0) > I replaced the deprecated code that caused the failures, Fixed with http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=2bf6c75a08a17ddbaac9a876567e4177431def84
Sarika, we have to do this during RC2, see comment 1.
There is no reference in any java file but the test launch file has an entry like this : <stringAttribute key="selected_target_plugins" value="org.eclipse.core.runtime.compatibility.registry@default:false, Does the gerrit test use the same launch file to run the tests ? /org.eclipse.jdt.debug.tests/JDT Debug Test Suite.launch
(In reply to Sarika Sinha from comment #4) > There is no reference in any java file but the test launch file has an entry > like this : > <stringAttribute key="selected_target_plugins" > value="org.eclipse.core.runtime.compatibility.registry@default:false, > > Does the gerrit test use the same launch file to run the tests ? > > /org.eclipse.jdt.debug.tests/JDT Debug Test Suite.launch No, Gerrit executes the org.eclipse.jdt.debug.tests.AutomatedSuite.
Created attachment 253577 [details] Removed reference from saved test run configuration file
(In reply to Sarika Sinha from comment #6) > Created attachment 253577 [details] [diff] > Removed reference from saved test run configuration file Submitted with http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=98047d2b151cb5922421fdfd06b27fed5ceba2f6
Verified that we don't use any deprecated method which will invoke Compatibility layer.