Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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

 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
←[[DTP Ganymede Resolving Discouraged Access Warnings | Back to the DTP Ganymede Discouraged Access page]]
 
←[[DTP Ganymede Resolving Discouraged Access Warnings | Back to the DTP Ganymede Discouraged Access 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.
 
  
 
==Purpose==
 
==Purpose==
Line 17: Line 13:
 
[[Image:build_path_page.JPG]]
 
[[Image:build_path_page.JPG]]
  
* Expand the "Plug-in Dependencies" node ('''note:''' watch out, since the "JRE System Library" node has an "Access rules" child too, and setting the filter there will not work as expected):
+
* Expand the "Plug-in Dependencies" node ('''note:''' watch out, since the "JRE System Library" node has an "Access rules" child too, and setting the filter there will not work as expected) and select "Access rules":
 +
 
 +
[[Image:build_path_page_access_rule.JPG]]
 +
 
 +
* "Edit" then "Add" to define the following rule:
 +
 
 +
[[Image:build_path_page_add_access_rule.JPG]]
 +
 
 +
* Accept the changes to the Access Rules, and rebuild the plug-in
 +
 
 +
* The '''internal''' ''Discouraged Access'' warnings should disappear for that plug-in

Latest revision as of 12:37, 6 February 2008

Back to the DTP Ganymede Discouraged Access page

Purpose

This document shows how to set access rule exceptions for filtering out internal Discouraged Access warning in DTP Ganymede and future versions.

Procedure

An access rule exception needs to be set for the plug-in project's build configuration.

  • For the plug-in project, open the build configuration page (either <alt-enter> or "Properties" from the context menu for the plug-in project), and select the "Libraries" tab for "Java Build Path":

Build path page.JPG

  • Expand the "Plug-in Dependencies" node (note: watch out, since the "JRE System Library" node has an "Access rules" child too, and setting the filter there will not work as expected) and select "Access rules":

Build path page access rule.JPG

  • "Edit" then "Add" to define the following rule:

Build path page add access rule.JPG

  • Accept the changes to the Access Rules, and rebuild the plug-in
  • The internal Discouraged Access warnings should disappear for that plug-in

Back to the top