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

Martin Bukatovic commented on BIGTOP-1222:
------------------------------------------

{quote}
Re-compilation isn't specific to Maven. The reason it is done is because
   * tests and their execution are separated
   * tests are written as a Java or Groovy programs, not scripts
{quote}

I'm not a groovy expert, so maybe I'm missing something, but when I was 
experimenting with it, I was able to modify {{TestNode.groovy}} and run it via 
shell wrapper without explicit maven recompilation. That said your objections 
confirms my feeling that this is not quite correct approach, right?

{quote}
As I've pointed out a couple time already - there's already a way to do this by 
using {{-Dorg.apache.maven-failsafe-plugin.testInclude}} sysprop.
{quote}

Thanks for pointing this our, I need to recheck how this one works.

{quote}
 If you are talking about having a different entry-point into the test system 
to make ad-hoc experiments easier - I am all for it. And I think gradle is the 
right way to go.
{quote}

Yes, that the usecase I have in mind. Another one would be a situation when you 
are running particular bigtop testcase in from other test scripts for 
integration testing.

Anyway, I will try to look at your gradle work on BIGTOP-1201 later this week 
to better understand it.

> Completely gradleize the bigtop smokes
> --------------------------------------
>
>                 Key: BIGTOP-1222
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1222
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 0.7.0
>            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.2#6252)

Reply via email to