Bug 362979 - Inconsistent JavaVMTypes URI resolution
Summary: Inconsistent JavaVMTypes URI resolution
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-06 03:10 EST by Ed Willink CLA
Modified: 2012-04-09 15:16 EDT (History)
1 user (show)

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 Ed Willink CLA 2011-11-06 03:10:05 EST 
If an Xtext file references

import "http://www.eclipse.org/xtext/common/JavaVMTypes" as types

and its manually generated model also references

http://www.eclipse.org/xtext/common/JavaVMTypes#//JvmType

then the Xtext editor reports an incompatible feature.

If however the manually generated model references 

../../org.eclipse.xtext.common.types/model/JavaVMTypes.ecore#//JvmType

the problem goes away.

I was working around this problem by importing org.eclipse.xtext.common.types till some new genmodel problem needed investigating.

Surely both

../../org.eclipse.xtext.common.types/model/JavaVMTypes.ecore

and 

http://www.eclipse.org/xtext/common/JavaVMTypes

should resolve URIs via

platform:/plugin/org.eclipse.xtext.common.types/model/JavaVMTypes.ecore

ensuring that both use the same normalized URI and so avoid the metamodel schizophrenia.