Bug 265898

Summary: [formatter] Not having "Enable Javadoc comment formatting" breaks breaks class level javadoc
Product: [Eclipse Project] JDT Reporter: Martyn Speck <martynspeck>
Component: CoreAssignee: Frederic Fusier <frederic_fusier>
Status: VERIFIED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: david_audel, Olivier_Thomann
Version: 3.4.1   
Target Milestone: 3.5 M5   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Martyn Speck CLA 2009-02-23 18:24:57 EST
We would like to not format our javadoc comments automatically. However, deselecting "Enable Javadoc comment formatting" causes the class level javadoc to cease being a javadoc. This is important for things like Hibernate.

This...
/**
 * @hibernate.subclass discriminator-value="address"
 */
public class AddressAssetVersion extends AbstractAssetVersion
{

becomes this on ctrl-shift-f.
/*
 * @hibernate.subclass discriminator-value="address"
 */
public class AddressAssetVersion extends AbstractAssetVersion
{


Please and Thank You
Comment 1 Olivier Thomann CLA 2009-02-23 23:02:28 EST
This would be a bug. Not formatting a javadoc comment should not convert it to a block comment.
Comment 2 Frederic Fusier CLA 2009-02-24 03:29:00 EST
I cannot reproduce this problem except when 'Enable header comment formatting' is selected as well. Could you confirm that this check-box is also selected in your preferences?
Comment 3 Martyn Speck CLA 2009-02-24 11:32:39 EST
'Enable header comment formatting' is selected.

I get the same result as you. The bug only happens when 'Enable header comment formatting' is selected.   
Comment 4 Frederic Fusier CLA 2009-02-24 11:39:39 EST
(In reply to comment #3)
> 'Enable header comment formatting' is selected.
> 
> I get the same result as you. The bug only happens when 'Enable header comment
> formatting' is selected.   
> 
Thanks for the feedback, hence a duplicate of bug 254998...


*** This bug has been marked as a duplicate of bug 254998 ***
Comment 5 David Audel CLA 2009-03-09 11:55:10 EDT
Verified for 3.5M6.

The bug is fixed but the behavior does not look perfect: https://bugs.eclipse.org/bugs/show_bug.cgi?id=267658