Jump to: navigation, search

Difference between revisions of "DTP Ganymede Resolving Discouraged Access Warnings"

(New page: ← Back to DTP Main Page ==Document Status== [8/24/07]: This document is a '''draft''' and '''should not''' be taken as offical until reviewed and app...)
 
Line 7: Line 7:
  
 
As described in the [[DTP_Ganymede_Project_Plan | DTP Ganymede Project Plan]], a main goal of DTP Ganymede is to resolve as many ''Discouraged Access'' warnings in the DTP code line as possible. The reasoning and general process for doing this is outlined in the [[DTP_Ganymede_Development_Guidelines | DTP Ganymede Development Guildlines]]. The purpose of this page is to collect specific information about how these ''Discouraged Access'' warnings will be resolved.
 
As described in the [[DTP_Ganymede_Project_Plan | DTP Ganymede Project Plan]], a main goal of DTP Ganymede is to resolve as many ''Discouraged Access'' warnings in the DTP code line as possible. The reasoning and general process for doing this is outlined in the [[DTP_Ganymede_Development_Guidelines | DTP Ganymede Development Guildlines]]. The purpose of this page is to collect specific information about how these ''Discouraged Access'' warnings will be resolved.
 +
 +
==Current Status==
 +
 +
A check of DTP HEAD at the beginning of August, 2007, reveals a large number of ''Discouraged Access'' warnings. Fortunately, the vast majority of these are within DTP itself. Since we have decided that DTP components can freely use code among themselves, this means that most of the ''Discouraged Access'' warnings are really not a problem. Hence, we only need to find a way of indicating, in project and/or plug-in meta-data, that no ''Discouraged Access'' warning should be registered for ''org.eclipse.datatools.*'' classes using ''org.eclipse.datatools.*'' code.

Revision as of 10:19, 24 August 2007

Back to DTP Main Page

Document Status

[8/24/07]: This document is a draft and should not be taken as offical until reviewed and approved by the DTP PMC and project leads.

Overview

As described in the DTP Ganymede Project Plan, a main goal of DTP Ganymede is to resolve as many Discouraged Access warnings in the DTP code line as possible. The reasoning and general process for doing this is outlined in the DTP Ganymede Development Guildlines. The purpose of this page is to collect specific information about how these Discouraged Access warnings will be resolved.

Current Status

A check of DTP HEAD at the beginning of August, 2007, reveals a large number of Discouraged Access warnings. Fortunately, the vast majority of these are within DTP itself. Since we have decided that DTP components can freely use code among themselves, this means that most of the Discouraged Access warnings are really not a problem. Hence, we only need to find a way of indicating, in project and/or plug-in meta-data, that no Discouraged Access warning should be registered for org.eclipse.datatools.* classes using org.eclipse.datatools.* code.