Twitter github

!@#$%^& Access Restrictions!

In keeping with the “Enhancing New Plug-in Developer Experience” theme, PDE recently added new validation and a quickfix to help with access restriction issues that could be solved by exporting a package. For example, say you have two plug-ins: a and b. If a attempts to use a class from b and b doesn’t export the package containing the class, you’ll get a pretty warning and quickfix now:

The next stops on the “Enhancing New Plug-in Developer Experience” train for me are:

  • 198724: Raise warning when . is not on bundle-classpath and there are source folders
  • 176360: Create marker if PDE projects uses external jar
  • 201347: Merge Plug-in Spy into PDE