Bug 475455 - Unable to generate getters and setters
Summary: Unable to generate getters and setters
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 475456 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-08-20 04:02 EDT by Jan Cejp CLA
Modified: 2022-10-01 11:00 EDT (History)
3 users (show)

See Also:

Attachments
Project log with stacktrace (377.97 KB, text/x-log)
2015-08-20 04:02 EDT, Jan Cejp CLA 		no flags Details
View All 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 Jan Cejp CLA 2015-08-20 04:02:20 EDT 
Created attachment 255975 [details]
Project log with stacktrace

I have POJO with set of private fields. I want to generate getters and setters for all fields. After chose context menu -> Source -> Generate Getters and Setters. Generation finish with error:
 
Generating Getters and Setters Failed.
Index: 5, Size:5
Comment 1 Markus Knauer CLA 2015-08-20 05:24:40 EDT 
Works for me... I'll forward it to JDT.
Comment 2 Stephan Herrmann CLA 2015-08-20 09:29:51 EDT 
Likely a duplicate of either

- bug 462945 (fixed in Mars), or

- bug 472858 (caused by Lombok)

Please check if either of these bugs matches your situation.
Comment 3 Stephan Herrmann CLA 2015-08-20 09:31:10 EDT 
*** Bug 475456 has been marked as a duplicate of this bug. ***
Comment 4 Eclipse Genie CLA 2020-09-10 14:05:04 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 5 Eclipse Genie CLA 2022-10-01 11:00:20 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.