Hello Community, I want to propose following improvements for apex-core build and related steps:
1. Most (probably all of the open source project) has the a binary release package of the software and not just the source release package. Currently we have only source package. Luckily there are few places (outside of apache apex) where binary packages of apex has been created for different purposes : https://github.com/atrato/apex-cli-package & https://github.com/apache/bigtop) Proposal here is generate this binary release package as a part of build process of apex-core. 2. Currently, the docker build that is being created for apex is built one of my personal repository (https://github.com/chinmaykolhatkar/docker-pool). While I don't mind hosting the content (Dockerfile etc...) in my repository, I believe it make sense to host this in apex-core repository. This way, there is a possibility of using docker github triggers for building the docker image from release branches. 3. Currently the docker build uses hadoop and apex specific packages from bigtop deb repo & CI. (See https://github.com/chinmaykolhatkar/docker-pool/blob/master/apex/ubuntu/app/setup.sh for more details) While use of hadoop packages from bigtop repo is fine, we also need to rely on bigtop contribution to update apex component and then build from bigtop CI for getting apex.deb package. Basically our docker image generation process gets blocked on bigtop source update to generate the updated apex deb. As we technically don't need to depend on bigtop to generate the apex binary, the proposal here is to generate binary package during build process (point 1) and use that during docker image build process instead of using the ready made deb package from bigtop CI. I understand that there are multiple items being mention in a single mail but they seem related hence the mail. Please let me know your opinion on above items. Thanks, Chinmay.
