Compiler error when aws-java-sdk in pom.xml was updated from 1.x.x to 2.x.x

[pjonnlagadda]

Describe the bug

As i am trying to migrate aws-sdk-java from V1 to V2,
to make start i have replaced the artifacts in pom.xml accordingly for S3, STS, SQS and IAM etc.. . Later when i am trying to build, getting few of the compile errors saying that, classes like AmazonSQS, SQSActions are missing and many other compile errors for few other classes. Seems the package "com.amazonaws.auth.policy" is missing.
Ex:-
constructor S3BucketResource in class com.amazonaws.auth.policy.resources.S3BucketResource cannot be applied to given types;
required: java.lang.String
found: java.lang.String,java.lang.String

Expected Behavior

Is there any smooth way to replace V2 from V1?

Current Behavior

getting few of the compile errors saying that, classes like AmazonSQS, SQSActions are missing

Reproduction Steps

Replace the artifacts in pom.xml accordingly for S3, STS, SQS and IAM etc.

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

AWS SDK for Java 2.0

JDK version used

java 1.8

Operating System and version

Windows 11 Enterprise

[yasminetalby]

Hello @pjonnlagadda ,

Thank you very much for your submission.
Could you please clarify the following:
Is the only step you have took to migrate modifying the pom.xml file with v2 artifact?

There exists multiple changes between the two versions. You would need to update your code appropriately while migrating from v1 to v2.

The Developer Guide describes the main changes to be aware of when converting an application from using the AWS SDK for Java version 1.x to version 2.x.

The 1.11 to 2.0 Changelog is also a good resource to see changes between the two versions.

If your application depends on libraries that have not yet been released in version 2.x, see Using both SDKs side-by-side to learn how to configure your pom.xml to use both 1.x and 2.x.

Best,

Yasmine

[pjonnlagadda]

Hi @yasminetalby ,
Thank you for the response.
regarding your question "Is the only step you have took to migrate modifying the pom.xml file with v2 artifact?"
Yes, The very first step i started with replacing the pom.xml entries only.
Not modified any code changes before changing form V1 to V2

[yasminetalby]

Hello @pjonnlagadda ,

Thank you very much for the information.

You will need to update your code based on the changes between the two version of the SDK.
You can find most documentation on the resources I have shared above!

Another good resource to look at for an overview of the use of different services in AWS Java SDK v2 is in aws-docs/aws-doc-sdk-examples/javav2/example_code.

This does not seems like a bug but more a documentation question so I will change the label on the issue.
Let me know if you have any question or if there is any information that is not provided by the documentation that I can help with!

Sincerely,

Yasmine

[pjonnlagadda]

Hi @yasminetalby,
Thank you very much for the valuable info.

So the final conclusion you mean,
Step 1:- Start using side – by side
Step 2:- Start making the code changes for migration of the services which we are using from V1 to V2(Ex:- to S3, SQS, IAM, STS etc..)
Step 3:- In future Once all the changes are migrated from V1 to V2(long process), we can completely remove the V1 entries from Pom.xml if everything is supported in V2

As I we have policy related classed in V1 com.amazonaws.auth.policy are found in the V2 test folder. But not all. Any idea where I can found them all or any examples like how can we start using them in the V2?
or the usage of Statement, Principal, Condition, Policy etc..

Thanks in Advance.

[yasminetalby]

Hello @pjonnlagadda ,

Yes exactly!

This is the V1 package com.amazonaws.auth.policy

Here is the V2 package software.amazon.awssdk.core.auth.policy

If you need example for a specific use case you can also submit a documentation request to the aws-docs team to ask for new documentation of a specific use case here under feature-request.

I hope these resources help!

Is there any way we can improve the documentation provided on the migration guide to facilitate migration from AWS Java SDK V1 to V2 on your end? We would love to have any feedback on your experience and what you would find helpful/valuable to support you through this process.

Sincerely,

Yasmine