Bug 507815 - Cleanup PDE code warnings
Summary: Cleanup PDE code warnings
Status: CLOSED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Karpisek CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 246590 275738 351475 390980 484246 507831 507971 508140 509041 510829
Blocks:
  Show dependency tree
 
Reported: 2016-11-19 16:53 EST by Martin Karpisek CLA
Modified: 2018-06-17 15:52 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 Martin Karpisek CLA 2016-11-19 16:53:58 EST
Cleanup PDE code warnings

This bug is to propose patches for reducing amount of warnings in current PDE codebase 
(for all pde projects, which seems to be currently ~ 1126 warnings)
Target would be to make more easy further bugfixing and contributing (while removing basic issues first).

Proposed steps:
- fix deprecated java code
- generify where possible (warnings are mostly in runtime)
- fix javadoc problems found (bug 275738)
- replace non-javadoc comment with @override annotation => enable save action for missing code annotations
- introduce foreach loop for iterating over arrays (instead of clasic for)
- increase all PDE plugins to be execution environment=1.8 (if not some issue to raise minimal requirements) 
	currently launching=1.7, ua.core=1.4, ua.test=1.5, ui.trace=1.5, otherwise all are 1.8
- fix deprecated extension points usage (where possible, part of it is to address also bug 246590 and bug 390980)

Proposed approach: 
- i would prepare patches for steps above one by one during remaining 4.7 timeframe (as time permits)
- scope of this bug is cleanup - which would be easy to review - not rewrite or change of functionality
- for each item above i would create separate bug and relate to this umbrella one  
- each cleaned-up project would have own patch (gerrit review) for the fixed kind of problem

Please review and comment, especially approach above (to make it easy for review).
Comment 1 Lars Vogel CLA 2016-11-20 01:58:42 EST
+1 for the approach
Comment 2 Lars Vogel CLA 2018-06-15 03:26:00 EDT
Martin, are you still around or shall we close this bug?
Comment 3 Martin Karpisek CLA 2018-06-17 15:52:02 EDT
closing bug as suggested in comment #2, no further work on it expected