mvn archetype:generate only returning 2.X archetypes

Gatling (Open-Source)
1

I’m trying load 3.3.1 by archetype. I was wondering if anyone has seen this and what the solution is. I think the problem is in the main maven repository.

Thanks

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\maven\apache-maven-3.6.3-bin\apache-maven-3.6.3\bin…
Java version: 11.0.6, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-11.0.6
Default locale: en_US, platform encoding: Cp1252
OS name: “windows 10”, version: “10.0”, arch: “amd64”, family: “windows”

C:\MyGatlingProjects>mvn archetype:generate
[INFO] Scanning for projects…
[INFO]
[INFO] ------------------< org.apache.maven:standalone-pom >-------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.1.2:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.1.2:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO]
[INFO] — maven-archetype-plugin:3.1.2:generate (default-cli) @ standalone-pom —
[INFO] Generating project in Interactive mode
[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
Choose archetype:
1: remote → am.ik.archetype:maven-reactjs-blank-archetype (Blank Project for React.js)
2: remote → am.ik.archetype:msgpack-rpc-jersey-blank-archetype (Blank Project for Spring Boot + Jersey)
3: remote → am.ik.archetype:mvc-1.0-blank-archetype (MVC 1.0 Blank Project)
. . . .

2080: remote → us.fatehi:schemacrawler-archetype-plugin-lint (-)
2081: remote → xyz.luan.generator:xyz-generator (-)
Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): 1129: gatling
Choose archetype:
1: remote → io.gatling.highcharts:gatling-highcharts-maven-archetype (gatling-highcharts-maven-archetype)

Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 1
Choose io.gatling.highcharts:gatling-highcharts-maven-archetype version:
1: 2.0.0-RC1
2: 2.0.0-RC2
3: 2.0.0-RC3
4: 2.0.0-RC4
5: 2.0.0-RC5
6: 2.0.0-RC6
7: 2.0.0
8: 2.1.0
9: 2.1.1
10: 2.1.2
11: 2.1.5
12: 2.1.6
13: 2.1.7
14: 2.2.0-M2
15: 2.2.0
16: 2.2.1
17: 2.2.4
18: 2.2.5
19: 2.3.0
Choose a number: 19:

Intelij reports the following when trying to create a project by archetype

[INFO] Scanning for projects…
[INFO]
[INFO] ------------------< org.apache.maven:standalone-pom >-------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.1.2:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.1.2:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO]
[INFO] — maven-archetype-plugin:3.1.2:generate (default-cli) @ standalone-pom —
[INFO] Generating project in Batch mode
[INFO] Archetype repository not defined. Using the one from [io.gatling.highcharts:gatling-highcharts-maven-archetype:2.3.0] found in catalog remote

Thanks

2

The problem is on your side, your local catalog is not up to date.

https://maven.apache.org/archetype/maven-archetype-plugin/specification/archetype-catalog.html

3

Thanks Stephane. I ran the following and it updated the catalog.
mvn archetype:crawl

4

More info on this issue. A co-worker was having the same issue. I found we had to:

download gatling-highcharts-maven-archetype-3.3.1.jar from the maven repository.

Then install the archetype by
mvn install:install-file -Dfile=“c:\MyGatlingProjects\gatling-highcharts-maven-archetype-3.3.1.jar” -DgroupId=io.gatling.highcharts -DartifactId=gatling-highcharts-maven-archetype -Dversion=3.3.1 -Dpackaging=jar

then run mvn -archetype:crawl
then run mvn -archetype:generate

once complete we could then see the 3.3.1 archetype in the list of 2.X versions.

5

Do you run in a corporate network where you are forced to use the internal maven proxy?

6

Yes. Project pom files only point to the internal mvn repository.

7

So exactly my point. Your config forces maven to use your internal repository as a mirror of everything, including maven central.
And your internal repository contains an archetype catalog that seriously lags behind.