Packages not installing on publisher | Community
Skip to main content
stiegjo22
Level 4
December 18, 2023
Solved

Packages not installing on publisher

  • December 18, 2023
  • 1 reply
  • 1501 views

We're having a problem with packages not installing on our AEM publisher. (we deploy via TeamCIty) The only recent change we've made is adding the following change to some of the pom.xml to set up our project for Adobe Cloud Manager. (we haven't migrated yet)

 

 

<properties> <cloudManagerTarget>none</cloudManagerTarget> </properties>

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

Thanks Sudheer. I do have this defined in my all pom.xml file:

<properties> <cloudManagerTarget>all</cloudManagerTarget> </properties>

@stiegjo22 

 

We would also need to Embed the dependencies in all module. Just cloudManagerTarget would not suffice. Example:

<embeddeds> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd.ui.apps</artifactId> <type>zip</type> <target>/apps/wknd-packages/application/install</target> </embedded> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd.core</artifactId> <target>/apps/wknd-packages/application/install</target> </embedded> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd.ui.content</artifactId> <type>zip</type> <target>/apps/wknd-packages/content/install</target> </embedded> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd.ui.config</artifactId> <type>zip</type> <target>/apps/wknd-packages/application/install</target> </embedded> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd.ui.content.sample</artifactId> <type>zip</type> <target>/apps/wknd-packages/content/install</target> </embedded> <embedded> <groupId>com.adobe.aem.guides</groupId> <artifactId>aem-guides-wknd-shared.ui.content</artifactId> <type>zip</type> <target>/apps/wknd-vendor-packages/content/install</target> </embedded> </embeddeds>

 

 

 

So, all the packages would be embedded into all module and all would be deployed. The other modules which are part of all will then be picked by AEM and installed.

 

Sample pom.xml of all : https://github.com/adobe/aem-guides-wknd/blob/main/all/pom.xml

1 reply

arunpatidar
Community Advisor
Community Advisor
December 18, 2023

Hi @stiegjo22 
The property does exactly the same, what you are facing.

https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/getting-started/project-creation/project-setup.html#skipping-content-packages 

 

Cloud Manager will look for a property named cloudManagerTarget in the properties of built content packages. If this property is set to none, the package will be skipped and not deployed.

 

Arun Patidar
stiegjo22
stiegjo22Author
Level 4
December 18, 2023

Yes - I understand that it will skip in Cloud Manager if set to none. However we're still deploying to an on-premise instance of AEM and it's not installing on the publisher. Thanks.

Sudheer_Sundalam
Community Advisor
Community Advisor
December 18, 2023

@stiegjo22 ,

Based on the screenshot provided, I'm assuming you are using one of the latest archetypes. In your project, if you have 

"all" maven module, you need to set 

<cloudManagerTarget>all</cloudManagerTarget>

in the "all" maven module pom.xml file. 

Also, you need to have other maven modules like ui.apps, ui.config, and ui.content added in the embed section of filevault-package-maven-plugin configuration.

Both in Adobe CM & (I think on-premise), the <cloudManagerTarget>none</cloudManagerTarget> is set to none to avoid individual packages getting installed on their own. By installing "all" package, other embed packages are automatically installed.