[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284025#comment-14284025
]
jay vyas edited comment on BIGTOP-1608 at 1/20/15 5:19 PM:
-----------------------------------------------------------
hmmm.. i *may* be in the minority on this one :) ... ([~dcapwell] i definetly
agree good to restructure all tests to a single system.)
if running from jar files is less confusing (not sure why running a jar file
is easier than running from source), we can go back to using run 4 maven
commands which take 8 minutes instead of one gradle command that takes 30
seconds.
but at the very least : lets not wrap maven into gradle (unless *maven* really
is doing something we cant easily do in gradle)? that won't solve anything
other than just making two levels of java indirection for something that really
could just be done in a shell script.
was (Author: jayunit100):
hmmm.. i *may* be in the minority on this one :) ...
if running from jar files is less confusing (not sure why running a jar file
is easier than running from source), we can go back to using run 4 maven
commands which take 8 minutes instead of one gradle command that takes 30
seconds.
but at the very least : lets not wrap maven into gradle (unless *maven* really
is doing something we cant easily do in gradle)? that won't solve anything
other than just making two levels of java indirection for something that really
could just be done in a shell script.
> all smoke-tests should compile and use iTest as source, no jar. Remove ITEST
> env variable.
> -------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1608
> URL: https://issues.apache.org/jira/browse/BIGTOP-1608
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Reporter: David Capwell
> Assignee: David Capwell
> Attachments: BIGTOP-1608-first-part.patch, BIGTOP-1608.1.patch
>
>
> If you try to run the smoke tests without setting {{BIGTOP_HOME}} they will
> run and be unable to find tests, so nothing runs. This variable should be
> added to checkEnv to make sure its present while running
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
