You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2014/12/29 10:00:39 UTC

[jira] [Commented] (JCLOUDS-797) OkHttp module requires JDK 1.7

    [ https://issues.apache.org/jira/browse/JCLOUDS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259950#comment-14259950 ] 

Ignasi Barrera commented on JCLOUDS-797:
----------------------------------------

This was already commented in this thread:
http://markmail.org/message/sqlpgah5vrq5z6op

Code needs to be compiled with Java 7 but is runtime compatible with Java 6, to satisfy JCLOUDS-747. The filesystem provider is the only one that actually uses Java 7 methods that are not available in Java 6, and it has a [custom Animal Sniffer configuration |https://github.com/jclouds/jclouds/blob/3ed8db78733afd0ef3438f950df92a8f21bb45ed/apis/filesystem/pom.xml#L100-L110]. It is the only exception to this runtime portability.

If this makes sense, can this issue be closed?

> OkHttp module requires JDK 1.7
> ------------------------------
>
>                 Key: JCLOUDS-797
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-797
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-drivers
>    Affects Versions: 2.0.0
>            Reporter: Andrew Gaul
>
> jclouds no longer compiles with JDK 1.6 due to OkHttp's dependency on JDK 1.7:
> {noformat}
> $ mvn clean install -DskipTests
> [ERROR] COMPILATION ERROR :
> [ERROR] /home/gaul/work/jclouds/drivers/okhttp/src/main/java/org/jclouds/http/okhttp/OkHttpCommandExecutorService.java:[122,33] cannot access java.nio.file.Path
> class file for java.nio.file.Path not found
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project jclouds-okhttp: Compilation failure
> [ERROR] /home/gaul/work/jclouds/drivers/okhttp/src/main/java/org/jclouds/http/okhttp/OkHttpCommandExecutorService.java:[122,33] cannot access java.nio.file.Path
> [ERROR] class file for java.nio.file.Path not found
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :jclouds-okhttp
> {noformat}
> We can use a workaround like we do for the filesystem blobstore to address this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)