Bug 172649 - RSE must not use Platform "internal" API
Summary: RSE must not use Platform "internal" API
Status: ASSIGNED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.3.1   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 257397 257407 257408 172651 257398
Blocks: 170915
  Show dependency tree
 
Reported: 2007-02-02 07:31 EST by Martin Oberhuber CLA
Modified: 2011-05-31 17:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-02 07:31:42 EST
As per
http://www.eclipse.org/org/councils/20070123PCMinutes.php
the RSE must not use other project's "internal" (discouraged) API.

This applies to the Platform and CDT. Discouraged access should be removed wherever possible. This may mean getting rid of some RSE extension points for actions and property pages where they just duplicate Platform concepts for convenience.
Comment 1 Martin Oberhuber CLA 2007-02-02 07:42:44 EST
Consider a must-have for 2.0
Comment 2 Martin Oberhuber CLA 2007-02-07 09:56:23 EST
Platform "internal" access can be found easily by applying the following filter
in the Problems view:
Severity="Warning", Description contains="required library"

On 7-Feb-2007, we have the following kinds of Platform "internal" access:
* Illegal re-use of text, labels etc. from base Eclipse --> Copy&Paste to RSE
* Illegal re-use of stuff from Editor, Compare and Preference Pages
* Illegal use of CDT GDBDebuggerPage (in RemoteCDT)

Dave - can you analyze the situation with Editor and Compare, whether you see chances to get rid of the Platform "internal" access? - For CDT, I'm writing to the cdt-dev list.
Comment 3 Martin Oberhuber CLA 2011-05-31 17:38:37 EDT
Moving 3.3 cleanup items to 3.3.1