Bug 429559 - [1.8] Remove tweaks for javac bug-compatibility
Summary: [1.8] Remove tweaks for javac bug-compatibility
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 420045 429490
Blocks: 564617
  Show dependency tree
 
Reported: 2014-03-04 06:21 EST by Stephan Herrmann CLA
Modified: 2022-08-17 05:00 EDT (History)
3 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 2014-03-04 06:21:07 EST 
Umbrella bug to remind us to remove our tweaks that have been implemented for the sole purpose of being compatible with javac in what is perceived as a bug in javac.
Comment 1 Stephan Herrmann CLA 2014-03-04 06:28:03 EST 
Marked existing bugs as dependencies (or should I actually add my entries to bug 420045?)


Some tweaks with no bug of their own, currently:

InferenceContext18
 - SIMULATE_BUG_JDK_8026527
 - ARGUMENT_CONSTRAINTS_ARE_SOFT


Put on radar for 4.4, but actual time line depends on what javac team decides.
Comment 2 Manoj N Palat CLA 2018-05-16 01:38:09 EDT 
Bulk move out of 4.8
Comment 3 Eclipse Genie CLA 2020-06-22 09:53:29 EDT 
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.
Comment 4 Eclipse Genie CLA 2022-08-17 05:00:41 EDT 
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.