I tracked the jclouds-karaf test failure to using Java 8 for the build. All tests are failing, but only the last one is being reported. Looks like Karaf 2.3.11 is not compatible with Java 8 and there's not much we can do about it at this point. Andrea's PR [1] addresses this problem for future releases by upgrading Karaf to an up-to-date version which can work with Java 8.
Note that jclouds-karaf artifacts are still usable with Java 8. The problem is with the test setup. Svet. [1] https://github.com/jclouds/jclouds-karaf/pull/92 > On 21.02.2017 г., at 22:43, Ignasi Barrera <ignasi.barr...@gmail.com> wrote: > > BTW, the CI build passes: > https://jclouds.ci.cloudbees.com/job/jclouds-karaf-2.0.x-branch/ > > Can you try building it with a clean Maven repo? > > On Feb 21, 2017 9:40 PM, "Ignasi Barrera" <ignasi.barr...@gmail.com> wrote: > >> I'll have it fixed. >> >> Didn't fail for me (OSX) but perhaps I had something cached in the local >> maven repo. >> >> I'll cancel the vote in a while and push all the fixes. >> >> On Feb 21, 2017 7:53 PM, "Andrea Turli" <andrea.tu...@gmail.com> wrote: >> >>> I'm seeing the same problem from osx. >>> >>> Shall we fix that for RC2? >>> >>> Il mar 21 feb 2017 19:40 Andrew Gaul <g...@apache.org> ha scritto: >>> >>>> Can anyone reproduce the failing karaf vagrant symptoms when running the >>>> verify script? I am running on Ubuntu 14.04 using JDK 1.8.0_121. I >>>> attached the logs. >>>> >>>> On Tue, Feb 21, 2017 at 05:05:19PM +0100, Ignasi Barrera wrote: >>>>> Hi! >>>>> >>>>> While testing the new Azure ARM security group extension I've found a >>>>> small issue here [1]. Basically we are not dealing properly the "all >>>>> protocols" firewall rules, and will always fail to create them. >>>>> >>>>> Given that the SecurityGroupExtension (along with Packet and Vagrant) >>>>> is one of the important features we're releasing in 2.0.1, I'd like to >>>>> propose to cancel the RC1 and cut a RC2 with a fix for that. >>>>> The fix is pretty straightforward, and I'd also have a look at the >>>>> vagrant feature thing in Karaf (although all tests passed locally for >>>>> me). >>>>> >>>>> WDYT? The change would only affect labs. I don't pretend to be >>>>> releasing the other unrelated repos again, so I hope to be able to >>>>> have the RC2 prepared tonight/early tomorrow. >>>>> >>>>> >>>>> Cheers! >>>>> >>>>> I. >>>>> >>>>> >>>>> [1] >>>> https://github.com/jclouds/jclouds-labs/blob/master/azurecom >>> pute-arm/src/main/java/org/jclouds/azurecompute/arm/ >>> compute/extensions/AzureComputeSecurityGroupExtension.java#L217 >>>>> >>>>> On 19 February 2017 at 20:59, Andrew Gaul <g...@apache.org> wrote: >>>>>> I attached integration test results against aws-s3, azureblob, b2, >>>>>> filesystem, glacier, google-cloud-storage, rackspace-cloudfiles-us, >>> s3 >>>>>> (dreamhost), and transient. >>>>>> >>>>>> On Fri, Feb 17, 2017 at 05:05:24PM +0100, Ignasi Barrera wrote: >>>>>>> This thread is for discussion of the first release candidate for >>>>>>> Apache jclouds 2.0.1. >>>>>>> Please use this thread for discussion of issues uncovered in the >>> RC, >>>>>>> questions you may have about the RC, etc. >>>>>>> >>>>>>> If you want to help validating the release, you can follow these >>>> instructions: >>>>>>> >>>> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release >>>>>>> >>>>>>> >>>>>>> Thank you! >>>>>> >>>>>> -- >>>>>> Andrew Gaul >>>>>> http://gaul.org/ >>>> >>>> -- >>>> Andrew Gaul >>>> http://gaul.org/ >>>> >>> >>
