Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-dev] Discouraged package access - are we following the rules?

I noticed that we still have may discouraged access warnings in the builds. It looks like all the bundles included in RCP are OK, but there are several bundles in the SDK that still have discouraged access warnings. Should the discourage access warnings be eliminated in SDK bundles for 3.4? Or did we decide that accessing internal packages was OK for bundles outside of RCP?

Today I tried to run the Hello RCP example in strict mode (e.g. with the configuration setting osgi.resolverMode=strict). This failed because some of the RCP bundles reference internal packages in extension definitions (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=221319). I suspect we have many cases where this is done because our tools currently do not flag this as an error/warning. For 3.4 are we expecting the RCP bundles to only use real API packages (and special case x-friends) and are we expecting RCP bundles to work when access rules are fully enforced at runtime? With out some help from API tooling and a fix to the PDE bug mentioned above I don't think this will be easy to accomplish.

Tom


Back to the top