| Re: [ptp-dev] APIs |
| Yes. Open the MANIFEST.MF and go to the Runtime tab. Make sure every package is listed in the Exported Packages table. If not, add them. Select each package in turn and set the Package Visibility to "hidden from all plug-ins except:". Leaving the corresponding table empty will just mark the package internal. You can also export the package to specific plugins so they don't get the "Discouraged access" warnings. Also, for package names, internal packages should be named org.eclipse.ptp.internal.<component>. There are still quite a few that have the "internal" part in the wrong place. When renaming a package there are a couple of gotchas to be aware of. If your plugin is called org.eclipse.ptp.foo and you have a package called org.eclipse.ptp.foo then depending on which options you pick, the refactoring may try to rename the plugin name in the .project and pom.xml files. Make sure you don't do this. Also, there may be fully qualified names in the files that you do or do not want to change. For example, you don't want to change the PLUGIN_ID in the activator or IDs in the plugin.xml. However you do want to change the BUNDLE_ID in Messages.java. Unfortunately this means you need to do a fair bit of manual inspection before accepting the changes. Thanks, Greg On May 3, 2013, at 7:41 PM, Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
|