adobe / adobe/aem-eclipse-developer-tools

AEM content sync root directory keeps getting reset after Maven -> Update Project

Open
#93 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
37
Forks
23
PR merge metrics
No merged PRs in 30d

Description

### Expected Behavior

In Eclipse, for the ui.apps project, importing an Archetype 24 maven project should result in an AEM content sync root directory of "src/main/content/jcr_root", but instead sets the content sync root to "src/main/resources".

If you update the content sync root to "src/main/content/jcr_root" and later run Maven -> Update Project, that action resets the content sync root directory back to "src/main/resources".

### Actual Behavior

Importing an Archetype 24 project initially sets the AEM Content sync root directory to "src/main/resources", and it gets reset to "src/main/resources" every time that Maven -> Update Project is run.

#### Steps to Reproduce

- Install latest Eclipse (currently version 2020-09).
- Install latest AEM Developer Tools for Eclipse (currently version 1.3.0).
- Create new archetype 24 maven project.
- Import project into Eclipse.
- Right click on ui.apps project and select Properties.
- In dialog, click on "AEM" section.
- See that content sync root directory is "src/main/resources".
- Change content sync root directory to "src/main/content/jcr_root"
- Right click on ui.apps project and select Maven -> Update Project.
- Click OK in dialog.
- Update runs.
- Right click on ui.apps project and select Properties again.
- In dialog, click on "AEM" section.
- See that content sync root directory has been reset to "src/main/resources".

#### Platform and Version

Archetype 24, Eclipse 2020-09

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the listed Eclipse 2020-09, AEM Developer Tools 1.3.0, and Archetype 24 setup, then inspect how the ui.apps AEM content sync root is handled during Maven - Update Project. Done means importing the project and updating it preserves "src/main/content/jcr_root" instead of resetting it to "src/main/resources".

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.