Bug 178366 - [ast rewrite] 'Add all missing tags' and 'Add @param tag' quick fixes place comment at wrong location
Summary: [ast rewrite] 'Add all missing tags' and 'Add @param tag' quick fixes place ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-20 14:19 EDT by Dani Megert CLA
Modified: 2023-11-28 13:48 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2007-03-20 14:19:49 EDT 
I20070320-0010.


Have:
	/**
	 * This is a test.
	 * 
	 * @since 3.0
	 */
	private void test(int foo) {

Assuming Javadoc warnings are enable, execute the 'Add all missing tags' or 'Add @param tag'
==>
	/**
	 * This is a test.
	 * @param foo 
	 * 
	 * @since 3.0
	 */
EXPTECTED:
	/**
	 * This is a test.
	 * 
	 * @param foo 
	 * @since 3.0
	 */

Same is true if there are already some parameters Javadoc'ed.

This becomes more and more frustrating as I want to correct the Javadoc warnings in JDT UI when I see them.
Comment 1 Dani Megert CLA 2007-11-06 04:07:49 EST 
Can this be fixed for M4? It would save me lots of typing. Of course the correct thing would be to use all the comment formatter settings as currently people who changed them always have to go and apply them manually.
Comment 2 Eclipse Genie CLA 2019-12-14 15:25:02 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Dani Megert CLA 2019-12-17 04:46:45 EST 
Still an issue in 4.14.
Comment 4 Eclipse Genie CLA 2021-12-07 12:05:15 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2023-11-28 13:48:57 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.