Getting some unusual packages installed in CRX on a maven build | Community
Skip to main content
New Participant
December 12, 2023
Solved

Getting some unusual packages installed in CRX on a maven build

  • December 12, 2023
  • 5 replies
  • 1069 views

Getting some unusual packages installed in CRX on a maven build along with project packages, names as below -

pack_201a2be2-9883-45b2-a81e-88771db24a3e.zip

Last installed 15:24 | admin

 

Then the whole set of pages associated with the project and site structure went blank. The bundles are up and the /apps are installed.

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 Peter_Puzanovs

Hi Deepthi,

 

Assuming it's on your local box,

Check your project build and associated pom file to see how this package get's created, remove it if it's not needed.

 

Regards,

Peter

5 replies

kautuk_sahni
Employee
January 2, 2024

@deepthisa Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
arunpatidar
New Participant
December 13, 2023

Can you please check if you have watcher or webpack? Or you are using any utility which push content to aem on save?

Arun Patidar
Sudheer_Sundalam
New Participant
December 12, 2023

@deepthisa ,

Check the build log while you are building the code. Use "mvn -e -X clean install" command to see the debug level build logs. This should give you more insight into how/where the unknown package is getting built and deployed to AEM server.

 

Jagadeesh_Prakash
New Participant
December 12, 2023

@deepthisa  Can you check the filter and what all are getting installed. Seems this is not part of AEM installation and should be from your code.

Peter_Puzanovs
Peter_PuzanovsAccepted solution
New Participant
December 12, 2023

Hi Deepthi,

 

Assuming it's on your local box,

Check your project build and associated pom file to see how this package get's created, remove it if it's not needed.

 

Regards,

Peter