Bug 564449 - Setting compiler compliance to 14 corrupts the workspace
Summary: Setting compiler compliance to 14 corrupts the workspace
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.17   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2020-06-18 19:48 EDT by Denis Molony CLA
Modified: 2022-07-30 11:27 EDT (History)
2 users (show)

See Also:

Attachments
workspace before the upgrade (26.03 MB, application/octet-stream)
2020-06-18 23:54 EDT, Denis Molony CLA 		no flags Details
View All 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 Denis Molony CLA 2020-06-18 19:48:29 EDT 
I have just installed 20-06 java developers version. Once the workspace is upgraded, everything works fine. But changing the compiler compliance to 14, rebuilding and restarting causes the workspace to become corrupted. No source files can be found, and the project explorer displays all my projects as folders. They cannot be opened.
Comment 1 Manoj N Palat CLA 2020-06-18 23:40:34 EDT 
Can you please attach a reproducible workspace (ideally a smaller version)? Is this happening in a new workspace as well?
Comment 2 Denis Molony CLA 2020-06-18 23:54:51 EDT 
Created attachment 283351 [details]
workspace before the upgrade
Comment 3 Andrey Loskutov CLA 2020-06-19 01:22:20 EDT 
Please attach error log too.
Comment 4 Denis Molony CLA 2020-07-21 07:13:20 EDT 
I sent you a workspace before the error. There is no error log.
Comment 5 Eclipse Genie CLA 2022-07-30 11:27:19 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.