This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 246706 - "Generate" commands will remove class javadoc comments.
Summary: "Generate" commands will remove class javadoc comments.
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Svata Dedic
URL:
Keywords:
Depends on: 245103
Blocks:
  Show dependency tree
 
Reported: 2014-08-26 15:46 UTC by crosati
Modified: 2014-08-29 07:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (133.52 KB, text/plain)
2014-08-26 15:46 UTC, crosati
Details

Note You need to log in before you can comment on or make changes to this bug.
Description crosati 2014-08-26 15:46:31 UTC
"Generate" commands will remove class javadoc comments.

The most annoying are (on windows activated using ALT-INSERT the selecting the "Generate" command with UP/DOWN arrows and RETURN):
- Generate implementation...
- Generate override method...


Product Version = NetBeans IDE 8.0 (Build 201403101706)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_11
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.11-b03
Comment 1 crosati 2014-08-26 15:46:37 UTC
Created attachment 148905 [details]
IDE log
Comment 2 Svata Dedic 2014-08-29 07:22:11 UTC
I could not reproduce the case of comments remove doing "Generate override method" or "generate implement method". The enclosing class' javadoc remained as it was for both inner and top-level classes (Build 201403101706).
Maybe it's connected to your specific code generation and/or indentation settings.

Anyway, this issue was fixed as a part of issue #245103 and should be improved in 8.0.1 or even better in the dev version.

If you encounter the defect in the dev version, please export your configuration or zip your $userdir/config contents and attach here, possibly with classes (fragments) that would allow to reproduce the scenario failing on your machine.