Bug 534032 - Add a warning access restriction on packages who will be removed with Java11
Summary: Add a warning access restriction on packages who will be removed with Java11
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2018-04-25 05:51 EDT by Thomas Schindl CLA
Modified: 2022-12-26 14: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 Thomas Schindl CLA 2018-04-25 05:51:58 EDT 
Java11 will remove the well known packages from the JRE:
* javax.annotation
* javax.xml.bind

To warn users about that I think we could add Access-Restriction warnings so that developers who that this API should not be accessed from the JRE but as an ordinary dependency eg via maven, ... .
Comment 1 Thomas Schindl CLA 2018-04-25 05:53:07 EDT 
Not sure maybe this belongs to debug, because it somehow has to do with the VM-Install
Comment 2 Dani Megert CLA 2018-04-25 10:03:55 EDT 
(In reply to Thomas Schindl from comment #0)
> Java11 will remove the well known packages from the JRE:
> * javax.annotation
> * javax.xml.bind
> 
> To warn users about that I think we could add Access-Restriction warnings so
> that developers who that this API should not be accessed from the JRE but as
> an ordinary dependency eg via maven, ... .

If we do this, we should cover everything that will be removed.

Not sure we have time for this.
Comment 3 Eclipse Genie CLA 2022-12-26 14:10:35 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.