Twitter github

PDE and BugDay

I just wanted to share something cool that has come out of bugday so far!

But first, let me tell you a story! Have you ever worked on your cool plug-in project or product, drank a few glasses of wine (or some fine coffee porter) to see this in your project explorer view:

External Plug-in Libraries…? Where did that come from? How many glasses of wine did I have? Where am I? I don’t remember creating that project.

Well, I have good news, you didn’t create that project directly. If you ever took advantage of adding plug-ins to Java Search (which a lot of people do via the Plug-ins view), PDE indirectly created this project to help the awesome JDT search the plug-in(s) you’re interested in. I’ve always wanted this project hidden by default because it confused me as a new user and it will probably confuse other new users (some of which will probably delete that project when they see it anyway).

So now back to bugday. Peter Friese submitted a patch and finally fixed this problem. There is now a filter that is on by default:

Thanks Peter and check this out in the next I-build!

  • Eugene Kuleshov

    Isn’t adding this project added to fancy Java search is a huge hack? I think Jeff McAffer will love the idea, but surely there should be nicer way to add stuff into Java search. Am I missing something?

  • Villane

    I think this needs a more generic solution. Perhaps projects should have a “hidden” property, or projects starting with “.” (dot) should be filterable. I don’t really know what I’m talking about, though.

  • Wassim Melhem

    Eugene, as you know, the JDT Search engine cannot see any classes that are not in the workspace scope, while PDE has a concept of target plug-ins that are not part of that scope.

    So what one person may call a huge hack, another may call it “the best that PDE can do at this time”.

  • David Kyle

    Check out Eclipse bug 194694. Eclipse 3.4 will hide “External Plug-in Libraries” by default.

    The problem with hidding “External Plug-in Libraries” by default is it breaks the FAQ “How do I find a particular class from an Eclipse plug-in?” in both the “Official Eclipse 3.0 FAQs” book and the web page.

    It just moves the Eclipse IDE farther and farther away from the original books. It is another small hinderance for new developers learning the Eclipse framework.

    Will there be new editions of the Eclipse series of books?