[jira] [Updated] (BIGTOP-1201) Enchanced the build to facilitrate deployment, development, and abstract implementation details

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Boudnik updated BIGTOP-1201:
---------------------------------------

    Description: 
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 for develop or test targeted stack
  - enforce all per-requisited 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.



  was:
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. install, and target artifacts (packages, jars)
  - prepared for develop or test targeted stack
  - enforce all per-requisited 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.




> Enchanced the build to facilitrate deployment, development, and abstract implementation details
> -----------------------------------------------------------------------------------------------
>
>                 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
>
>
> 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 for develop or test targeted stack
>   - enforce all per-requisited 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.1.5#6160)