[
https://issues.apache.org/jira/browse/JCLOUDS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660060#comment-13660060
]
Andrew Phillips commented on JCLOUDS-51:
----------------------------------------
Success! https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/23/
Patch applied:
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=commit;h=5ba3068dfaea3759b4d9f6baf4890c5acc2d10fa
> Fix Karaf integration tests
> ---------------------------
>
> Key: JCLOUDS-51
> URL: https://issues.apache.org/jira/browse/JCLOUDS-51
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-karaf
> Affects Versions: 1.7.0, 1.6.1, 1.5.11
> Reporter: Andrew Phillips
> Assignee: Andrew Phillips
> Attachments: JCLOUDS-51.patch
>
>
> Now that Karaf compiles again (see JCLOUDS-41 and JCLOUDS-18) it would be
> nice if the integration tests worked again too. They are currently failing
> [1] because, as [~iocanel] explains:
> [14:29:34] Ioannis Canellos: the integration tests assume that the build
> artifacts are installed to the local maven repository
> [14:29:44] Ioannis Canellos: if they are not found there the itests will fail
> ...
> [14:30:39] Ioannis Canellos: so we have 2 options here: a) make sure we build
> using the install goal or refactor the itests so that they look under
> features module target dir
> [1]
> https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf/lastBuild/testReport/
> [2]
> https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf-1.6.x-branch/lastBuild/testReport/
--
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
