[
https://issues.apache.org/jira/browse/BIGTOP-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912543#comment-13912543
]
Konstantin Boudnik commented on BIGTOP-1222:
--------------------------------------------
Jay, the point is that you don't need to hack pom files to run tests - the
filtering mechanism is built into the execution framework. All you need to do
is to set a system property (check the common module for the names, I don't
remember them off hand) in the command line. It might be simplified somewhat -
there's no question about it. And that's the whole point of my bringing Gradle
to consolidate the entry points.
Let me sched a bit of light on why something as structural as Maven - or a
similar approach that provides tight control over the dependencies - is
beneficial in the case of Bigtop. Bigtop makes guarantees that the tests one
runs against a stack have the same version of dependencies as the stack itself.
Thus the guarantee that we are comparing carrots to carrots and not to
potatoes. Because Bigtop has been designed with having multiplicity of target
stacks in mind, we had to pick a mechanism with a strickter level of control. I
admit again - while Maven model provides great contol over the dependencies -
it has a long way to go wrt UX. In other words - XML sucks and blows at the
same time. But there's a big but here: providing the same level of guarantees
of the coherent dependencies management using something like shell would be
challenging (to say it politely).
So to rephrase: I agreen that Maven thing needs to be improved. No one in sound
mind will argue with that. However, I am highty doubtful that shell is the
right and/or better alternative. So, looks like Gradle is a sensible middle
ground - as you've mentioned above. Now, let's focus on making it happen. Am I
making sense?
> Completely gradleize the bigtop smokes
> --------------------------------------
>
> Key: BIGTOP-1222
> URL: https://issues.apache.org/jira/browse/BIGTOP-1222
> Project: Bigtop
> Issue Type: Improvement
> Reporter: jay vyas
>
> Currently, there is a JIRA underway to make running the maven based smoke
> tests easier: BIGTOP-1195.
> Eventually, however, maybe we could run these smokes from gradle. I think
> that will obviate BIGTOP-1195 (Although i still assert a bash driver is a big
> win/gain for bigtop's goals : which are to unify the hadoop packaging and
> deployment paradigm).
> - run the smokes using a simple gradle goal
> - smokes should be easily runnable as scripts, with no need for jar file
> intermediates.
> - The bash driver for BIGTOP-1195 (if accepted, still under debate) should be
> upgraded to use the new gradle smokes
> - Delete old maven smokes.
> This might be a little ambitious, if so others chime in. I'm not a
> gradle/groovy expert but getting more well versed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
