-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b15
The javac -Xmaxerrs/-Xmaxwarns flags could be made more discoverable. Sometimes the diagnostic that best explains a failing build is truncated because the warning or error limit has already been reached, and the problem may be difficult to diagnose for users that aren't aware of -Xmaxerrs/-Xmaxwarns.
One possible solution would be to add something similar to e.g. compiler.note.unchecked.recompile, which notes that diagnostics were suppressed and mentions that recompiling with a larger value of -Xmaxerrs/-Xmaxwarns will show more information.
For example:
# 0: number, 1: number
compiler.misc.count.error.recompile=\
{0} more errors not shown; recompile with -Xmaxerrs {1} to see them
# 0: number, 1: number
compiler.misc.count.warn.recompile=\
{0} more warnings not shown; recompile with -Xmaxwarns {1} to see them
One possible solution would be to add something similar to e.g. compiler.note.unchecked.recompile, which notes that diagnostics were suppressed and mentions that recompiling with a larger value of -Xmaxerrs/-Xmaxwarns will show more information.
For example:
# 0: number, 1: number
compiler.misc.count.error.recompile=\
{0} more errors not shown; recompile with -Xmaxerrs {1} to see them
# 0: number, 1: number
compiler.misc.count.warn.recompile=\
{0} more warnings not shown; recompile with -Xmaxwarns {1} to see them