[jira] [Commented] (JCLOUDS-1568) Support for connectivity via VPC Endpoint(AWS PrivateLink)

[ https://issues.apache.org/jira/browse/JCLOUDS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17305283#comment-17305283 ] Andrew Gaul commented on JCLOUDS-1568: -- We will gladly accept a pull request for this feature. >

[jira] [Updated] (JCLOUDS-1568) Support for connectivity via VPC Endpoint(AWS PrivateLink)

[ https://issues.apache.org/jira/browse/JCLOUDS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1568: - Labels: aws-s3 (was: ) > Support for connectivity via VPC Endpoint(AWS PrivateLink) >

[jira] [Created] (JCLOUDS-1569) "did not receive expected response code and header" during undeploy request

Simone created JCLOUDS-1569: --- Summary: "did not receive expected response code and header" during undeploy request Key: JCLOUDS-1569 URL: https://issues.apache.org/jira/browse/JCLOUDS-1569 Project: jclouds

[jira] [Created] (JCLOUDS-1568) Support for connectivity via VPC Endpoint(AWS PrivateLink)

Blagoi Anastasov created JCLOUDS-1568: - Summary: Support for connectivity via VPC Endpoint(AWS PrivateLink) Key: JCLOUDS-1568 URL: https://issues.apache.org/jira/browse/JCLOUDS-1568 Project:

[GitHub] [jclouds] gaul opened a new pull request #101: Upgrade to error-prone 2.5.1

gaul opened a new pull request #101: URL: https://github.com/apache/jclouds/pull/101 This addresses issues seen with more recent Java and Maven versions. Enabled by requiring Java 8. Also suppress several new warnings and remove stale ones. This commit also adds the missing jaxb and