Order imports when reformatting (#74059)

Change the formatter config to sort / order imports, and reformat the
codebase. We already had a config file for Eclipse users, so Spotless now
uses that.

The "Eclipse Code Formatter" plugin ought to be able to use this file as
well for import ordering, but in my experiments the results were poor.
Instead, use IntelliJ's `.editorconfig` support to configure import
ordering.

I've also added a config file for the formatter plugin.

Other changes:
   * I've quietly enabled the `toggleOnOff` option for Spotless. It was
     already possible to disable formatting for sections using the markers
     for docs snippets, so enabling this option just accepts this reality
     and makes it possible via `formatter:off` and `formatter:on` without
     the restrictions around line length. It should still only be used as
     a very last resort and with good reason.
   * I've removed mention of the `paddedCell` option from the contributing
     guide, since I haven't had to use that option for a very long time. I
     moved the docs to the spotless config.

Author: pugnascotia

.editorconfig

@@ -8,12 +8,20 @@ trim_trailing_whitespace = true
 insert_final_newline = true
 indent_style = space
 
+# IntelliJ-specific options
+ij_java_class_count_to_use_import_on_demand = 999
+ij_java_names_count_to_use_import_on_demand = 999
+ij_java_imports_layout = *,|,com.**,|,org.**,|,java.**,javax.**,|,$*
+
 [*.gradle]
 indent_size = 2
 
 [*.groovy]
 indent_size = 4
 max_line_length = 140
+ij_groovy_class_count_to_use_import_on_demand = 999
+ij_groovy_names_count_to_use_import_on_demand = 999
+ij_groovy_imports_layout = *,|,com.**,|,org.**,|,java.**,javax.**,|,$*
 
 [*.java]
 indent_size = 4

.idea/eclipseCodeFormatter.xml

@@ -181,8 +181,12 @@ action is required.
 #### Formatting
 
 We are in the process of migrating towards automatic formatting Java file
-using [spotless], backed by the Eclipse formatter. If you have the [Eclipse
-Code Formatter] installed, you can apply formatting directly in IntelliJ.
+using [spotless], backed by the Eclipse formatter. **We strongly recommend
+installing using the [Eclipse Code Formatter] plugin** so that you can
+apply the correct formatting directly in IntelliJ.  The configuration for
+the plugin is held in `.idea/eclipseCodeFormatter.xml` and should be
+automatically applied, but manual instructions are below in case you you
+need them.
 
    1. Open **Preferences > Other Settings > Eclipse Code Formatter**
    2. Click "Use the Eclipse Code Formatter"
@@ -194,7 +198,8 @@ Code Formatter] installed, you can apply formatting directly in IntelliJ.
 
 Note that only some sub-projects in the Elasticsearch project are currently
 fully-formatted. You can see a list of project that **are not**
-automatically formatted in [gradle/formatting.gradle](gradle/formatting.gradle).
+automatically formatted in
+[build-tools-internal/src/main/groovy/elasticsearch.formatting.gradle](build-tools-internal/src/main/groovy/elasticsearch.formatting.gradle).
 
 ### Importing the project into Eclipse
 
@@ -270,12 +275,10 @@ form.
 
 ### Java Language Formatting Guidelines
 
-Java files in the Elasticsearch codebase are formatted with the Eclipse JDT
-formatter, using the [Spotless
-Gradle](https://github.com/diffplug/spotless/tree/master/plugin-gradle)
-plugin. This plugin is configured on a project-by-project basis, via
-`build.gradle` in the root of the repository. The formatting check can be
-run explicitly with:
+Java files in the Elasticsearch codebase are automatically formatted using
+the [Spotless Gradle] plugin. All new projects are automatically formatted,
+while existing projects are gradually being opted-in. The formatting check
+can be run explicitly with:
 
     ./gradlew spotlessJavaCheck
 
@@ -315,28 +318,12 @@ Please follow these formatting guidelines:
 
 IntelliJ IDEs can
 [import](https://blog.jetbrains.com/idea/2014/01/intellij-idea-13-importing-code-formatter-settings-from-eclipse/)
-the same settings file, and / or use the [Eclipse Code
-Formatter](https://plugins.jetbrains.com/plugin/6546-eclipse-code-formatter)
-plugin.
+the same settings file, and / or use the [Eclipse Code Formatter] plugin.
 
 You can also tell Spotless to [format a specific
 file](https://github.com/diffplug/spotless/tree/master/plugin-gradle#can-i-apply-spotless-to-specific-files)
 from the command line.
 
-#### Formatting failures
-
-Sometimes Spotless will report a "misbehaving rule which can't make up its
-mind" and will recommend enabling the `paddedCell()` setting. If you
-enabled this setting and run the format check again,
-Spotless will write files to
-`$PROJECT/build/spotless-diagnose-java/` to aid diagnosis. It writes
-different copies of the formatted files, so that you can see how they
-differ and infer what is the problem.
-
-The `paddedCell()` option is disabled for normal operation so that any
-misbehaviour is detected, and not just suppressed. You can enabled the
-option from the command line by running Gradle with `-Dspotless.paddedcell`.
-
 ### Javadoc
 
 Good Javadoc can help with navigating and understanding code. Elasticsearch
@@ -730,3 +717,4 @@ repeating in this section because it has come up in this context.
 [Checkstyle]: https://plugins.jetbrains.com/plugin/1065-checkstyle-idea
 [spotless]: https://github.com/diffplug/spotless
 [Eclipse Code Formatter]: https://plugins.jetbrains.com/plugin/6546-eclipse-code-formatter
+[Spotless Gradle]: https://github.com/diffplug/spotless/tree/master/plugin-gradle

CONTRIBUTING.md

@@ -14,12 +14,12 @@
 import org.apache.lucene.search.Query;
 import org.elasticsearch.common.breaker.CircuitBreaker;
 import org.elasticsearch.common.breaker.PreallocatedCircuitBreakerService;
-import org.elasticsearch.core.Releasable;
-import org.elasticsearch.core.Releasables;
 import org.elasticsearch.common.settings.ClusterSettings;
 import org.elasticsearch.common.settings.Settings;
 import org.elasticsearch.common.util.BigArrays;
 import org.elasticsearch.common.util.PageCacheRecycler;
+import org.elasticsearch.core.Releasable;
+import org.elasticsearch.core.Releasables;
 import org.elasticsearch.index.Index;
 import org.elasticsearch.index.IndexSettings;
 import org.elasticsearch.index.analysis.NamedAnalyzer;

benchmarks/src/main/java/org/elasticsearch/benchmark/search/aggregations/AggConstructionContentionBenchmark.java

@@ -218,11 +218,23 @@ subprojects {
             target 'src/**/*.java'
           }
 
+          toggleOffOn('formatter:off', 'formatter:on') // use `formatter:off` and `formatter:on` to toggle formatting - ONLY IF STRICTLY NECESSARY
           removeUnusedImports()
+          importOrderFile rootProject.file('build-tools-internal/elastic.importorder')
           eclipse().configFile rootProject.file('build-tools-internal/formatterConfig.xml')
           trimTrailingWhitespace()
 
-          // See CONTRIBUTING.md for details of when to enabled this.
+          // Sometimes Spotless will report a "misbehaving rule which can't make up its
+          // mind" and will recommend enabling the `paddedCell()` setting. If you
+          // enabled this setting and run the format check again,
+          // Spotless will write files to
+          // `$PROJECT/build/spotless-diagnose-java/` to aid diagnosis. It writes
+          // different copies of the formatted files, so that you can see how they
+          // differ and infer what is the problem.
+
+          // The `paddedCell()` option is disabled for normal operation so that any
+          // misbehaviour is detected, and not just suppressed. You can enabled the
+          // option from the command line by running Gradle with `-Dspotless.paddedcell`.
           if (System.getProperty('spotless.paddedcell') != null) {
             paddedCell()
           }

build-tools-internal/src/main/groovy/elasticsearch.formatting.gradle

@@ -104,11 +104,6 @@ if (System.getProperty('idea.active') == 'true') {
         taskTriggers {
           afterSync tasks.named('configureIdeCheckstyle'), tasks.named('configureIdeaGradleJvm'), tasks.named('buildDependencyArtifacts')
         }
-        codeStyle {
-          java {
-            classCountToUseImportOnDemand = 999
-          }
-        }
         encodings {
           encoding = 'UTF-8'
         }

build-tools-internal/src/main/groovy/elasticsearch.ide.gradle

@@ -10,13 +10,14 @@
 
 import joptsimple.OptionSet;
 import joptsimple.OptionSpec;
+
 import org.elasticsearch.cli.Command;
 import org.elasticsearch.cli.Terminal;
-import org.elasticsearch.core.SuppressForbidden;
 import org.elasticsearch.common.hash.MessageDigests;
-import org.elasticsearch.core.PathUtils;
 import org.elasticsearch.common.xcontent.XContentGenerator;
 import org.elasticsearch.common.xcontent.XContentType;
+import org.elasticsearch.core.PathUtils;
+import org.elasticsearch.core.SuppressForbidden;
 
 import java.io.BufferedInputStream;
 import java.io.BufferedOutputStream;

distribution/tools/geoip-cli/src/main/java/org/elasticsearch/geoip/GeoIpCli.java

@@ -10,11 +10,12 @@
 
 import joptsimple.OptionSet;
 import joptsimple.OptionSpec;
+
 import org.elasticsearch.cli.ExitCodes;
 import org.elasticsearch.cli.Terminal;
 import org.elasticsearch.cli.UserException;
-import org.elasticsearch.core.SuppressForbidden;
 import org.elasticsearch.core.PathUtils;
+import org.elasticsearch.core.SuppressForbidden;
 import org.elasticsearch.env.Environment;
 
 import java.nio.file.Files;

distribution/tools/keystore-cli/src/main/java/org/elasticsearch/common/settings/AddFileKeyStoreCommand.java

@@ -10,6 +10,7 @@
 
 import joptsimple.OptionSet;
 import joptsimple.OptionSpec;
+
 import org.elasticsearch.cli.ExitCodes;
 import org.elasticsearch.cli.Terminal;
 import org.elasticsearch.cli.UserException;

distribution/tools/keystore-cli/src/main/java/org/elasticsearch/common/settings/AddStringKeyStoreCommand.java

@@ -10,6 +10,7 @@
 
 import joptsimple.OptionSet;
 import joptsimple.OptionSpec;
+
 import org.elasticsearch.cli.ExitCodes;
 import org.elasticsearch.cli.KeyStoreAwareCommand;
 import org.elasticsearch.cli.Terminal;