Bug 529606 - When opening a .java file from a non-JDT project with JDT editor, propose to configure project
Summary: When opening a .java file from a non-JDT project with JDT editor, propose to ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2018-01-10 03:10 EST by Mickael Istria CLA
Modified: 2018-01-11 08:10 EST (History)
2 users (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 Mickael Istria CLA 2018-01-10 03:10:34 EST 
As a Java developer
When I open a .java file in Eclipse IDE from a project I already have in workspace.
I'd expect JDT to configure the project at best to be usable
I get messages telling that the .java file is not part of the build path and poor completion/features.

In this case, I'd love to see a pop-up: "Project <blah> is not configured for rich Java edition. Do you want to configure it now?" that would drive me to most appropriate UI to configure the project.