Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 162445

Summary: The model importer plug-ins should be independent of the Eclipse resource API
Product: [Modeling] EMF Reporter: Adam Cabler <acabler>
Component: ToolsAssignee: 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 CLA 2006-10-26 12:56:40 EDT
When using emf.XSD2Java, the ant task model path only takes a file system relative or absolute path.  In order for the generated code to work in deployment, the task must take a platform relative path.  If not, the runtime will be unable to find the schemas.
Comment 1 Ed Merks CLA 2006-10-26 13:10:27 EDT
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?
Comment 2 Ed Merks CLA 2006-10-27 05:47:40 EDT
*** Bug 101162 has been marked as a duplicate of this bug. ***
Comment 3 Adam Cabler CLA 2007-01-09 18:50:54 EST
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?
> 

Comment 4 Marcelo Paternostro CLA 2008-02-01 12:24:11 EST
I am moving setting this as a feature request.
Comment 5 Marcelo Paternostro CLA 2008-02-01 12:28:51 EST
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.
Comment 6 Ed Merks CLA 2012-10-04 10:49:43 EDT
It doesn't appear we can do such refactoring in an API preserving way so I'll close this as won't fix.