Understand, but it's all the same: build is the code. If somebody working for you tells you otherwise - fire the guy: you're wasting your money on that "professional".
The best way to address the issue is to offer the patch to the upstream project. HBase community is quite responsive and we happen to have Andrew on-board, who's IIRC the RM for 0.98.* line, so we have a good chance to get your changes in the next update. In the meanwhile, it'd be reasonable to monkey-patch the issue at Bigtop level. Then remove the patch immediately once fixed release is incorporated to the stack. Regards, Cos On Thu, Feb 18, 2016 at 12:06AM, MrAsanjar . wrote: > Cos, I am refereeing to build and not source code changes. I would like to > make changes to pom.xml. > > On Wed, Feb 17, 2016 at 11:49 PM, Konstantin Boudnik <[email protected]> wrote: > > > There's no such option in the packaging code of our build system. Besides, > > we tend to be _extremely_ reluctant with upstream patching > > > > Cos > > > > On February 18, 2016 6:25:58 AM GMT+03:00, "MrAsanjar ." < > > [email protected]> wrote: > > >I am following instructions define at > > >https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Packaging to > > >apply a patch to upstream HBase source code. However, it is not clear > > >if > > >there is an option for conditional patching. For example, apply the > > >patch > > >only if the platform is ppc64le. help please :) > > > >
signature.asc
Description: Digital signature
