Demote recompiling message from INFO to DEBUG (#333)

[elharo]

Part of #333

Changes the 'Recompiling all files because ...' log message from INFO to DEBUG level. This message is emitted for every module during incremental builds and is noisy at the default log level.

[Copilot]

Pull request overview

Reduces default build output noise during incremental builds by lowering the verbosity of the “Recompiling all files because …” reason message so it no longer appears at the default INFO level for every module.

Changes:

• Changed the incremental full-rebuild “cause” log line from INFO to DEBUG in ToolExecutor.applyIncrementalBuild(...).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ascheman]

LGTM — demoting the per-module "Recompiling all files…" message to DEBUG is a sensible noise reduction for the default log level, and it's guarded by the existing !sourceFiles.isEmpty() check so it won't fire on empty sets. Thanks @elharo.

[github-actions]

@elharo Please assign appropriate label to PR according to the type of change.

[desruisseaux]

The comment in the review saying that we should probably keep the info level when the user explicitly requested that information (with the showCompilationChanges configuration option) has not been answered. There is also the issue that we currently flood the debug level with so many records that logging anything at this level is practically lost, because debug is often used as a trace level providing no way for users to debug their build configuration without being drowned in Maven internal details.

I have create pull request #1108 for the showCompilationChanges flag. About the flood at debug level, I have no solution for now, as this is wider problem that the compiler plugin. A solution may be to create a Log.trace method and demote many debug levels to trace among all Maven core and plugins.

[ascheman]

I have create pull request #1108 for the showCompilationChanges flag. About the flood at debug level, I have no solution for now, as this is wider problem that the compiler plugin. A solution may be to create a Log.trace method and demote many debug levels to trace among all Maven core and plugins.

I like this idea (we have discussed and applied it elsewhere already).