Community
Participate
Working Groups
2.1 It would be nice to be able to search for text in the Javadoc of types and members, and have the matches be presented in terms of Java members. Alternatively, searching the whole body of a Java declaration would be fine. What I was actually trying to do was to find all types and methods with "@since 2.1". I had to use text search, which only gives the matches in terms of the files, not the individual declarations. More specialized support for searching Javadoc tags is another possibility. E.g. search for "2.1" in all @since tags.
There are plans to index "Javadoc" as well. But it is not yet clear how far this will go.
*** Bug 30713 has been marked as a duplicate of this bug. ***
Yes this would be greatly usefull, I was look for a way to maximize a view programatically, and tried to look for MAXIMIZE but nothing came up in the javadoc or there are static fields names MAXIMIZE like : ActionFactory.MAXIMIZE which I found thanks to the Eclipse site search but I spent a lot of looking for APIs to do that and could not fing any. The javadoc search would be of great help.
See bug 29840 for the zoom support.
Moving to jdt.core to evaluate this. There has been progress in 3.1 (I think) and all references or @link and @see are found. I could imagine that Java search can search for certain tags, @since, or @category.
(In reply to comment #5) > Moving to jdt.core to evaluate this. > > There has been progress in 3.1 (I think) and all references or @link and @see > are found. > You are right. All types/methods/fields references done in all tags (ie. @see, @link, @throws/@exception, @value) are found using Java Search. > I could imagine that Java search can search for certain tags, @since, or > @category. > Yes this could be a good search template. We'll look at this while implementing bug 110157...
Defer
Reopen as LATER is deprecated...
Should be more addressed while fixing bug 155013 than bug 110157...
After having worked on prototype for bug 155013, I realized that fine grain search only concerns reference to java element, not text in comments... So, put back to low priority (similar as LATER) as this enhancement will not be addressed while fixing bug 155013...
