Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. Select a problem in the Problems view and hit Delete. 2. Click "Yes" to confirm Nothing happens. It doesn't seem to matter whether Build Automatically is on or off. More information: Nothing happens whatsoever; the marker remains. Nothing in the Error Log either. (As I understand, this was to be the solution to bug #136337, so it seems that bug is no longer fixed.)
This works for me. I simply selected one of our warning elements and deleted (clicked Yes). I'm running on M20080813-0800, one of the maintenace builds towards 3.4.1 Could you please download a recent maintenance build and post the steps when you try and reproduce it? You are looking for a "3.4.1 Stream Build" on http://download.eclipse.org/eclipse/downloads/ PW
If the marker failed deltion due to a CoreException we will not have deleted it from the view. Which type of marker were you trying to delete? This works with the markers generated by the JDT framework.
(In reply to comment #2) > If the marker failed deltion due to a CoreException we will not have deleted it > from the view. Which type of marker were you trying to delete? This works with > the markers generated by the JDT framework. I tried it both with JDT markers and with validator markers (XML schema violations, IIRC).
(In reply to comment #1) > This works for me. I simply selected one of our warning elements and deleted > (clicked Yes). I'm running on M20080813-0800, one of the maintenace builds > towards 3.4.1 > > Could you please download a recent maintenance build and post the steps when > you try and reproduce it? > > You are looking for a "3.4.1 Stream Build" on > http://download.eclipse.org/eclipse/downloads/ > > PW Tried it on 3.4.1 M20080813-0800, and now marker deletion works. Also tried on a clean instance of the released 3.4, and the bug was still there. (Same workspace in both cases.) So it looks like this has been fixed.
I didn't notice that you are on Linux. This is Bug 241384. Sorry I didn't figure it out earlier. *** This bug has been marked as a duplicate of bug 241384 ***