Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 28581 - File association to external programs other than *.exe
Summary: File association to external programs other than *.exe
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-17 17:28 EST by Mark Edwards CLA
Modified: 2003-01-02 09:53 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Edwards CLA 2002-12-17 17:28:54 EST 
Eclipse not allowing the file association to be made to anything except .exe 
files. There might be cases when developers would prefer to use an external 
program other than exe, for example java.  Example: Tea template editor Kettle 
4.0.3 runs as java process sing command line:
java -cp .\Kettle.jar com.go.kettle.Kettle %1
It would be nice to have an option to associate *.tea files with Kettle in the 
Eclipse Workbench.
Comment 1 Sonia Dimitrov CLA 2002-12-18 09:28:05 EST 

*** This bug has been marked as a duplicate of 22752 ***
Comment 2 Mark Edwards CLA 2002-12-19 22:28:31 EST 
Thank you for pointing to the 22752 bug report. That bug does sound like this 
same request. It says it was fixed in 2.0 in September. However I am using 
Eclipse Platform 2.0.2.1 with build id 200211071448 and when I go to the File 
Association preference page and select External Program on the Editor Selection 
page and then click on Browse, the Browse dialog only offers *.exe as the file 
filter. I can't associate anything other than an exe file. Am I missing 
something here? It appears that the fix mentioned in 22752 is not in the 
2.0.2.1 build?
Comment 3 Sonia Dimitrov CLA 2002-12-20 08:15:40 EST 
Assigning for comment by component owner.
Comment 4 Tod Creasey CLA 2003-01-02 09:53:02 EST 
This problem was fixed in the 2.1 stream in September. The problem was not 
deemed serious enough to make it into 2.0.2 which was a maintenance release 
for 2.0.