-
Notifications
You must be signed in to change notification settings - Fork 273
Autoprocessor fails when using Java 24 #895
Copy link
Copy link
Closed
Description
Follow up to the issue encountered during working on: #893
Reproduction Steps
$ java --version
openjdk 24.0.2 2025-07-15
OpenJDK Runtime Environment Temurin-24.0.2+12 (build 24.0.2+12)
OpenJDK 64-Bit Server VM Temurin-24.0.2+12 (build 24.0.2+12, mixed mode, sharing)
mvn clean
mvn test -Ds3proxy.test.conf=s3proxy-azurite.conf -Dtest=AwsSdkTest
Output:
Most tests fail. The key information is:
[ERROR] AwsSdkTest.setUp:135 » NoSuchElement key [azureblob-sdk] not in the list of providers or apis: {providers=[aws-s3, azureblob, b2, google-cloud-storage, rackspace-cloudfiles-us, rackspace-cloudfiles-uk], apis=[s3, atmos, glacier, openstack-swift, openstack-keystone, openstack-keystone-3, rackspace-cloudfiles, rackspace-cloudidentity, filesystem, transient, sts]}
Observations
After building with Java 11 a services file is generated for the ProviderMetadata:
target/classes/META-INF/services/org.jclouds.providers.ProviderMetadata:
org.gaul.s3proxy.azureblob.AzureBlobProviderMetadata
org.gaul.s3proxy.nio2blob.FilesystemNio2BlobProviderMetadata
org.gaul.s3proxy.nio2blob.TransientNio2BlobProviderMetadata
After compiling with Java 24: No META-INF directory is generated at all. It seems like Google's AutoService just silently fails. Complete log of mvn test -Ds3proxy.test.conf=s3proxy-azurite.conf -Dtest=AwsSdkTest is attached.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels