-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mill build fails to render compiler warning with format specifiers #2105
Comments
Thanks for this report. I think, this is an issue in sbt zinc regarding handling of log messages, and it should be reported upstream. We previously reported similar issues , e.g. in sbt/zinc#1122, but also in chats. Can you check with a recent Mill snapshot release? Maybe, #2087 already fixes (in the sense of "avoid") it already? If not, please report it upstream. |
To elaborate on this. I'm not familiar with log4j2, I only used older version log4j1 and friends, as well as SLF4J with logback, which don't have such problems. But it seems to me, that the log messages are post-processed after given to the log4j2 logger with something like |
What do I have to put into |
The release pages list all released snapshot artifacts. E.g. latest snapshot after |
GitHub hides the snapshot releases from me. Anyway, |
I forgot to mention, that snapshot releases are attached to the page of the latest previous tag, so you'll find all "after 0.10.8" snapshots on the "0.10.8" release page as attached artifacts. Great, that it fixes the issue. I'm closing this issue then, as we do what we can to work around it in Mill. To really fix the upstream issue, it should be reported to sbt-zinc. |
Reproduction
Install or switch to Java 19, then execute:
The build does not fail but reports an error because some
sbt
library fails to format a warning produced bydotty
:Notice that the warning contains application code with format specifiers.
I am reporting this as a
mill
issue because it's not clear to me which component (dotty
,mill
, orsbt
) is supposed to escape the format specifiers.Full output
Expected output
The text was updated successfully, but these errors were encountered: