And actually, I take my agreement back (all the more a good reason to have fine-grained commits: you can simply revert one if it is not sound): from https://github.com/TotallyPro/nar-maven-plugin/blob/7e08d9dbef16bd21ce583adb3c68ac7390f17e5d/src/main/java/com/github/maven_nar/NarLogger.java#L89 it is relatively obvious that the NarLogger defaults to the DEBUG log level *except* when the message suggests compilation or linking.

Now, I agree that this is counter-intuitive: the INFO log level should not demote messages back to DEBUG (which is not shown by default, as opposed to WARn or ERROR, which have a *higher* priority than INFO). But the correct fix is to skip the test for "files were compiled" or "Linking..." in addition to the hunk shown above.

But again, this is a logically-separate fix from the commit we're commenting on. It needs to be split off into its own commit. We're not in politics here, where you can tack on tax exemptions onto an agriculture bill or some insanity like that. We're doing Open Source, so we have the luxury of keeping things clean and proper.