Community
Participate
Working Groups
If you add things to Java Search, an ugly and visible project is created in your workspace called 'External Plug-in Libraries' This should be hidden by default as new users might be confused where this comes from and may delete it or do something silly.
DJ and Kevin are big fans of this function. We should get their input on whether this project should be hidden (e.g. have a name that starts with '.' etc.) I suspect DJ likes to see it since he likes the entries to be sorted (bug 177773).
Since I was forced to see it, I wanted the entries sorted. But if there was a filter or something so it could be hidden, that would be fine with me.
Assigning to Adam. I think we need a new separate filter here (ie. we don't want to reuse existing ones like the binary projects filter). The filter is on by default, and since the project that gets created has a hardcoded name, it should just filter out the project by its name.
Created attachment 74608 [details] Patch to fix 194694
Created attachment 74609 [details] mylyn/context/zip
I'll review later today and release. This brings me so much joy because I've always hated seeing that mystery project ;p
committed to HEAD. This filter is now on by default. Blogged about it in your honor :) http://mea-bloga.blogspot.com/2007/07/pde-and-bugday.html
btw Peter, I enabled this filter by default, which was a very small change in the plugin.xml for the filters (basically a yes instead of a no). I also attributed the work to you via the copyright. Thanks!
Chris, stop wiping out the target milestone ;)
blame Mik, it's a Mylyn bug.
(In reply to comment #7) > Blogged about it in your honor :) > http://mea-bloga.blogspot.com/2007/07/pde-and-bugday.html Thanks a lot! (In reply to comment #8) > btw Peter, I enabled this filter by default, which was a very small change in > the plugin.xml for the filters (basically a yes instead of a no). Shame on me for forgetting this one. One should not do "copy-paste"... Well, good you reviewed and fixed it :-)
I'm a bit late to the party but I'll add my 2c worth. I've always found the presentation of the Java search elements as a pseudo project to be rather odd. I understand the technical constraints that got us there though. It does solve the problem of having a place for these elements to show up in the package explorer. A more involved solution would be one where say there was a separate explorer tab for the libraries (although that introduces other issues around navigation), or some kind of split area in the explorer, or something more clever we've not thought of. With the present restrictions and in the absence of a major rethink, the current solution is odd but workable. Adding filtering is at least a consistent step but in my mind a workaround for a more subtle problem.
The problem with hidding "External Plug-in Libraries" by default in 3.4 is it breaks the FAQ "How do I find a particular class from an Eclipse plug-in?". http://wiki.eclipse.org/FAQ_How_do_I_find_a_particular_class_from_an_Eclipse_plug-in%3F It just moves the Eclipse IDE farther and farther away from the original books. Are new editions in works?
Adding things to Java Search still works, along with Ctrl+Shift+T. You just don't see the hack of a project where the class comes from :) As a side note, Jeff, Jean and I are working on updating the RCP Book for 3.4
(In reply to comment #14) > As a side note, Jeff, Jean and I are working on updating the RCP Book for 3.4 Woot!!! :-)
(In reply to comment #14) > As a side note, Jeff, Jean and I are working on updating the RCP Book for 3.4 Fantastic! Is there a scheduled date? The only drawback of Eclipse books is that they look a little outdated as soon as they get published :(
> Fantastic! Is there a scheduled date? There's no scheduled date as we can't guarantee anything yet, but we're shooting to have something done a few months after EclipseCon, if not sooner. A lot has changed since 3.1 guys :P
