On the fly hash before and after to replace current caching system files. about formatter-maven-plugin HOT 1 OPEN

If the hypothesis is correct that it's the reading/writing the files that's the slow part and always formatting isn't harmful to performance, then this seems like a good improvement.

I think it could still be useful to allow forcing writing formatted files, regardless of whether the before/after hashes match... for the extremely rare cases where there is a hash collision or the user wants to be absolutely sure things were formatted. Such a flag could even be a hidden flag, for development purposes... like using a Java system property rather than something set in the Maven configuration.

I would be curious to know what the impact would be on a large build, for both the already-formatted case, and the not-formatted case.

If this change works better, the old caching file could not just be deprecated, but turned into a NOOP to be removed later.

from formatter-maven-plugin.