apache / apache/maven-archetype
Support for multiple archetypes repositories
- Dominant language
- Java
- Stars
- 148
- Forks
- 181
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 8
Description
### New feature, improvement proposal
Given current settings.xml:
```xml
ibm
was-archetype
https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/maven/repository/
ibm
```
when run
```bash
mvn archetype:generate -Dfilter="com.ibm:"
```
the archetypes resolution respond with:
```
Choose archetype:
1: remote -> com.ibm.cics:cics-bundle-deploy-reactor-archetype (An archetype demonstrating how to use the cics-bundle-maven-plugin to build and deploy a CICS bundle using a build with a Maven reactor.)
2: remote -> com.ibm.cics:cics-bundle-reactor-archetype (An archetype demonstrating how to use the cics-bundle-maven-plugin to build a CICS bundle using a build with a Maven reactor.)
3: remote -> com.ibm.mfp:adapter-maven-archetype-http (IBM MFP Adapter archetype for JavaScript adapter as a maven project. BuildNumber is : 8.0.2024082809)
4: remote -> com.ibm.mfp:adapter-maven-archetype-java (IBM MFP Adapter archetype for Java adapter as a maven project. BuildNumber is : dummyBuildNumber)
5: remote -> com.ibm.mfp:adapter-maven-archetype-sql (IBM MFP Adapter archetype for sql adapter as a maven project. BuildNumber is : dummyBuildNumber)
6: remote -> com.ibm.sbt:sbt.sso.webapp-archetype (-)
Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): :
```
Not resolving the added repository ones.
When you use a repository with id "archetype", this works... but it stops searching in central. ¿Why is the archetypes search done in only one repository? In my opinion, at least an "id pattern" should be used instead of a static and single one.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the settings.xml example and the `mvn archetype:generate -Dfilter="com.ibm:"` command, then trace how archetype repositories are selected and why the static `archetype` repository id stops central from being searched. Done means configured repositories can be searched together, including central, without requiring every repository to use one id.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100