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
  • Antoine

    How about that one ?

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=198465

    I think it covers 198724 and even more cases. How about linking them in Bugzilla ?

  • Antoine

    How about that one ?https://bugs.eclipse.org/bugs/show_bug.cgi?id=198465I think it covers 198724 and even more cases. How about linking them in Bugzilla ?

  • Kevin McGuire

    Hey, this is fantastic! The relationship between package import and plugin export are very tricky for people to get right and previously could be hidden until a full export and test was performed (then good luck sorting it out). Great to see this work going on.

  • Kevin McGuire

    Hey, this is fantastic! The relationship between package import and plugin export are very tricky for people to get right and previously could be hidden until a full export and test was performed (then good luck sorting it out). Great to see this work going on.

  • Chris Aniszczyk (zx)

    Thanks Kevin, I thought it was one of the coolest features ever, however, not many people are as excited about quickfixes like us šŸ˜‰

  • Chris Aniszczyk (zx)

    Thanks Kevin, I thought it was one of the coolest features ever, however, not many people are as excited about quickfixes like us šŸ˜‰