Community
Participate
Working Groups
Build ID: I20090605-1444 Steps To Reproduce: 1. Create a plugin project 2. Select any element inside that new project 3. Invoke Open Type dialog (via short-cut) 4. Type "Reader" in the filter and find "org.eclipse.emf.mwe.utils.Reader" NOT being listed 5. Add dependency to "org.eclipse.emf.mwe.utils" and save manifest 6. Invoke Open Type dialog (via short-cut) 7. Type "Reader" in the filter and find "org.eclipse.emf.mwe.utils.Reader" BEING listed More information: I'm very certain, that in Eclipse 3.4.x the Open Type dialog did not restrict it's search on the Types available to the current project, but rather scanned all type available on the platform. That feature had helped me a lot finding a plugin to a type, that's NOT in the dependency list yet. Please ensure the consistency of that behavior for the upcoming Galileo release.
Did you add your plug-ins to Java search? http://wiki.eclipse.org/FAQ_How_do_I_find_a_particular_class_from_an_Eclipse_plug-in%3F
I suspect the same as Remy: you probably have a new workspace that does not have all plug-ins yet. In 3.5 you can add all plug-ins in one shot: 1. Ctrl+3 2. type "add all" into search field 3. press 'Enter' Does this solve your issue?
(In reply to comment #2) > I suspect the same as Remy: you probably have a new workspace that does not > have all plug-ins yet. In 3.5 you can add all plug-ins in one shot: > > 1. Ctrl+3 > 2. type "add all" into search field > 3. press 'Enter' > > Does this solve your issue? > Yes, it did. However, my colleagues and I find this quite inconvinient. Why can't all plugins be added automatically to the java search by Eclipse? If I don't want to see certain classes, I'd use the type filters as I did before.
Because people who just develop Java (not plug-ins) are not interested in those types.
See bug 81281 and bug 175134 for improvements in PDE-land.
