adobe / adobe/aem-project-archetype

What is the purpose of maven-assembly-plugin inside of ui.frontend?

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

Description

### Platform and Version
archetypeVersion=27

### Reproduce Scenario (including but not limited to)
Generate project from the latest adobe archetype e.g.:
`mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=27 -D aemVersion=6.5.7 -D appTitle='my app' -D appId=platform -D groupId=com.my.app -D includeExamples=n
`

### Actual Behaviour
The pom.xml file for ui.frontent module contains maven-assembly-plugin configuration. The plugin during maven build generates a zip package from the dist directory which doesn't really make sense as the dist folder is not even processed by aem-clientlib-generator yet.

### Expected Behaviour
What is the purpose of the package/maven-assembly-plugin ?

Contributor guide

Open the contributing guide

Research direction

Start with the ui.frontend module's pom.xml and inspect the maven-assembly-plugin configuration, then trace how the dist directory is handled relative to aem-clientlib-generator. Compare the generated package with the archetype build command; the investigation is complete when the plugin's purpose and whether its configuration is still needed are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, javascript
Domain
build-system
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.