Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CDT/Obsolete/APIBreakages
< CDT | Obsolete
Revision as of 13:12, 9 March 2015 by Marc.khouzam.gmail.com (Talk | contribs) (→Proposed API-breaking changes)
CDT 9.0
This page is attempt to collect possible API breaking proposals for next CDT release
Proposed API-breaking changes
- Remove all methods, interfaces and classes that have been deprecated since CDT 8.2.0 and are not currently used in CDT code.
- Improves readability
- Reduces maintenance
- Could be contributions from a hackathon
- Suggested rules (not mandatory): something deprecated for around 2 years and not used by CDT itself
- Delete CDI plugins
- Cleaning up old build stuff
- Cleanup old-style project
- Our tests still use old-style and migrating them is not trivial
- Old scanner discovery (Language setting provider)
- Rewrite error parsers to use a better regex library (java.regex.Pattern is part of API now) because build is horribly slow from IDE stricltly because of error parsers.
- Rewrite ui for debug tabs, all current ui controls are APIs...
- Switch to java 1.8
- Extract CDI so that it does not have to be installed by default
Proposed process
- Select an API-breaking change to work on
- Estimate the impact (code changes) of the change on the APIs
- Communicate that impact to the cdt-dev list to notify possible impacted parties