[
https://issues.apache.org/jira/browse/BIGTOP-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000323#comment-14000323
]
Konstantin Boudnik commented on BIGTOP-1201:
--------------------------------------------
Thanks Jay. Here're the answers:
# I am not sure what you're referring to, but I would be under an impression
that it is a homogeneous build environment that doesn't require a user to go
cross framework boundaries as you perform different activities; be it packages
creation, deployment, testing, etc. I'd think having everything driven by
Gradle can accomplish it.
# The purpose of the target is to build local yum repo, so the packages can
later be installed using yum command. Actually, I need to change this because
right now this target is created for each component, which doesn't make any
sense, really. How exactly {{gradle yum}} failed? Can you be more specific?
# build.gradle lines 20-21 explains just that
{code}
// All packaging logic is separated into its own build module
apply from: 'packages.gradle'
{code}
> 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, 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)
