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.
Dali Discouraged Access Warnings
Revision as of 12:57, 4 December 2007 by Brian.vosburgh.oracle.com (Talk | contribs) (New page: For background, see DTP's discussion of resolving <code>Discouraged Access</code> warnings. Currently, Dali has three levels of ''Di...)
For background, see DTP's discussion of resolving Discouraged Access warnings.
Currently, Dali has three levels of Discouraged Access warnings to deal with:
- Internal Discouraged Access Warnings
- Non-Test Plug-ins: Add non-test plug-ins as "friends" of other non-test plug-ins, as appropriate (e.g. all the non-test plug-ins are friends of
org.eclipse.jpt.utility; while none of the plug-ins are friends oforg.eclipse.jpt.ui).
- Non-Test Plug-ins: Add non-test plug-ins as "friends" of other non-test plug-ins, as appropriate (e.g. all the non-test plug-ins are friends of
- Test Plug-ins: Because test plug-ins are not loaded at run-time, there is no need to make test plug-ins friends of the non-test plug-ins. To suppress the
Discouraged Accesswarnings in a test plug-in, add the appropriate build-time access rule exceptions to the project's Java Build Path (e.g.org.eclipse.jpt.core.testssuppresses any warnings caused by references toorg.eclipse.jpt.core). See the DTP description of this Eclipse feature.
- Test Plug-ins: Because test plug-ins are not loaded at run-time, there is no need to make test plug-ins friends of the non-test plug-ins. To suppress the
- Exception: The test "extension" plug-in,
org.eclipse.jpt.core.test.extension.resourceshould not add any access rule exceptions, since it should be using Dali's public API (eventually).
- Exception: The test "extension" plug-in,
- WTP Discouraged Access Warnings
Dali
- External Discouraged Access Warnings