Getting error on this one as well!

adobe-public profile didn't work

I have read this one but when following it I am getting the below-mentioned error![INFO] Scanning for projects...[WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.5: Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could...

Hi All, I know Asset share commons is outside the scope of the AEM is open source.However, for upgrading the Asset share commons to cloud we are facing issues. in ui.apps we have the below dependency - <dependency> <groupId>com.adobe.aem.commons</groupId> <artifactId>assetshare</artifactId> ...

I run the utility with the following results - No Maven projects were created, No workflow launchers were disabled, No workflow runner configurations were created, No workflow models were modified and No processing profiles were created.# Migration IssuesThese issues were encountered while migrating...

hi all, we have a restriction wherein we cannot run the aem workflow migration tool due to security constraints for aio npm plugins.Reffered Asset Workflow Migration Tool | Adobe Experience Manager What is the alternate way to do so? BPA has flagged issues related to the workflow launchers being ena...

okay, the bpa report lists the below path for non-compatible changes - /apps/dam/gui/content/assetdetails/jcr:content/actions/viewproperties/granite:rendercondition If we navigate to the current path and check it against libs then there is no difference - /apps - /libs -   

how do you move AMS repo to the git repo for cloud?

hey @Shashi_Mulugu, its local cloud sdk - i will update the question to clarify that - thanks

hey guys, I recently started working on a migration project wherein the codebase is already having a skeleton cloud compatible repo.They ran the BPA report on AMS Production and then manually did a lift-and-shift from AMS repo to Cloud compatible repo. The expectation is to resolve the issues highli...