sekikn opened a new pull request, #929:
URL: https://github.com/apache/bigtop/pull/929
This PR is based on #326 submitted by @Xingwd (much appreciated!) and
includes the following updates:
* Upgrade Ranger version to 2.2.0
* Change the download site from ASF to GitHub, because the source
tarball distributed on the former is unnecessarily large
* Add package dependencies to bigtop.bom
* Remove the assembly:assembly target from the mvn command since it
doesn't work in recent releases
* Add the version info of other components to the mvn command
* Fix the lib paths in install_ranger.sh and the RPM spec file
* Add the #BIGTOP_PATCH_FILES and #BIGTOP_PATCH_COMMANDS comments to the
RPM spec so that the patches provided by Bigtop are applied during
building RPM
* Add patches for addressing RANGER-3373 and RANGER-3459
* Remove symlink to non-existent ojdbc6.jar in install_ranger.sh
* Replace the hard-coded paths to /usr/lib/rpm/redhat in the RPM spec
with %{_rpmconfigdir} (cf. BIGTOP-1344)
* Define debug_package=nil in the RPM spec to avoid build failure on
Fedora 35
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'BIGTOP-3638: Your PR title ...'.
-->
### Description of PR
See https://issues.apache.org/jira/browse/BIGTOP-2971.
### How was this patch tested?
Ran `./gradlew allclean ranger-pkg repo -Dbuildwithdeps=true` on CentOS 7,
Rocky Linux 8, and Fedora 35 (x86_64).
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'BIGTOP-3638. Your PR title ...')?
- [x] Make sure that newly added files do not have any licensing issues.
When in doubt refer to https://www.apache.org/licenses/
--
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]
