AEM Groovy Installation and configurion at AEMaaCS

Question

Currently we getting following error when we install the AEM Groovy Console package 17.x.x which compatiable with Cloud Service but local env its working Expect issue org.cid15.aem.groovy.console.job.consumer.GroovyConsoleScheduledJobConsumer component status is "satisfied"

content-package:1.0.0-SNAPSHOT: Failed to collect dependencies at org.cid15.aem.groovy.console:aem-groovy-console-all:zip:17.0.12: Failed to read artifact descriptor for org.cid15.aem.groovy.console:aem-groovy-console-all:zip:17.0.12: Failure to find org.cid15.aem.groovy.console:aem-groovy-console:pom:17.0.12 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced 
Steps followed 1) download the :aem-groovy-console-all:zip:17.0.0 Package 2) Deploy using cloud pipeline then deployement got failded

arunpatidar · Accepted Answer

Hi,You can install groovy throughhttps://github.com/valtech/aem-easy-content-upgrade  Example : https://github.com/arunpatidar02/aemaacs-aemlab/commit/3325b65bec062a549139156bc3584c743db67ff7  Installing groovy using https://github.com/CID15/aem-groovy-console in AEMaaCS does not work.

nitesh_kumar-1 · Answer

Hi @varaande ,

You should embed it into the container module (all) like below

<-- In the embed section --->

 <embedded>
      <groupId>org.cid15.aem.groovy.console</groupId>
      <artifactId>aem-groovy-console-all</artifactId>
      <type>zip</type>
      <target>/apps/aem-groovy-console-packages/content/install</target>
 </embedded>

<-- In the dependency section --> 
<!-- https://mvnrepository.com/artifact/org.cid15.aem.groovy.console/aem-groovy-console-all -->
<dependency>
     <groupId>org.cid15.aem.groovy.console</groupId>
     <artifactId>aem-groovy-console-all</artifactId>
      <version>${groovyconsole.version}</version>
      <type>zip</type>
</dependency>

Also, the version I only see available in the maven repo is 17.0.0, can you cross-check the version? (In your error I see version 17.0.12)

Make sure this path is covered in filter.xml.

Hope this helps!

Regards,

Nitesh

Sign up

Login with SSO

Login to the community

Login with SSO