[
https://issues.apache.org/jira/browse/WHIRR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152994#comment-13152994
]
Alex Heneveld commented on WHIRR-415:
-------------------------------------
Patch looks sensible, might not have the chance to test it for a few days.
Combining version test with regular test is simpler, although my thinking was
that it was better to have integration test which tests a specific version
which is testably distinct from what you get when you request the latest.
Although that said, I was (with all the WHIRR-427 errors) wondering whether we
might hit version errors at the pom level -- locally we are locked to one
version for the project, so could be problematic testing multiple versions on
the other end if they aren't compatible with the local one.
So fine either way.
> Let users specify the CDH release (cdh3u1, cdh3u2)
> --------------------------------------------------
>
> Key: WHIRR-415
> URL: https://issues.apache.org/jira/browse/WHIRR-415
> Project: Whirr
> Issue Type: Improvement
> Components: service/cdh
> Reporter: Andrei Savu
> Priority: Critical
> Fix For: 0.7.0
>
> Attachments: WHIRR-415-env.patch, WHIRR-415-whirr.env.patch,
> WHIRR-415.patch, WHIRR-415.patch
>
>
> Allow explicit selection of the CDH release you want to use. The current
> behaviour is to use the latest one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
