adobe / adobe/aem-project-archetype
AEM Archetype project created with version above 23 is including a common filter for '/apps/sling' which overrides the existing changes.
- Dominant language
- JavaScript
- Stars
- 596
- Forks
- 431
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
### Expected Behaviour
Any entry in a filter.xml should be specific to the project. Thus there must not be any generic entries such as "apps/sling"
### Actual Behaviour
A generic entry called "apps/sling" is being included
### Reproduce Scenario (including but not limited to)
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.
#### Steps to Reproduce
Create a maven archetype project with a version above 23.
Check the filter.xml and it has an entry "apps/sling"
#### Platform and Version
AEM
Archetype version 23 and above.
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-archetype-project-created-with-version-above-23-is-including/m-p/433068#M123427
#### Sample Code that illustrates the problem
#### Logs taken while reproducing problem
Contributor guide
Research direction
Locate the archetype template's filter.xml and inspect the entry for apps/sling. Regenerate a project with an archetype version above 23 and confirm that the generated filter.xml no longer contains this generic path; the issue does not mention a specific test file.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100