Community
Participate
Working Groups
Build Identifier: 20100917-0705 Hi there, I'm using Xtext 1.0.1 and I've noticed the following issue: The built-in exporting services for Ecore (org.eclipse.xtext.ecore) export simple instead of qualified names - which is bad. Imagine you have an EPackage "model" containing an EEnum "Direction" containing an EEnumLiteral "left". The name exported for the literal is "left" but it should be "model.Direction.left" to reflect the hierarchy and to avoid name clashes. The error is critical because the scoping of Xtext removes duplicate names (all occurences) so that some attribute or reference named "left" leads to a model with elements that may not be referenced from outside. Reproducible: Always Steps to Reproduce: 1. Create two ENamedElements with the same name 2. Simple name export leads to duplicate names 3. Scoping removes duplicates completely 4. Elements may not be referenced
We want to export all ENamedElements twice: http://nsURI | EClassName | EStructuralFEatureName -> userData nsURI=true EPackageName | EClassName | EStructuralFeatureName -> userData nsURI=false
Pushed to MASTER. EOperations are indexed with their name, too.
Closing all bugs that were set to RESOLVED before Neon.0