adobe / adobe/aem-project-archetype
Project with archetype 41 build failing with maven version less than 3.6.0
- Dominant language
- JavaScript
- Stars
- 596
- Forks
- 431
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
### Expected Behaviour
Project (archetype 41 ) creation and build (mvn clean install ) should go through successfully using maven version 3.3.9+ as per the documentation .
Archetype | AEM as a Cloud Service | AEM 6.5 | Java SE | Maven
-- | -- | -- | -- | --
41 | Continual | 6.5.7.0+ | 8, 11 | 3.3.9+
### Actual Behaviour
Project (archetype 41 ) creation is successfull but build (mvn clean install ) is failure with error while using maven version 3.5.3 which is greater than the version mentioned in [https://github.com/adobe/aem-project-archetype](documentation) .
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:install-node-and-npm (install node and npm) on project mysiteAdmin.ui.frontend: The plugin com.github.eirslett:frontend-maven-plugin:1.12.0 requires Maven version 3.6.0 -> [Help 1]
### Reproduce Scenario (including but not limited to)
With Maven version 3.5.3 , issue is reproducible
#### Steps to Reproduce
1. Create a project of archetype 41 --> **mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=41 -D appTitle="My SiteAdmin" -D appId="mysiteAdmin" -D groupId="com.mysiteAdmin**
2. after project creation is successfull , **cd mysiteAdmin**
3. **mvn clean install**
#### Platform and Version
Windows 10 , Command Prompt , Zulu JDK 11
#### Sample Code that illustrates the problem
NA
#### Logs taken while reproducing problem
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:install-node-and-npm (install node and npm) on project mysiteAdmin.ui.frontend: The plugin com.github.eirslett:frontend-maven-plugin:1.12.0 requires Maven version 3.6.0 -> [Help 1]
Contributor guide
Research direction
Generate archetype 41 using the command in the issue, then run mvn clean install with Maven 3.5.3 and inspect the frontend-maven-plugin 1.12.0 failure. Compare the generated project’s Maven configuration with the documented Maven 3.3.9+ requirement; done means the supported-version guidance and build behavior agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100