Bug 543517 - PDE project settings inconsistent
Summary: PDE project settings inconsistent
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.11   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Andrey Loskutov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-17 03:30 EST by Andrey Loskutov CLA
Modified: 2019-05-14 02:50 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Loskutov CLA 2019-01-17 03:30:21 EST
While patching PDE for bug 543490 I've noticed that organize imports automatically replaced almost all imports with *, and curly braces were automatically added for all if/else statements.

This made the original diff for https://git.eclipse.org/r/135175 3x bigger as the actual, adding a lot of noise, so I had to manually revert all the automated changes to have a clean patch.

The first problem is because we have org.eclipse.jdt.ui.ondemandthreshold=3 set in PDE settings, but this seem never be consistently used.

I've searched my workspace and I see that from 99 projects I have opened in platform, 26 use "3" and 73 projects use "99" as limit.

From 28 PDE projects 11 use "3", 3 projects use "5" and the rest uses workspace default (99).

Also looks like the code was never managed according to the settings, so even if the project says "3", some imports were added with "99" and so this leads to unexpected "automated" edits on save.

Same is for "convert control statement bodies to block" - it is set in PDE core but not in the UI, and the code uses a funny mix of both styles.

So I think we should harmonize this and use 99 / "convert control statement bodies to block" everywhere. This is also workspace default setting.

I propose to do this in two shots: organize imports / add braces around if/else.

I plan to provide patches.
Comment 1 Eclipse Genie CLA 2019-01-18 12:14:19 EST
New Gerrit change created: https://git.eclipse.org/r/135344
Comment 3 Vikas Chandra CLA 2019-02-18 00:52:08 EST
Should this be in resolved state?
Comment 4 Andrey Loskutov CLA 2019-02-18 02:25:49 EST
(In reply to Vikas Chandra from comment #3)
> Should this be in resolved state?

I plan to submit more patches. Since they aren't functional code changes, may be I will be able to do this for 4.11.
Comment 5 Lars Vogel CLA 2019-02-19 03:31:34 EST
Mass change, please reset target if you still planning to fix this for 4.11.