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

Andrew Bayer commented on WHIRR-579:
------------------------------------

Another option would be to do something like what Jenkins does - when 
configuring a Java installer in the Jenkins management UI, you have to click 
through and accept the license/terms/etc. But then Jenkins will cache that 
downloaded tarball and reuse it on any of its slaves. So if we could add a 
click-through behavior to the Whirr CLI, we should be able to stay in line with 
the terms and conditions.

But in the meantime, OpenJDK is probably the best default option, with clear 
documentation saying "If your app won't work on OpenJDK, you'll need to install 
Oracle JDK on your boxes yourself"
                
> sun jdk install fails
> ---------------------
>
>                 Key: WHIRR-579
>                 URL: https://issues.apache.org/jira/browse/WHIRR-579
>             Project: Whirr
>          Issue Type: Bug
>          Components: service/hadoop
>    Affects Versions: 0.7.1
>         Environment: any
>            Reporter: Antonio Piccolboni
>         Attachments: WHIRR-579.patch
>
>
> Due to changes in licensing terms, automatic download from Oracle of the 
> sunjdk is not working. Hence Hadoop installs but fails to launch. To add 
> insult to injury, launch-cluster doesn't fail and I couldn't find a related 
> message in the logs. Potential workarounds need to take into account that it 
> seems like a human has to click on the dreaded Oracle TOS (disclaimer: I am 
> not a lawyer and will never be). How to make that happen with whirr is 
> unclear. The option of not supporting sunjdk seems unappealing as there is 
> limited testing experience with it, I hear from people at Cloudera. But the 
> apache hadoop compatibility page states that that sunjdk is needed only for 
> building. Clarity on this would be helpful to plan ahead.

--
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

        

Reply via email to