[
https://issues.apache.org/jira/browse/BIGTOP-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849792#comment-13849792
]
jay vyas commented on BIGTOP-1097:
----------------------------------
Given that right now ALL of the groovy stuff in bigtop is for itest/smokes,
which run via maven and automagically grab groovy for us:
$> find ./ -name *groovy | grep -v "test-framework" | grep -v "test-artifacts"
| wc -l
0
Adding groovy as something that bigtop repackages seems like adding complexity
that doesnt really have any clear benefit. If we do so lets be very clear
about the direction of things: Is bigtop moving towards using groovy as a core
element of the core package build and deploying?
As of now, groovy is only used for test-artifacts and test-execution and itest.
> introduce bigtop-groovy package
> -------------------------------
>
> Key: BIGTOP-1097
> URL: https://issues.apache.org/jira/browse/BIGTOP-1097
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.6.0
> Reporter: Roman Shaposhnik
> Assignee: Konstantin Boudnik
> Fix For: 0.8.0
>
>
> Bigtop platform depends on groovy extensively and we see a trend to introduce
> new functionality into the cluster deployment, etc. that will greatly benefit
> from the presence of a dynamic, functional scripting language on top of JVM.
> Hence, it makes sense to provide Groovy runtime environment as a part of
> Bigtop installable stack (e.g. think of bigtop-utils type of package). It
> will be lightweight and only needs to include a couple of jar files from a
> standard Groovy distribution. There's no need to build Groovy from scratch
> but just download the binary archive, extract jars we need, and wrap them
> into a Linux package.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
