Merge branch 'diffplug:main' into fix-RemoveWildcardImportsStep

Author: iddeepak

plugin-gradle/README.md

@@ -92,6 +92,7 @@ Spotless supports all of Gradle's built-in performance features (incremental bui
   - [Disabling warnings and error messages](#disabling-warnings-and-error-messages)
   - [Dependency resolution modes](#dependency-resolution-modes)
   - [How do I preview what `spotlessApply` will do?](#how-do-i-preview-what-spotlessapply-will-do)
+  - [Can I apply Spotless to specific files?](#can-i-apply-spotless-to-specific-files)
   - [Example configurations (from real-world projects)](#example-configurations-from-real-world-projects)
 
 ***Contributions are welcome, see [the contributing guide](../CONTRIBUTING.md) for development info.***
@@ -1897,6 +1898,16 @@ If you use this feature, you will get an error if you use a formatter in a subpr
 
 <a name="examples"></a>
 
+## Can I apply Spotless to specific files?
+
+You can target specific files by setting the `spotlessFiles` project property to a comma-separated list of file patterns:
+
+```
+cmd> gradle spotlessApply -PspotlessFiles=my/file/pattern.java,more/generic/.*-pattern.java
+```
+
+The patterns are matched using `String#matches(String)` against the absolute file path.
+
 ## Example configurations (from real-world projects)
 
 * [A few thousand github projects](https://github.com/search?l=gradle&q=spotless&type=Code)

plugin-maven/IDE_HOOK.md

@@ -0,0 +1,16 @@
+# Spotless Maven IDE integrations
+
+## How to add an IDE
+
+The Spotless plugin for Maven accepts a command-line argument `-DspotlessIdeHook=${ABSOLUTE_PATH_TO_FILE}`.  In this mode, `spotless:check` is disabled, and `spotless:apply` will apply only to that one file.  Because it already knows the absolute path of the only file you are asking about, it is able to run much faster than a normal invocation of `spotless:apply`.
+
+For extra flexibility, you can add `-DspotlessIdeHookUseStdIn`, and Spotless will read the file content from `stdin`.  This allows you to send the content of a dirty editor buffer without writing to a file.  You can also add `-DspotlessIdeHookUseStdOut`, and Spotless will return the formatted content on `stdout` rather than writing it to a file (you should also add `--quiet` to make sure Maven doesn't dump logging info into `stdout`).
+
+In all of these cases, Spotless will send useful status information on `stderr`:
+
+- if `stderr` starts with `IS DIRTY`, then the file was dirty, and `stdout` contains its full formatted contents
+  - in every other case, `stdout` will be empty / the file will be unchanged because there is nothing to change
+- if `stderr` starts with `IS CLEAN`, then the file is already clean
+- if `stderr` starts with `DID NOT CONVERGE`, then the formatter is misbehaving, and the rest of `stderr` has useful diagnostic info (e.g. `spotless:diagnose` for [padded cell](../PADDEDCELL.md))
+- if `stderr` is empty, then the file is not being formatted by spotless (not included in any target)
+- if `stderr` is anything else, then it is the stacktrace of whatever went wrong