I do not have that build failure, or I would have addressed it. I can fix in the same branch and push. Did it build otherwise before? I thought that issue in Jira was open for it failing under 1.8 or something. Also I am using guava 24 and Java 9. Though I would imagine Java 9 to be pickier. I had Jclouds building under 1.8 before. I guess maybe my failing came with 9.
How come the CI build didn't fail? The patch doesn't really change anything to cause a failure. I think maybe its just not addressing all issues. Though not sure why I do not run into that. Maybe a guava issue. Can you try with gauva 24? Just curious, I can address either way. Likely just another static import change... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1180#issuecomment-366173965
