Compilation stopping at first error
See original GitHub issueHello guys,
I’ve developed a BugChecker here but when I compile it fails at the first error, but there are other instances of that error that I would like to show to the user.
I mean:
/Users/sergio/Documents/projects/utqg-errorprone/utqg-errorprone-sampleusage/src/test/java/com/utqg/errorprone/sample/HelloNotPassing1Test.java:10: error: [UTQG:HelperMethodCannotBePublic] Helper Methods of test classes cannot be public.
public void prepareMockedData() {
^
(see https://www.mycompany.com/utqg/HelperMethodCannotBePublic)
1 error
But there are a lot of UTQG:HelperMethodCannotBePublic errors that I would like to show to the user at same time. In the actual process, user must fix each of them separately because they are displayed separately. I also tried mvn -fae -fn options but without any success.
How can I handle it?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
Top Results From Across the Web
Using the Stop on First Error compilation mode - Overleaf
This article explains how to use Overleaf's Stop on first error compilation mode, together with reviewing some important background topics, including:.
Read more >Stop compilation after first error - Visual Studio Feedback
Clang and G++ have a -Wfatal-errors option which instructs the compiler to abort compilation after the first error. This can be useful to...
Read more >gcc compiler not stop on first error - Stack Overflow
There's a GCC compiler option -Wfatal-errors to stop after the first error: -Wfatal-errors. This option causes the compiler to abort ...
Read more >How to stop compilation on first error : r/VisualStudio - Reddit
As far as I know, Visual Studio doesn't have this feature. Instead I use the extension StopOnFirstBuildError which does exactly what it says, ......
Read more >Francesco Montorsi - Re: How to make GCC stop on first error
-Wfatal-errors This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had ran into the same issue. This is what worked in case anyone is still looking for a solution.
<compilerArg>-XepAllErrorsAsWarnings</compilerArg>
to bring down all the ERRORs to WARNs and then to make sure compiler shows warnings as well addWe would also like a way to achieve this without marking errors as warnings. In fact, we use
-Werror
in our build on purpose to fail the build if error-prone reports anything. Now it would be nice if the reports from our CI build would include all problems and not only those from one file. Marking errors as warnings would mean the CI build would not be marked as failure at all, so this is not a solution.