adobe / adobe/aem-project-archetype

Update Archetype 24 to Support Eclipse

Open
#577 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
596
Forks
431
Avg merge
10d 6h
Merged PRs (30d)
1

Description

Customer is currently stuck using Archetype 20 but is running into issues with JSP support and is unable to upgrade to archetype 21,22,23 due to a previous FileNotFound Issue (https://github.com/adobe/aem-project-archetype/issues/358). The solution was to upgrade to Archetype 24 but are unable to do so since Eclipse is not supported. Looking to find out the timeline for this support and push for the update of Archetype 24 to support the use case.

[Ticket](https://adobe-ent.crm.dynamics.com/main.aspx?appid=aeb537da-9595-ea11-a811-000d3a303484&forceUCI=1&pagetype=entityrecord&etn=incident&id=3c271ec0-1634-eb11-a813-00224809820c&recordSetQueryKey=incident-9fa71d15-2d9f-ea11-a812-000d3a3038a2%253A%2520entityimage_url%253A%2520%253A%2520%253A%2520%253A%2520%253A%2520false%253A%2520%253A%2520%253A%252050)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Archetype 24 project and the previous FileNotFound issue #358 to understand the Eclipse compatibility gap. The issue names no files or tests, so first identify where Archetype 24 defines or limits Eclipse support. Done means the reported Eclipse use case works with Archetype 24 and is covered by appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.