Description
The asflicense check runs mvn apache-rat:check from the root of the project (unless told otherwise). For a multi-module build, the build exits with failure after the first occurrence of a module with a license problem. It won't check subsequent modules. If the patch in question is touching one of those subsequent modules, then asflicense won't check it. A reviewer might incorrectly conclude that the patch is fine, because the pre-existing license problems are unrelated.
Attachments
Attachments
Issue Links
- relates to
-
YARN-4248 REST API for submit/update/delete Reservations
-
- Resolved
-