Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367013 - Spurious "The imported package is not on the classpath of this project which may lead to follow up errors."
Summary: Spurious "The imported package is not on the classpath of this project which ...
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.2.1   Edit
Hardware: PC Windows Vista
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-17 12:18 EST by Ed Willink CLA
Modified: 2013-12-04 06:54 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 Ed Willink CLA 2011-12-17 12:18:46 EST 
Xtext 2.2.1 reports "The imported package is not on the classpath of this project which may lead to follow up errors." unless the package is in an explicitly imported package. It fails to consider exported packages from the closure of imported packages.
Comment 1 Ed Willink CLA 2013-07-06 02:26:40 EDT 
Finally found out what the cause of this confusing message is:

Xtext now requires all referenced packages in open projects to have an Xtext nature.

Therefore where this requiirement is violated please use the alternative message (and quick fix).

"The imported package does not have the Xtext nature."