Community
Participate
Working Groups
Eclipse M8. If you enable the javadoc warning Window->Preferences->JAva->Compiler->JAvadoc->Missing Javadoc Tags for public methods and then use quickfix on the following as indicated ------------------------ public class A { private int m_x; /** * */ public A(int x) //<-- use quickfix here on "x" { m_x = x; } } ---------------------- the option add missing javadoc tags doesn't show up.
Beware: If you switch to another text window and come back again, the quick fix is suddenly offered! Sometimes the editor loose the track and its state is recreated after the switch.
bug 60689 was the reason of this behaviour *** This bug has been marked as a duplicate of 60689 ***
Unfortunately this is still not completly fixed in 3.0 final (had no occurrencies in RC3 though). 1. Go to a method of an interface that declares no exception yet. 2. add "throws " and press CTRL+1 and select an exception. 3. press CTRL+S to save 4. Press CTRL+1 again ... "no correction available" 5. Switch to another Editor and come back 6. Press CTRL+1 again ... you have three items available (two for javadoc and local rename) I had also a case once, that in 4. I was presented only with the two java options, but selecting "Add all missing tags" did nothing and selecting "Add '@throws' tag" inserted "@throws" at the current curser position. Again switching editors and coming back enabled all three menu options and they worked as expected.
I can't reproduce. - add a new throws declaration to a method e.g. 'throws Exception' - Exception is marked: 'missing tag': Ctrl + 1: Quick fixes are there (don't choose one) - save Ctrl + 1: Quick fixes are still there Do you have more specific steps?
Unfortunately I could not reproduce it with these steps today even editing the same position in the same file as yesterday (using WinXP). I will try to find a repeatable case. I had same/similar problems (quick fix problem and the editor will not mark/find occurrences) with the Linux/GTK version yesterday evening and there were events in the error log. I will post them as soon as I am hoem again. -- Jörg
I guess you must have detected a different problem with the same symptoms. Can you open a new bug report when you find this again? Setting this one as a duplicate of bug 60689 again. *** This bug has been marked as a duplicate of 60689 ***
