Community
Participate
Working Groups
In the process of installing and setting up 3.2RC1 I created a new file association; *.pro for ProGuard configuration files. It accepts this new file extension but when I attempt to add a default editor for these files I cannot. Pressing the Add button produces no effect. Selecting another extension (which populates the list of Assocated editors) and pressing the Add button also produces no effect.
I assume you are using the File Associations preference page to do this, correct? I tried adding a file association there and it works for me in RC1. Is there a stack trace in the .log file (see Error Log view, also) that appears to be related?
Created attachment 39707 [details] Eclipse log of a failed editor selection for a new file extension
(Yes, I am using the File Association preference page) I've attached the log file. It gets created specifically as a direct result of my clicking the Add button, I watched the file system from start up through the addition of the new file association through pressing the Add button. This is a fresh install of 3.2RC1 with Callisto RC1a. There are only three other plugins loaded to this installation (Mylar 0.5.0), jpedal's PDF viewer and yWork's ant visualizer. None of these three plugins have caused any such problems on my previous 3.1.2 installation of Eclipse. So I am presuming that it's in the beta software. I'm happy to investigate further, just let me know.
From the stack trace it looks like JFace is trying to load the image (of one of the associated editors) and is failing because the format of the image for one of the associated editors is not supported or recognized. The org.eclipse.ui.workbench.prefs file (in .metadata\.plugins\org.eclipse.core.runtime\.settings) should have all your file associations and associated editors in it. There's an image in your list (either internal or external) of associated editors that uses the incorrect format.
So I ran through and disabled all the features/plugins via the Product Configuration configuration screen (Help > Software Updates > Manage Configuration). Then, arduously, one by one, I re-eanbled each and checked the File Associations Add button (for the Associated editor). It turns out that I can reproduce this problem by enabling and disabling: Data Tools Platform SQL Development Tools 0.9.0.200604141 So how would you like to see this bug dispositioned?
Directing to Data Tools Product - looks like there is a bad icon somewhere in the DTP stuff.
I believe this has already been fixed in the RC2 stream. Will verify and update this entry.
This is fixed in DTP 0.9RC2 (Callisto RC2).
See also BZ#136482
Closing bugs
