[
https://issues.apache.org/jira/browse/BIGTOP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750193#comment-13750193
]
Roman Shaposhnik commented on BIGTOP-1052:
------------------------------------------
I guess what I have in mind is to have a script that would maintain an illusion
that you could just run them from the source. If you think about it, that's
exactly what Groovy scripts do. Supposed you have:
{noformat}
#!/usr/bin/env groovy
println("Hello world")
{noformat}
Groovy runtime doesn't really create any jars/class files at all in this
particular case, the compilation
just happens dynamically.
> Increase pom.xml configurability of Mahout Tests
> ------------------------------------------------
>
> Key: BIGTOP-1052
> URL: https://issues.apache.org/jira/browse/BIGTOP-1052
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Reporter: jay vyas
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The TestMahoutExamples.groovy file is very comprehensive :) but also very
> long and complex. There are other JIRA's that suggest that some of the tests
> in it fail. It is different from TestHadoopExamples in that it is not easy
> to comment out the subtests to only run a subset.
> I suggest
> 1) Refactoring tests into separate groovy scripts so that they can be
> filtered in the Pom, using the includes. i.e.
> <includes>
> <include>**/*Test*MovieLens*</include>
> </includes>
> And as another convenience for the purpose of easing the running of these
> tests, I suggest
> 2) Utilizing MAHOUT_HOME environmental variable in the tests if it is
> provided, so that the mahout package installation can be tested directly from
> tarballs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
