Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM Archetype project created with version above 23 is including a common filter for '/apps/sling' which overrides the existing changes.

Avatar

Level 2

Archetype project created with version above 23 is including a common filter for '/apps/sling'. If an AEM instance already has a project which has customisations in 'apps/sling' folder, any new project with this common filter when deployed to the same instance is overriding the existing changes. 

The issue here is why does a common path like '/apps/sling' is being included in filter.xml. As every path present in filter.xml must be corresponding to the project folder. This is causing issues and every time when we create a new its necessary for us to delete this entry from filter.xml. 

 

Any alternative workaround suggested would be helpful.

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @abinayaSirius, I think that maybe good idea will be to raise this issue on github or contribute and make AEM Archetype better for everyone 

You can find contribution guide under https://github.com/adobe/aem-project-archetype/blob/develop/CONTRIBUTING.md it also contains instruction how to raise a bug.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @abinayaSirius, I think that maybe good idea will be to raise this issue on github or contribute and make AEM Archetype better for everyone 

You can find contribution guide under https://github.com/adobe/aem-project-archetype/blob/develop/CONTRIBUTING.md it also contains instruction how to raise a bug.

Avatar

Community Advisor

you can remove this from your project or use merge or update mode for this path in filter.xml

https://jackrabbit.apache.org/filevault/filter.html



Arun Patidar