Bug 439161 - Problem markers no longer displayed in editor annotations after PTP installation.
Summary: Problem markers no longer displayed in editor annotations after PTP installat...
Status: REOPENED
Alias: None
Product: PTP
Classification: Tools
Component: Photran.Problems View & Error Markers (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Photran Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2014-07-08 14:12 EDT by Bruno Medeiros CLA
Modified: 2014-07-24 08:29 EDT (History)
1 user (show)

See Also:


Attachments
Editor annotations that are no longer displayed missing. (119.46 KB, image/png)
2014-07-08 14:12 EDT, Bruno Medeiros CLA
no flags Details
Bug example after installing PTP (50.49 KB, image/png)
2014-07-08 14:18 EDT, Bruno Medeiros CLA
no flags Details
Bug example before installing PTP (46.99 KB, image/png)
2014-07-08 14:22 EDT, Bruno Medeiros CLA
no flags Details
log file after PTP installation. (1.47 KB, application/octet-stream)
2014-07-09 11:56 EDT, Bruno Medeiros CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Medeiros CLA 2014-07-08 14:12:59 EDT
Created attachment 244897 [details]
Editor annotations that are no longer displayed missing.

This problem manifests itself in the UI, but I believe it is related to the runtime, OSGi, p2, or something similar.

A short description of the problem is: After installing the Parallel Tools Platform, the file resource errors/problems are no longer displayed as annotations in "Vertical ruler" and the "Overview ruler" of any editor opened on the respective file.
Note that if the "org.eclipse.osgi" directory is deleted from the Eclipse configuration folder, and Eclipse is started, the problem will be gone. This seems to indicated that "org.eclipse.osgi" has become outdated or corrupted in some way after installation. (this is why I also don't think this bug is related to PTP)
Comment 1 Bruno Medeiros CLA 2014-07-08 14:18:09 EDT
More detailed steps to reproduce:

=== First part: creating a resource error marker on the workspace.
This first part could be vastly simplified, but its the only way I have for now to reproduce. The objective is simply to create a file resource error marker on the workspace.

* Download the Eclipse platform.
* Install the GoClipse IDE as described here: https://github.com/GoClipse/goclipse/blob/latest/documentation/Installation.md#installation
* You'll also need to install a Go compiler (http://golang.org/doc/install) and set the GOROOT preference page setting of GoClipse to that Go compiler location.
* Set GOPATH to any directory.
* Create a new Go project.
* Create a new_file.go in the "src" folder. Set the file to some invalid contents, such as:
------- new_file.go:
package main 

func main() {
  asdfasd asdfsdf
}
------
* Build the workspace.
Now an error should be created, and it will be displayed in the "Vertical ruler" and the "Overview ruler" of the Go editor (as well as in the built in text editor)

=== Second part: 
Install Parallel Tools Platform from Luna. Restart.
Now the resource error no longer is displayed "Vertical ruler" and the "Overview ruler" of the Go editor (or any other editor).

See "AnnotationsBug.after.png" attachment for example.
Comment 2 Bruno Medeiros CLA 2014-07-08 14:18:51 EDT
Created attachment 244898 [details]
Bug example after installing PTP
Comment 3 Bruno Medeiros CLA 2014-07-08 14:22:23 EDT
Created attachment 244899 [details]
Bug example before installing PTP
Comment 4 Paul Webster CLA 2014-07-08 21:41:30 EDT
Can you please attach your error log?  <workspace>/.metadata/.log

PW
Comment 5 Bruno Medeiros CLA 2014-07-09 11:56:27 EDT
Created attachment 244936 [details]
log file after PTP installation.

It doesn't have much info though.
Comment 6 Bruno Medeiros CLA 2014-07-09 12:16:24 EDT
If it might help, here's a complete Eclipse installation after the steps above, it should be enough to replicate the bug (it does on my machine):
https://docs.google.com/file/d/0B8dnhT_E1D_2bm42cnZwdlBLNVE
(open it on the workspace included in the zip - Go compiler installation should not be necessary)

I couldn't attach it to the bugzilla cause it exceeds the file limits.
Comment 7 Dani Megert CLA 2014-07-23 08:46:56 EDT
Are the markers also gone for Java files in the Java editor?
Comment 8 Bruno Medeiros CLA 2014-07-24 06:44:27 EDT
No, the editor annotations for Java Problems are still displayed in the Java editor. 

Even if I force the Java file to be opened with the Go editor, the Java Problems annotations will be displayed. But if I open the Go file (with the Go problems), with the Java editor, the editor annotations for the Go problems will not be displayed.
Comment 9 Dani Megert CLA 2014-07-24 06:47:02 EDT
(In reply to Bruno Medeiros from comment #8)
> No, the editor annotations for Java Problems are still displayed in the Java
> editor. 
> 
> Even if I force the Java file to be opened with the Go editor, the Java
> Problems annotations will be displayed. But if I open the Go file (with the
> Go problems), with the Java editor, the editor annotations for the Go
> problems will not be displayed.

This looks like a bug in GoClipse.
Comment 10 Bruno Medeiros CLA 2014-07-24 08:21:10 EDT
It's not a GoClipse bug.

I've found an alternative way to manifest this bug, which doesn't involve GoClipse, but instead uses PDE only:

* Download Eclipse Standard
* Start Eclipse, create a new PDE plugin project.
* Open the MANIFEST.MF file, write some syntax garbage there. (an error marker will be created, and displayed in the editor annotation ruler)
* Install Parallel Tools Platform from Luna. Restart.
* The error annotation is no longer displayed in the manifest editor (or the text editor): http://i.imgur.com/oapSCRN.png

Just as the GoClipse case, uninstalling PTP, or deleting the "org.eclipse.osgi" directory from the Eclipse configuration directory (and restarting) will make the bug state disappear (the error editor annotations appear again).
Comment 11 Dani Megert CLA 2014-07-24 08:29:54 EDT
(In reply to Bruno Medeiros from comment #10)

Thanks for those steps. Moving to PTP since obviously they somehow damage it.