Yes i did that and in my note already mentioned that, 14:00:46,076 [main] [ERROR] Error resolving dependencies for project com.pacificlifeinsurancecompanydam:aem-pacificlifeinsurancecompanydam-project.all14:00:46,077 [main] [ERROR] Failed to collect dependencies at com.adobe.granite:com.adobe.granit...

Didnot find the solution yet for this

Because of mutable concept we can't create non OSGI to osgi bundle and deploy. We need to keep this as a part of codebase through embed dependency only.

We are not setting up datastore here. We are just adding the s3 connector ZIP as to resolve the dependency. It should be possible.

Yes we are using AWS SDK to use in our codebase to move AEM to S3 assets and JSON metadata. We are finding issue when adding the respective depdencies like,Maven Repository: com.adobe.granite » com.adobe.granite.oak.s3connector » 1.10.10 (mvnrepository.com... and https://mvnrepository.com/artifact/c...

Hi Team, Issue -1. Usage of org.apache.sling.api.resource.ResourceResolver as a field is not thread safe.2. Usage of javax.jcr.Session as a field is not thread safe.3. ResourceResolver, Session should be closed in finally block. Critical in SonarQube through CloudManager. What is the workaround for ...

Both the dependencies not working

We tried to add both depdencies like,Maven Repository: com.adobe.granite » com.adobe.granite.oak.s3connector » 1.10.10 (mvnrepository.com) and https://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk-osgi/1.12.13

AEM TO S3 Blocker Case -> AWS libraries for S3 connector configs not resolved in AEM as a cloud service instance Environment – AEM As a cloud service Issue – Dependency not resolved – We are using the AEM as a cloud service environment and we are finding issues in using the AWS SDK libraries using a...

Hi Team, AEM TO S3 Blocker UseCase -> AWS libraries for S3 connector configs not resolved in AEM as a cloud service instanceEnvironment – AEM As a cloud service Issue – Dependency not resolved – We are using the AEM as a cloud service environment and we are finding issues in using the AWS SDK librar...