Community
Participate
Working Groups
For 4.2 I needed to move org.eclipse.ui.testing package from org.eclipse.ui.workbench to org.eclipse.e4.ui.workbench3. I now export that package from org.eclipse.e4.ui.workbench3, consume it in o.e.ui.workbench, and re-export it. I up'ed the minor number for those 2 bundles + o.e.ui which re-exports workbench. I have an API baseline of 4.1.0. This leads to about 22 errors, see the end of the bug for a cross-section. So I right-click and create a problems filter for them. That creates /org.eclipse.e4.ui.workbench3/.settings/.api_filters. But all 22 problems are still in the problems view after the build, even after I completely clean and rebuild my workspace. You can see my state along with the api filter at: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/log/?h=pwebster/bug363334 example: Description Resource Path Location Type The re-exported type org.eclipse.ui.testing.ContributionInfo in org.eclipse.ui_3.7.100 is no longer API ContributionInfo.java /org.eclipse.e4.ui.workbench3/src/org/eclipse/ui/testing line 21 Compatibility Problem Description Resource Path Location Type The re-exported type org.eclipse.ui.testing.ContributionInfo in org.eclipse.ui.workbench_3.103.0 is no longer API ContributionInfo.java /org.eclipse.e4.ui.workbench3/src/org/eclipse/ui/testing line 21 Compatibility Problem Description Resource Path Location Type The type org.eclipse.ui.testing.ContributionInfo in org.eclipse.e4.ui.workbench3_0.12.0 is no longer API ContributionInfo.java /org.eclipse.e4.ui.workbench3/src/org/eclipse/ui/testing line 21 Compatibility Problem
I switched back to master and did a complete clean>rebuild of my workspace. The 22 errors did not go away. Restarting eclipse also did not get rid of the problems. PW
If I disable auto-build and delete the markers from the Problems view, they don't come back on a rebuild. PW
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.
