ppkarwasz commented on issue #1706: URL: https://github.com/apache/logging-log4j2/issues/1706#issuecomment-1809739210
We introduced a deterministic formatter in apache/logging-parent#59. The process of choosing the right formatter started on September 20th in [this `dev` thread](https://lists.apache.org/thread/t2fxkk4cx6x70wx8m1ld0n75nq39j62f). The choice fell on [palantir-java-format](https://github.com/palantir/palantir-java-format), because: - it has an excellent Java 8 (lambdas) support (compared to [google-java-format](https://github.com/google/google-java-format)), - it is largely compatible with our [previous Java Style Guide](https://logging.apache.org/log4j/2.x/javastyle.html). Compared to the Google Java Format, it uses an indentation of **4** spaces instead of **2** spaces, - compared to the [Eclipse Java formatter](https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fpreferences%2Fjava%2Fcodestyle%2Fref-preferences-formatter.htm) it has no formatting options. This is actually an advantage, since it prevents discussing each one of the hundreds Eclipse options. Moreover some Eclipse options render the formatting non-deterministic, - it provides support for both our build environment (Spotless) and IntelliJ IDEA editor, In order to provide support for the Eclipse IDE, we ported Google's Java Format Eclipse plugin to `palantir-java-format`: palantir/palantir-java-format#949. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
