Bug 543168 - Type parameters in Javadoc are not correctly interpreted
Summary: Type parameters in Javadoc are not correctly interpreted
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.11   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-04 06:25 EST by Roberto Morávia CLA
Modified: 2023-02-23 17:38 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Morávia CLA 2019-01-04 06:25:09 EST
When I "Format" the code with the option "Align Javadoc tags in columns -> Align names and descriptions" the type parameters are aligned with the description and not with the rest of the parameters:

    /**
     * Checks if the given object is not null.
     *
     * @param  object          The object that will be verified.
     * @param  exceptionGetter The method that will generate the exception.
     * @param                  <T> Exception parameter type.
     * @param                  <U> Object parameter type.
     * @return                 object if it is not null.
     * @throws T               If the given object is null.
     */

I would expect the <T> and <U> to be aligned under exceptionGetter.
Comment 1 Roberto Morávia CLA 2019-01-04 06:27:45 EST
The format I expect is described here https://docs.oracle.com/javase/1.5.0/docs/tooldocs/windows/javadoc.html#@param
Comment 2 Eclipse Genie CLA 2020-12-25 13:33:43 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 Eclipse Genie CLA 2023-02-23 17:38:12 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.