Jump to: navigation, search

Dali Discouraged Access Warnings

Revision as of 12:57, 4 December 2007 by Brian.vosburgh.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 of org.eclipse.jpt.ui).
    • 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 Access warnings 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.tests suppresses any warnings caused by references to org.eclipse.jpt.core). See the DTP description of this Eclipse feature.
      • Exception: The test "extension" plug-in, org.eclipse.jpt.core.test.extension.resource should not add any access rule exceptions, since it should be using Dali's public API (eventually).
  • WTP Discouraged Access Warnings


  • External Discouraged Access Warnings