Community
Participate
Working Groups
Build M20060921-0945. This is fup on bug 99738. The effect of the formatter on the example given in comment #6 is the following: /* <pre> <test> </pre> */ becomes: /* * <pre> <test> </pre> */ Notice the extra white space between the <pre> and the first &, which will result into a leading white space in the rendered HTML result. Unlike bug 99738, further format operations no more shift the result to the right.
Ownership has changed for the formatter, but I surely will not have enough time to fix your bug during the 3.5 development process, hence set its priority to P5. Please provide a patch if you definitely need the bug to be fixed in this version and I'll have a look at it... TIA
What is the expected behaviour after formatting something like: <pre>\n<test>\n</pre> Is this? <pre><test></pre> What about and the extra space after the first newline? <pre>\n <test>\n</pre> I think I could create a patch after clarifying this.
I think this is no longer a problem using 3.6.0... The following test case: public class X { /** <pre> <test> </pre> */ public void foo() {} } Is currently formatted as follow: public class X { /** * <pre> * <test> * </pre> */ public void foo() { } } I thought it was the correct behavior while fixing bug 305518. However, it seems that javadoc does not behaves the same as it does not generate exactly the same thing for: /** <pre> <test> </pre> */ than for: /** * <pre> * <test> * </pre> */ The difference is a space before the line in the generated method detail... Hence, it seems that javadoc considers that the space after the '*' belongs to the line, although our formatter does not... So, we can use this bug for this peculiar issue follow-up although the current formatter behavior is now different than the one described in comment 0... Of course a patch (including JUnit tests) is more than welcome :-)
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
