Different line length limit for groovy and java files

[g4s8]

It's not clear why line length limit for groovy and java files is different:

• java - 80 chars
• groovy - 120 chars

I think 120 chars would be OK for all file-type.

[0crat]

@krzyk/z please, pay attention to this issue

[krzyk]

@g4s8 I missed that, but there was already a discussion about this here - #862

@yegor256 Should groovy files be limited to 80 chars also? Or are we leaving them at 120 chars, because we assume there will be less code in groovy and more with "script" nature?

[yegor256]

@krzyk do we still check Groovy files in Qulice? We shouldn't. As for the Java, I would suggest to migrate to 100 chars limit. 80 is indeed too narrow.. WDYT?

[krzyk]

@yegor256 We check only java files for line length. OK so let's go with 100 chars for java. @g4s8 could you update your comment?
Groovy is checked using codenarc and not using qulice and we will increase java limit to 100 chars.

[krzyk]

@0crat in

[0crat]

@0crat in (here)

@krzyk Job #867 is now in scope, role is DEV

[0crat]

Bug was reported, see §29: +15 point(s) just awarded to @g4s8/z

[krzyk]

@0crat assign me

[0crat]

@0crat assign me (here)

@krzyk The job #867 assigned to @krzyk/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[0crat]

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @krzyk/z

[krzyk]

@g4s8 change has been merged to master and will be released in 0.18.9 in hour or two, please close this issue

[g4s8]

@krzyk thanks

[0crat]

Job was finished in 22 hours, bonus for fast delivery is possible (see §36)

[0crat]

The job #867 is now out of scope

[0crat]

Order was finished: +35 point(s) just awarded to @krzyk/z