[
https://issues.apache.org/jira/browse/JCLOUDS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658427#comment-13658427
]
Andrew Phillips commented on JCLOUDS-41:
----------------------------------------
> git cherry-pick 12ffa28115da091e853b1d85c1d7245890ee3eb7
Erm...I would *like* to do that, but as far as I understood the ASF
requirements it's the patch attached to the issue that is the "source of
truth", not any commit anywhere.
I guess the question is: assuming something goes wrong attaching the patch to
the issue and it ends up corrupt - with your approach, the merge will still
succeed. Is that acceptable? Or would that make it, from an ASF point of view,
"unreproducible"?
> Fix Karaf compilation failure under JDK 6
> -----------------------------------------
>
> Key: JCLOUDS-41
> URL: https://issues.apache.org/jira/browse/JCLOUDS-41
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-karaf
> Affects Versions: 1.7.0
> Reporter: Andrew Phillips
> Assignee: Ioannis Canellos
> Attachments: JCLOUDS-41.patch
>
>
> Karaf currently fails to build under JDK 6:
> https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf/225/console
> See https://github.com/jclouds/jclouds-karaf/pull/3
--
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
