The obvious counter question is:
Why do you want to do this? Why not just fix the compile errors?
Eduardo M KALINOWSKI schrieb:
Is there a way to configure Maven to ignore source files that present
errors during compilation, and compile everything that is possible (that
is, has no error)?
I've set maven-compiler-plugin's failOnError option to "false", and the
build is considered successful despite the errors. However, no classes
are generated. Our jar file is even created, but it has nothing except
the META-INF directory.
I believe the problem happens because it's a big project (229 source
files as of now). I created a simple project with two sources, and even
without failOnError=true the source with no errors was compiled. But
when I created a lot more sources with errors, nothing was generated.
Apparently after some number of errors Maven gives up and does not try
to compile anything else. Is that assumption correct? I couldn't find
any information on that.
One possible way to solve the problem would be to manually list the
files to be excluded, and remove them from the list as they get fixed.
But this is tedious and error-prone, so I wonder if there is a better way.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
