Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CDT/Obsolete/APIBreakages"

< CDT‎ | Obsolete
(CDT 9.0)
(Proposed API-breaking changes)
Line 5: Line 5:
 
=== Proposed API-breaking changes ===
 
=== 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.
 
# 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 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...
 
# Rewrite ui for debug tabs, all current ui controls are APIs...

Revision as of 13:12, 9 March 2015

CDT 9.0

This page is attempt to collect possible API breaking proposals for next CDT release

Proposed API-breaking changes

  1. 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)
  2. 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.
  3. Rewrite ui for debug tabs, all current ui controls are APIs...
  4. Switch to java 1.8
  5. Extract CDI so that it does not have to be installed by default

Proposed process

  1. Select an API-breaking change to work on
  2. Estimate the impact (code changes) of the change on the APIs
  3. Communicate that impact to the cdt-dev list to notify possible impacted parties

Back to the top