[
https://issues.apache.org/jira/browse/RANGER-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-5802.
------------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Merged in master:
[https://github.com/apache/ranger/commit/e705ae87046912c63d186c32834701c91d2586aa]
> Fix maven-assembly-plugin warnings in Ranger distro build
> ---------------------------------------------------------
>
> Key: RANGER-5802
> URL: https://issues.apache.org/jira/browse/RANGER-5802
> Project: Ranger
> Issue Type: Bug
> Components: maven-build, Ranger
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Every Ranger build logs over 200 warnings from maven-assembly-plugin, adding
> roughly 1,400 lines of noise to each build on developer machines and in CI.
> The warnings come from stale entries in the distro assembly descriptors:
> include/exclude rules for jars that are no longer dependencies (left behind by
> earlier dependency and library migrations), rules that can never match, and
> output paths that are not portable across platforms.
> These warnings are not only noise. The same warning is what a build prints
> when
> a tarball silently loses jars, so real packaging problems are easy to miss in
> the existing output.
> Proposed fix:
> - Remove the stale and unmatchable entries from the assembly descriptors, and
> make the non-portable output paths relative.
> - Fail the CI build when these warnings appear, so stale entries are caught in
> review rather than accumulating.
> Packaging stays the same: the contents of all distribution tarballs are
> identical before and after the change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
