com.amazonaws.auth package from different aws-java-xxx projects is causing problems when used in felix OSGI container. about aws-sdk-java HOT 4 CLOSED

The com.amazonaws.auth packages were created that way for the IAM Policy Builder, each service module contains its own policy actions. There's no plans to change the package names ahead of the upcoming v1 Maintenance Mode.
I don't have specific recommendations for a workaround in this case, sorry :/

I'll say that even though OSGi is not supported in Java SDK v2 either (tracking here), the IAM Policy actions were implemented differently so there should not be split packages in v2. If you can give v2 a try, please add your findings to that tracking issue.

from aws-sdk-java.

You are correct, Java SDK v1 doesn't support OSGi. A feature request was submitted in the past but it wasn't prioritized, and we don't have plans to support in V1.

from aws-sdk-java.

@debora-ito Thanks for the response. We can OSGI-fy ourselves but the problem is having same package name com.amazonaws.auth different jars files. Even standard JAVA coding practice discourages this but will not have problem as long as class names are different but in OSGI it does not work even if class names are different.

Any plans to change and have jar specific package names? If not, I have to tinker with aws jars to merge all jars as one jar and use. Do you recommend that?

from aws-sdk-java.

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from aws-sdk-java.