hbase/hbase-mapreduce
Bryan Beaudreault fd5b526398 Add maven and RPM building in blazar
This uses our standard buildpack, but each module must get a custom .blazar.yaml to pass in required
properties to the build. One can distribute that .blazar.yaml using build-scripts/copy_blazar_yaml.sh.
In order to minimize the duplication, most of the customizations are consolidated in
build-scripts/prepare_environment.sh.

The RPM build is hooked into the standard build hbase-assembly, as a post-build step. The RPM build
scripts in hbase-assembly/rpm-build handle turning the assembled tar.gz into multiple RPMs. We required
some minor changes to the descriptor in hbase-assembly to account for the fact that our build processes
each module independently instead of as a single reactor build. As a result, moduleSet does not work, so
moduleSet usages were converted to dependencySet.
2021-09-24 15:51:16 -04:00
..
src HBASE-26106 AbstractFSWALProvider#getArchivedLogPath doesn't look for wal file in all oldWALs directory. (#3636) 2021-09-02 12:08:49 -07:00
.blazar.yaml Add maven and RPM building in blazar 2021-09-24 15:51:16 -04:00
pom.xml Preparing hbase release 2.4.6RC0; tagging and updates to CHANGES.md and RELEASENOTES.md 2021-09-03 09:41:52 -07:00