Dennis-Mircea Ciupitu created FLINK-39565:
---------------------------------------------
Summary: Eliminate maven build warnings across all modules
Key: FLINK-39565
URL: https://issues.apache.org/jira/browse/FLINK-39565
Project: Flink
Issue Type: Improvement
Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.14.0
Reporter: Dennis-Mircea Ciupitu
Fix For: kubernetes-operator-1.15.0
h1. Description
{{mvn clean install}} currently emits hundreds of {{[WARNING]}} lines spread
across multiple maven plugins (RAT, CycloneDX, shade, assembly) and several
modules (operator, autoscaler-standalone, webhook, examples). None of them
block the build, but they mask legitimate signal during local builds, code
review, and CI runs, and they tend to accumulate as new contributions land on
top of an already-noisy baseline.
h1. Goal
Bring the build to zero {{[WARNING]}} output, while preserving runtime behavior
of the operator, autoscaler, webhook, and example modules.
h1. Scope
* Upgrade build plugins to recent versions whose deprecated parameters and
obsolete configuration shapes are the source of most warnings.
* Migrate plugin configurations to the supported, non-deprecated schema.
* Tighten plugin configuration where the previous defaults silently masked
policy gaps (e.g. RAT approving non-Apache license families).
* Make shade-plugin packaging deterministic by declaring explicit "winner"
filters for the few intentional class-level forks instead of relying on
undocumented include order.
* Properly merge resources that must not be overwritten last-write-wins (e.g.
Log4j2 plugin descriptors).
* Adjust the published artifact / dep-reduced pom story so downstream modules
can keep compiling against the operator as a normal Maven dependency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
