since ‎19-03-2018
‎10-12-2019
tonycarreira
Level 1
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Ok, I finally managed to get it to work! It was based on Macdonalds original advice.For all reading this, ignore the aws-java-sdk-osgi bundle because it has a lot of dependency faults and version issues. You will end up driving yourself mad chasing dependencies. For anyone wanting to incorporate AWS related stuff DO NOT follow the AWS tutorial here Using the SDK with Apache Maven - AWS SDK for Java it will tell you to either install the "bom" package or the one that pulls all the dependencies so...

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thanks Peter!That's the dependency I am using as well in the Core POM.I tried it before but when I install that dependency on OSGI though I get these errors:

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Mate the bundles are already there... I don't have to install them again. I can find them through the depfinderProblem is they cannot be resolved... Same happens to the AWS packages. I followed Macdonalds advice and created a bundle that exports them, but for some reason they are not picked up.

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
What do you mean by OSGified bundles?

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thanks Macdonald. I have done that and now I can see the dependency in the depfinder:The problem is my project still can't find those dependencies:My POM currently looks like this: org.apache.felix maven-scr-plugin org.apache.felix maven-bundle-plugin true If I add the following to the POM instructions in the POM org.apache.felix maven-scr-plugin org.apache.felix maven-bundle-plugin true aws-java-sdk-osgi,*;scope=compile com.amazonaws.*,* I get even more errors... Does this mea...

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thank you Macdonald! How do I do that with my Core bundle?Thanks

Views

2.0K

Likes

0

Replies

0
Re: AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thank you so much for the prompt answer. Unfortunately it did not work. My Core Pom is as follows: 4.0.0 com.company CC-aem ${companyCurrent} ../pom.xml CC-aem.core bundle Comapny CMS (AEM6) - Core Core bundle for Company CMS (AEM6) org.apache.felix maven-scr-plugin org.apache.felix maven-bundle-plugin true artifactId1, artifactId2;inline=true --> autoInstallBundle false org.apache.sling maven-sling-plugin /apps/company/install/ true com.amazonaws aws-java-sdk-cloudfront org.apache.felix org.apache.f...

Views

2.0K

Likes

0

Replies

0
AWS package cannot be resolved by Felix Console
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Hi guys,I am using the most recent maven archtype and therefore have the following folder structure:Project Name-Core-it.launcher-it.tests-it.apps-ui.contentI am importing an AWS dependency on my Master POM and Core POMMaster POM software.amazon.awssdk bom 2.5.25 pom import com.amazonaws aws-java-sdk-cloudfront 1.11.534 Core POM com.amazonaws aws-java-sdk-cloudfront The class using the AWS functionality is a custom workflow step that I have put inside the Core folder. However, when I depl...

Views

4.7K

Likes

0

Replies

16
Re: Logging for AEM 6.0
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
This here worked mate!! Thanks! I used my own workflow class to track! Thanks

Views

4.1K

Likes

0

Replies

1
Re: Logging for AEM 6.0
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thanks mate. I have actually done that before but it didn't work. I had it pointing to error.log but now I changed it to workflows.log. But still my workflow class is not outputting

Views

4.1K

Likes

0

Replies

0
Logging for AEM 6.0
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Hi all,I started writing a custom step workflow to clear the apache cache. I have a few questions as I am finding really hard to find good documentation about it.1 - Where can I see the logs for the workflow? I tried adding configuration to the Apache Sling Logging Logger Configuration but nothing is coming out in the logs (It's set to debug) I am looking at error.log btw.2 - Where can I find development based examples for custom workflows? I am working with AEM 6.0 but even 6.4 would be helpful...

Views

4.4K

Likes

0

Replies

5
Re: Upgrading from 6.0 to 6.4.x
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Hi Jorg,Again, thank you so much for the support. The complete command that I am running is:java -jar crx2oak-*.jar \/aem_environments/aem60/crx-quickstart/repository/ \/aem_environments/aem60/crx-quickstart/repository/datastore \How do I configure a datastore? I just want to move the content to 6.4 from 6.0

Views

387

Likes

0

Replies

0
Re: Upgrading from 6.0 to 6.4.x
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thanks so much for responding Jorg. I understand that but unfortunately my problem lies with the "Migrate the repository part".I've followed the instructions here Using the CRX2Oak Migration Tool but the information is very limited. I've set the env variables to export SLING_HOME="/usr/aem602/crx-quickstart".(I have AEM6.0 shutdown and sling_home is pointing to AEM6.0 crx-quickstart)Problem is when I run: Java -jar crx2oak-*.jar I get the error below. I don't want an s3datastore or any of the so...

Views

402

Likes

0

Replies

0
Re: Upgrading from 6.0 to 6.4.x
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
Thank you so much for the answers Jorg!Do you run the crx2oak directly on the crx of the 6.4? For instance, deploy all our 6.0 stuff on 6.4 and then run the tool against the 6.4 crx?

Views

407

Likes

0

Replies

0
Upgrading from 6.0 to 6.4.x
Avatar

tonycarreira

tonycarreira
- Adobe Experience Manager
We are aiming to perform a big migration from 6.0 to 6.4.x (where x=1 or 2). In the adobe documentation I can see that a recommended step is to perform a "Pattern Detector" to help with the migration, however the pattern detector is only supported from 6.1 onwards.1) Should we migrate first from AEM 6.0 to 6.1 run the pattern detector and then move from 6.1 to 6.4. Or do you advise moving from 6.0 directly to 6.4.2) The documentation also says that crx2oak tool should be run from 5.6.1 to 6.x .S...

Views

842

Likes

0

Replies

7