adobe / adobe/aem-eclipse-developer-tools
Creating new AEM Project using Wizard requires Advanced settings
- Vorherrschende Sprache
- Java
- Sterne
- 37
- Forks
- 23
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
It appears that during the creation of the new AEM Project, some of the project template variables are not being set. This causes the user to have to open up the Advanced tab and fill in the variables manually.
Steps to Reproduce (see screencap below):
1. In Eclipse 2025-09, select `File/New/Project...`
2. In the New Project dialog, select `AEM/AEM Sample Multi-module project` and hit `Next`
3. Leave the location at default and leave the Archetype at the default (archetype version 54), and hit `Next`
4. Change the name to `sample` and an error appears `group Id must be specified` even though a default group id is visible
5. Enter a `Group Id` (for example `com.github.rmcdouga` and an error appears `artifact Id must be specified` even though a default artifact id is visible
6. Enter an `Artifact Id` (for example `sample-app`) and an error appears `package must be specified`. In order to set the package, the user must expand the `Advanced` properties.
7. Enter the a `Package` value and an error appears `appId must be specified`. Enter the appId and the wizard can be move to the next screen.
Expected Behaviour:
1. Reasonable defaults should be able to be derived for all the advanced properties from the basic properties. Any mandatory advanced properties that don't have reasonable defaults or can't be derived from the basic properties should be promoted into the basic properties section. I feel a user shouldn't be required to expand the Advanced properties unless they wish to customize the generated maven project beyond the defaults.
2. Arguably, the basic properties should accept the pre-populated values or something should indicate that those prepopulated values can't be used directly (maybe make the values italisized or semi-transparent to indicate that they are not "real"). This is a minor point and doesn't prevent the wizard from being used.
Here is a screencap of the process:

Beitragsleitfaden
Rechercherichtung
Reproduziere das Problem über File/New/Project... mit AEM/AEM Sample Multi-module project unter Verwendung der Archetypversion 54 und untersuche anschließend, wie die Eigenschaften des einfachen und des Advanced-Wizards initialisiert und validiert werden. Überprüfe die Eingaben des generierten Maven-Projekts und bestätige die Erledigung, wenn die standardmäßigen groupId, artifactId, package und appId akzeptiert werden, ohne die Advanced-Einstellungen zu öffnen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- build-system, devtools
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100