| Summary: | [Compatibility] 'launcher' attribute for editor extensions are not considered | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Olivier Thomann <Olivier_Thomann> | ||||
| Component: | UI | Assignee: | Remy Suen <remy.suen> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Remy Suen <remy.suen> | ||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | daniel_megert, remy.suen | ||||
| Version: | 1.0 | ||||||
| Target Milestone: | 4.1 M6 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Olivier Thomann
I can reproduce this problem. The workaround would be to open the 'JUnit' view first and then importing it from there. Our code doesn't take into IEditorLauncher implementations specified by the 'launcher' attribute so we end up trying to create a new editor (which fails). Another related problem is that there is no stack trace in the error log which makes it slightly less obvious where the problem is. We also need to correct this. This also breaks opening the JAR Export wizard. Created attachment 188130 [details]
External editor patch v1
(In reply to comment #4) > Created attachment 188130 [details] > External editor patch v1 Both issues contained in comment 2 has been addressed. Patch released to CVS HEAD. Thanks for the bug report, Olivier! Whoops. Verified in I20110204-0715. |