adobe / adobe/aem-eclipse-developer-tools

Creating new AEM Project using Wizard requires Advanced settings

Ouverte
#140 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
Java
Étoiles
37
Forks
23
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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:
![Image](https://github.com/user-attachments/assets/0ff4c43f-eb7f-4236-a2fd-d5a25e384800)

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Reproduisez le problème depuis File/New/Project... en utilisant AEM/AEM Sample Multi-module project avec la version 54 de l’archetype, puis examinez comment les propriétés de l’assistant basic et Advanced sont initialisées et validées. Vérifiez les entrées du projet Maven généré et confirmez que c’est terminé lorsque les valeurs par défaut de groupId, artifactId, package et appId sont acceptées sans ouvrir les paramètres Advanced.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
java
Domaine
build-system, devtools
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.