[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-08-27 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-682237714


   Probably a few months.  We are still working on the OkHttp and gson 
dependencies.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-24 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-648842815


   @nacx Any further comments?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-16 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-644772816


   > Hello, we use your JClouds in our OSGi project. Actually OSGi and all the 
regulations around packet exports is a difficult topic. Especially when an OSGi 
compatibility is set by a library and others still access restricted areas of 
the library.
   
   @gurkerl83 thanks for chiming in.  We lack OSGi expertise and would 
appreciate if you could submit any improvements.  I am trying to modernize the 
dependencies and fear that this will break things I cannot test like OSGi.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-16 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-644771814


   > Is this because of the certificates we use in tests? Or something spotted 
running live tests, or because how we configure the SSL module by default? It 
would be great if we could upgrade and not be tied to older JDKs.
   
   #71 should resolve the certificate length but we need to upgrade 
BouncyCastle first.   I don't remember exactly but that was blocked on another 
dependency.  Working through these...



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-14 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-643729091


   Also need to use an older JDK to work around weak 1024-bit SSL certificates. 
 I found that `OrganizationApiExpectTest.testDeleteGroupFailsOn404` fails due 
to special handling in `ChefErrorHandler.handleError`.  Commenting this out 
allows the test to succeed but I don't understand how it passed before.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-13 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-643726148


   This is strange, `mvn test` cannot find gson but `mvn install` makes 
progress until failing tests.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [jclouds] gaul commented on pull request #75: JCLOUDS-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22

2020-06-13 Thread GitBox


gaul commented on pull request #75:
URL: https://github.com/apache/jclouds/pull/75#issuecomment-643711607


   This will likely fail in CI due to configuration but locally tests fail due 
a gson issue.  I don't understand our tower of hacks.  @nacx Any suggestions on 
how to address this?
   
   ```
   [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project jclouds-core: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test failed: There was an 
error in the forked process
   [ERROR] java.lang.NoClassDefFoundError: com/google/gson/TypeAdapterFactory
   [ERROR] at java.lang.ClassLoader.defineClass1(Native Method)
   [ERROR] at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
   [ERROR] at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   ...
   [ERROR] Caused by: java.lang.ClassNotFoundException: 
com.google.gson.TypeAdapterFactory
   [ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
   [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
   [ERROR] at 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
   [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
   [ERROR] ... 39 more
   ```



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org