[
https://issues.apache.org/jira/browse/JCLOUDS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662272#comment-13662272
]
Andrew Gaul commented on JCLOUDS-56:
------------------------------------
While this builds, it does not run. I pushed a fix to master as
0bf6499b35cef3e868a8d69821a90c1041c38512, to 1.6.x as
1a6c01f56a34f184e8d19cdc6cd95673ad427c15, and to 1.5.x as
fa53aa368761b3b0fffa2ae71e73b88271cc21b0. I suspect I made a mistake on the
Windows side in master only and opened a pull request here:
https://github.com/jclouds/jclouds-cli/pull/3
> Fix jclouds-cli build and tests
> -------------------------------
>
> Key: JCLOUDS-56
> URL: https://issues.apache.org/jira/browse/JCLOUDS-56
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-cli
> Affects Versions: 1.7.0, 1.6.1, 1.5.11
> Reporter: Andrew Phillips
> Assignee: Andrew Phillips
> Fix For: 1.7.0, 1.6.1, 1.5.11
>
> Attachments: JCLOUDS-56-1.6.x.patch, JCLOUDS-56.patch
>
>
> All three jclouds-cli CI builds are currently broken :-(
> https://jclouds.ci.cloudbees.com/view/cli/job/jclouds-cli/
> https://jclouds.ci.cloudbees.com/view/cli/job/jclouds-cli-1.6.x-branch/
> https://jclouds.ci.cloudbees.com/view/cli/job/jclouds-cli-1.5.x-branch/
--
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
