[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283544#comment-14283544
]
David Capwell commented on BIGTOP-1608:
---------------------------------------
i believe that this is caused by the fact that itest is maven and the tests are
gradle (aka not same parent build). If you depend on a version, you would
first need to compile it (don't see anything wrong with that). Another thing,
every release would need to update the version of itest to match what you are
building. I don't believe gradle has a equivalent of mvn version plugin so you
would have to update this at all call sites. You could define the version at
the top level or in gradle properties, but you would still have to update.
If people don't want to move bigtop-test-framework to use the same build
system, I could send a patch that does a require on the jar. This would work
off your local m2 repo.
[~cos] [~jayunit100] thoughts on working with user's local m2 repo and keeping
the version in gradle.properties?
> 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)
