Bug 526275 - [9] prevent adding modular JRE System Library to the classpath
Summary: [9] prevent adding modular JRE System Library to the classpath
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.1a   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-19 12:40 EDT by Stephan Herrmann CLA
Modified: 2017-10-20 05:47 EDT (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 Stephan Herrmann CLA 2017-10-19 12:40:48 EDT 
Since bug 520300, users have to decide whether they add a library to Modulepath or Classpath. For a modular JRE System Library (9+) it does not make sense to add it to the Classpath (which behind the scenes, invisibly, actually does the right thing: add to Modulepath).

Questions:

At what point to disable? Add Library is a multi-step process, and I'm not sure we still "know" whether classpath or modulepath is targeted at the point when the library version is selected.

How we can signal to the user, what's the problem and what should be done instead?

See also bug 526270 comment 5