| Summary: | The model importer plug-ins should be independent of the Eclipse resource API | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Adam Cabler <acabler> |
| Component: | Tools | Assignee: | Marcelo Paternostro <marcelop> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Ed.Merks, marcelop |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Adam Cabler
Probably this means we should allow the path to be specified using platform:/resource/... otherwise I'm not sure how we can distinguish file system relative from workspace relative. Does a platform:/resource path not work today? *** Bug 101162 has been marked as a duplicate of this bug. *** Sorry, just saw this. No, a platform:/ path does not work. This seemed the obvious approach to me as well. (In reply to comment #1) > Probably this means we should allow the path to be specified using > platform:/resource/... otherwise I'm not sure how we can distinguish file > system relative from workspace relative. Does a platform:/resource path not > work today? > I am moving setting this as a feature request. When the model importer plug-ins (and Ant tasks) were created, we had the idea that code generation would always be handled in an Eclipse environment. Since them, the actual generation code has changed to support stand-alone and other environments. So, better than patching the existing code, I am changing this request to a more ambitious goal: refactor the existing importer plug-ins to be platform (and workspace) independent. The basic idea is to adopt the same design principals that were used in the converter and exporter plug-ins: everything should be URI based, falling back to things like IPath and IResource only when necessary. It doesn't appear we can do such refactoring in an API preserving way so I'll close this as won't fix. |