Community
Participate
Working Groups
Somehow, the "old" (either in 3.0.m3 or m4, I am sorry I cannot recall) Java code formatter mucked my source such that I now have: public void setErrorQOptions(int errorQOptions) { this.errorQOptions = errorQOptions; } /** Sets the MQSeries error queue. */ public void setErrorQueue(MQQueue errorQueue) { this.errorQueue = errorQueue; } /** Sets the MQSeries error queue name to use on open. */ public void setErrorQueueName(String errorQueueName) { this.errorQueueName = errorQueueName; } /** Sets the MQ option flags to use for the input queue on open. */ public void setInputQOptions(int inputQOptions) { this.inputQOptions = inputQOptions; } /** Sets the MQSeries input queue. */ public void setInputQueue(MQQueue inputQueue) { this.inputQueue = inputQueue; } /** Sets the MQSeries input queue name to use on open. */ In 3.0.m4, When I reformat the code with the "old" or "new" formatter, nothing changes. Perhaps there should be another setting or the formatter should always make sure that Javadoc comments start on a new line. Thanks.
The new formatter tries to keep comments as much as possible where they are. But in this case. It should add a new line after the method closing brace. I will investigate.
In this case, your comments are considered as trailing comment of the preceeding method.
I will remove the javadoc comments from the trailing comments. So a javadoc comment will always be moved on a new line. Fixed and released in HEAD. Regression test added.
Verified.
