Bug 546864 - one place for @author in generated comments
Summary: one place for @author in generated comments
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-04-30 08:35 EDT by arne anka CLA
Modified: 2023-04-21 09:43 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description arne anka CLA 2019-04-30 08:35:58 EDT
having comments generated with 
@author
defaults to username:

/**
* @author username
**/

which IMO is not a sensible default anyway.
But I want it to read

/**
* @author firstname lastname (mail@address)
**/

By now I have changed it in 3 or 4 places, and still I often get the default.

I propose to have a _single_ place in preferences to configure the value for @author and have it picked up by all and sundry creating code using @author

I am aware of that hackish way to set something like that in eclipse.ini -- but that's hardly a viable solution.
Comment 1 Eclipse Genie CLA 2021-04-21 10:14:31 EDT
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 2 arne anka CLA 2021-04-22 04:55:49 EDT
AFAIT it' still not fixed.
Comment 3 Eclipse Genie CLA 2023-04-21 09:43:03 EDT
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.