Problem with carriage return is that after several month someone who uses formatter that doesn't need trailing slashes will remove it to cleanup the code.I can't say that it is fault of that developer because he removed it. We should not forbid cleaning the code.
So carriage return should be controlled by code formatter.
I guess it would be reviewed and some question would come "why are you removing these trailing slashes ?"
about #1, the only common tool across all IDE is maven
So I should say that we should have a maven plugin allowing to format the code (the same code convention could be used with Eclipse IDE, IntelliJ, Eclipse Che, another IDE) but at the end we could still use maven to check or format.
In this mailing list, I would say that the only common tool is Eclipse Che ...
Whatever the tool we use, a maven plugin or other, the formatting rules we choose should be available in Eclipse Che. This is what we should do at least.
about #2, I would avoid any "developer's touch". Formatter is the rule. (we can complain on the format but once it is pick-up, it should be applied without exceptions)
because "he choice of the developer to make the code easier to read" is subjective. Some developers will like in one line, some on separate lines while the formatter will always be the same.
A lot of things is subjective when we write code: variable name, method name, order of parameter, etc ...
Also, I think it's impossible to have a perfect formatter ... and at the end it will have to write unit test to make sure that all the change we are making to the formatter doesn't break the formatting rules defined for another piece code. We are not robot.
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev