adoroszlai commented on PR #10537:
URL: https://github.com/apache/ozone/pull/10537#issuecomment-4742985727
> As far as I understand the fix is to disable incremental build for the
parts that do shading/renaming.
1. We already have `useIncrementalCompilation=false` set globally:
https://github.com/apache/ozone/blob/48613a7a050eb12f16f5bf822abcdd5e70cf0a93/pom.xml#L1830
2. `useIncrementalCompilation` behavior may not be what you expect, please
see [MCOMPILER-209](https://issues.apache.org/jira/browse/MCOMPILER-209) for
long discussion and the
[documentation](https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#useincrementalcompilation)
added in [MCOMPILER-428](https://issues.apache.org/jira/browse/MCOMPILER-428):
> - true (**default**) in this mode the compiler plugin determines whether
any JAR files the current module depends on have changed in the current build
run; or any source file was added, removed or changed since the last
compilation. If this is the case, the compiler plugin recompiles all sources
> - false (**not recommended**) this only compiles source files which are
newer than their corresponding class files, namely which have changed since the
last compilation. This does not recompile other classes which use the changed
class, potentially leaving them with references to methods that no longer
exist, leading to errors at runtime
I don't know if the description is accurate or not, but you might want to
experiment with setting it to `true`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
