| Summary: | Should show better error message if no or an unknown document type is declared | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Chris Wilson <chris+eclipse-101028> | ||||
| Component: | Mylyn | Assignee: | Project Inbox <vex.core-inbox> | ||||
| Status: | CLOSED MOVED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | florian | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Chris Wilson
(In reply to comment #0) Do you have a plug-in installed or in your workspace which provides the DTD? (see http://wiki.eclipse.org/Vex/UserGuide#Vex_Plug-in_Project:_Configure_your_own_XML_format) Vex can only open files if their DTD is configured, either by an installed plug-in that extends the extension point 'org.eclipse.wst.xml.vex.ui.doctypes', or by a Vex plug-in project in your workspace. The plug-ins 'org.eclipse.wst.xml.vex.dita' and 'org.eclipse.wst.xml.vex.doctbook' are examples for plug-ins that provide the configuration for a document type. I guess I don't have any plugin for this file type and don't have time to write one. It told me to file a bug report so that's what I did. It seems like a less than helpful way for VEX to fail. If a document is opened in Vex that has no document type declared or uses an unknown document type, Vex should display a special error message which describes this problem and gives a hint on possible solutions to the underlying problem: 1. add a doctype declaration to the document 2. configure the document type e.g. by creating a Vex Plug-in in your workspace Moved to Mylyn Docs Vex. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |