You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+ "' does not exist, failing build (failOnUnknownFolder is true).";
getLog().error(message);
thrownewMojoFailureException(message);
} else {
getLog()
.warn(directoryDisplayName + " directory '" + directory + "' does not exist, ignoring.");
}
}
It looks like it will WARN you of a missing directory even if you explicitly excluded that directory from being checked (even if it does in fact exist).
To me it feels like this is the kind of information that deserves to be logged but at a INFO level, otherwise it leads to 'warning fatigue' because most of the time this isn't something that people will act on and it's also not possible to disable.
The text was updated successfully, but these errors were encountered:
cgoeller
added a commit
to cgoeller/fmt-maven-plugin
that referenced
this issue
Oct 28, 2024
Describe the bug
We're currently getting a WARN-level log line when one of the Maven modules doesn't have a
tests
directory.The code responsible for this:
fmt-maven-plugin/src/main/java/com/spotify/fmt/AbstractFMT.java
Lines 104 to 108 in 1cf19c0
fmt-maven-plugin/src/main/java/com/spotify/fmt/AbstractFMT.java
Lines 184 to 198 in 1cf19c0
It looks like it will WARN you of a missing directory even if you explicitly excluded that directory from being checked (even if it does in fact exist).
To me it feels like this is the kind of information that deserves to be logged but at a INFO level, otherwise it leads to 'warning fatigue' because most of the time this isn't something that people will act on and it's also not possible to disable.
The text was updated successfully, but these errors were encountered: