[jira] [Commented] (BIGTOP-1201) Enhance (gradleize) the build to ease development, deployment; abstract implementation

["Roman Shaposhnik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988899#comment-13988899 ] 

Roman Shaposhnik commented on BIGTOP-1201:
------------------------------------------

All in all, super useful stuff! In fact, I can't wait to get rid of make logic and get us be 100% java based.

A few nits/questions:
  # it seems that AL headers are still missing on a few files in  buildSrc/ 
  # is buildSrc/ folder at the top level the only way to get this going? IOW, is there any chance to push this stuff to top-level src/ ?
  # should we migrate bom definition to something more sane, like json? Perhaps not in this patch, but we can totally generate the bigtop.mk from it to keep the make side of things happy for a little while
  # packages.gradle -- should we remove the commented out sections?
  # at this point, we also have the top level pom.xml driving some of the site generation and project publishing logic. How doable would it be to merge that into gradle?

> Enhance (gradleize) the build to ease development, deployment; abstract implementation
> --------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1201
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1201
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 0.7.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.8.0
>
>         Attachments: BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch, BIGTOP-1201.patch
>
>
> As has been discussed on the multiple occasions different parts of the Bigtop framework aren't really well stitched together. It requires a certain level of understanding of the project or/and digging across different sources of documentation to be able to:
>   - build Bigtop framework
>   - build and install target artifacts (packages, jars)
>   - prepared to develop or test targeted stack
>   - enforce all per-requisites consistently
>   - coordinate version updates
>   - produce documentation 
>   - <add more here>
> There are isolated attempts to patch the flaw with small pieces of scripting band-aids. However, the problem requires more systematic approach, in my opinion. What we need to have is a declarative yet flexible build system that can
>  - short to medium term: wrap isolated pieces of the framework and provide a single entry point to building, developing, deployment, and testing
>   - long term: consolidate all bits of the framework in one comprehensive build management system
> An apparent requirements of the solution:
>   - it needs to play well with JVM stack
>   - it needs to be expressive and declarative to give us flexibility to incorporate a number of currently used frameworks (maven, make, puppet) in one focal point
>   - don't limit our ability to replace (if needed) various bits of current framework with something more uniform.
> Behold, I propose Gradle.



--
This message was sent by Atlassian JIRA
(v6.2#6252)