[solr] branch main updated: update formatting (#941)

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new 7339c37ad58 update formatting (#941)
7339c37ad58 is described below

commit 7339c37ad5893ad003e3d73fa72007e1ddd60747
Author: Eric Pugh <ep...@opensourceconnections.com>
AuthorDate: Thu Jul 14 11:16:09 2022 -0400

    update formatting (#941)
---
 help/formatting.txt | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/help/formatting.txt b/help/formatting.txt
index 96240b3f44d..b2a293e8773 100644
--- a/help/formatting.txt
+++ b/help/formatting.txt
@@ -1,10 +1,6 @@
 Code formatting
 ===============
 
-NOTE: This does not yet apply to Solr, see SOLR-14920 for details
-
-
-
 
 ---
 Starting with (SOLR-14920) Java code is enforced to comply with
@@ -21,7 +17,6 @@ your code so that it complies with the convention and passes gradle
 IMPORTANT: There is *no* way to mark sections of the code as excluded
 from formatting. This is by design and cannot be altered. In vast
 majority of cases the formatter will do a great job of cleaning up the
-code. Occasionally you may want to rewrite the code (introduce a local
-variable orreshape code paths) so that it's easier to read after
-automatic formatting.
----
\ No newline at end of file
+code. To exclude files from being formatted investigate the spotless.gradle
+build script.
+---