Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346731 - Import statement enhancements
Summary: Import statement enhancements
Status: CLOSED WONTFIX
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 12:25 EDT by Lan Phan CLA
Modified: 2013-02-21 08:13 EST (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 Lan Phan CLA 2011-05-20 12:25:29 EDT 
Build Identifier: Eclipse 3.6.2

For Xpand/Xtend/Check editor, user must firstly provide import statements. Our program have a long list of import statements such as:
import X::Y;
import X::Y::Z;
import X::Y::Z::T;
import X::Y::Z::T::K;
...
Is it possible to provide better way below?
import X::Y::*;

Reproducible: Always
Comment 1 Karsten Thoms CLA 2011-08-22 15:41:24 EDT 
This won't be possible, sorry. Import statements are internally just handled like prefixes. If Xpand accesses some definition and could not resolve it from the local namespace, it tries to prefix all import statements until it can resolve it. There is no way to know about sub-namespaces.
Comment 2 Karsten Thoms CLA 2013-02-21 08:13:43 EST 
Bug resolved before Xpand 1.2 release date => Closing