380094 – [formatter] Doesn't wrap method declaration exceeding line length

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 380094 - [formatter] Doesn't wrap method declaration exceeding line length

Summary: [formatter] Doesn't wrap method declaration exceeding line length

Status:	RESOLVED DUPLICATE of bug 303519

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	Core (show other bugs)
Version:	3.8
Hardware:	PC Windows 7

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	JDT-Core-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-05-20 21:03 EDT by Nobody - feel free to take it
Modified:	2012-05-21 12:32 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
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 Nobody - feel free to take it

2012-05-20 21:03:05 EDT

Build Identifier: 20120216-1857 

My Java formatter is set to a width of 120 characters, and I have a checkstyle configuration which also has the same setting.

On one line of code, when formatted, Eclipse says that its fine and won't put code on a new line and indent (it'll revert it to a single line if you attempt to).  However, the line length is 122, and Checkstyle is therefore saying its invalid.

Reproducible: Always

Steps to Reproduce:
1. Set Eclipse code formatter for Java to have a max line length of 120
2. Write a line of java that's 122 characters long.
(i.e.: void testIfThisWorks(final String variable1, final String variable2, final String variable3, final String variable4);)
3. Ctrl+F (or format), it'll remain on 122 lines.

Comment 1 Markus Keller

2012-05-21 09:18:21 EDT

Probably a dup of bug 110569 or bug 303519.

Comment 2 Ayushman Jain

2012-05-21 12:32:39 EDT

(In reply to comment #1)
> Probably a dup of bug 110569 or bug 303519.

Yup, this should be handled along with bug 303519

*** This bug has been marked as a duplicate of bug 303519 ***