Ability to read S3 URI while dryRun instead of relying on Http(s)

[Goel-Akshit]

What problem are you trying to solve?

My organization uses AWS S3 for hosting Maven repositories, which are accessed using s3:// URIs. While Maven resolves dependencies correctly using these URIs, the OpenRewrite framework seems unable to handle them. This prevents us from effectively running OpenRewrite commands like rewrite:dryRun and utilizing its functionality in our projects.

Describe the solution you'd like

ability to access the maven repository using s3 URI.

Have you considered any alternatives or workarounds?

1. I tried using S3 folder URL https://s3.ap-south-1.amazonaws.com/bucketName.maven.repo/release/
2. I tried using rewrite.yml as
   repositories:
   - id: s3.release
   uri: s3://bucketName.maven.repo/release
   - id: s3.snapshot
   uri: s3://bucketName.maven.repo/snapshot

Additional context

[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
......

[timtebeek]

Hi @Goel-Akshit ; indeed this has not been added yet, as indicated here.

rewrite/rewrite-maven/src/main/java/org/openrewrite/maven/internal/MavenPomDownloader.java

Lines 782 to 783 in a3249f2

	// can be s3 among potentially other types for which there is a maven wagon implementation
	ctx.getResolutionListener().repositoryAccessFailed(repository.getUri(), new IllegalArgumentException("Repository " + repository.getUri() + " is not HTTP(S)."));

If you'd like to help bring this to OpenRewrite that would be much appreciated, or we have plenty of folks willing to build that functionality on contract for you if you can make the business case internally to do so.