|
Ben Caradoc-Davies [Administrator] created an issue |
Upgrade joda-time to support Amazon AWS S3 on Java 8u60 or later |
Issue Type: |
|
---|---|
Affects Versions: |
2.9-beta |
Assignee: |
|
Components: |
Global, GWC |
Created: |
17/Jan/16 10:58 PM |
Environment: |
|
Priority: |
|
Reporter: |
joda-time before 2.8.1 causes Java 8u60 or later to fail to connect to Amazon AWS S3 with the error “AWS authentication requires a valid Date or x-amz-date header” when configuring a GeoWebCache S3 blob store via the GeoServer web interface: See: GeoWebCache gwc-aws-s3 unit tests pass with Java 8u72 because aws-java-sdk-core 1.9.30 depends on joda-time [2.2,), which resolves to the latest joda-time 2.9.1, which works with Java 8u72: GeoServer has a fixed dependency on joda-time to 2.2, which satisfies the transitive dependency on aws-java-sdk-core via gs-gwc-s3, but is incompatible with Java 8u60 or later. The solution is to change the GeoServer dependencyManagement version of joda-time to 2.8.1 or later. Although GeoWebCache gwc-aws-s3 is currently building against 2.9.1, later aws-java-sdk-core (e.g. 1.10.47) has a fixed dependency on 2.8.1 so it may be more consistent to fix the GeoServer dependency as joda-time 2.8.1: We could instead use explicit dependencies for both GeoServer and GeoWebCache on joda-time 2.9.1 and see if Maven can handle the version management. There are other GeoServer modules that user joda-time. |
This message was sent by Atlassian JIRA (v7.1.0-OD-04-012#71001-sha1:dd0493d) |
|