Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven skeleton generating failed #30

Open
HuKuTa94 opened this issue Jan 19, 2021 · 1 comment
Open

Maven skeleton generating failed #30

HuKuTa94 opened this issue Jan 19, 2021 · 1 comment

Comments

@HuKuTa94
Copy link

HuKuTa94 commented Jan 19, 2021

Hi. I repeat step by step instructions.
When I run
mvn archetype:generate
-DarchetypeRepository=local
-DarchetypeRepository=$HOME/.m2/repository
-DarchetypeGroupId=com.badlogic.gdx
-DarchetypeArtifactId=gdx-archetype
-DarchetypeVersion=1.2.0

I get an exception:
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2 org.apache.maven.wagon.TransferFailedException: Transfer failed for http://repo1.maven.org/maven2 501 HTTPS Required

Why it uses HTTP instead of HTTPS? I set up a profile in maven settings.xml like this:

id maven-https
activation
activeByDefault true
repositories
repository
id central
URL https://repo1.maven.org/maven2
snapshots
enabled false
pluginRepositories
pluginRepositor
id central
url https://repo1.maven.org/maven2
snapshots
enabled false

When maven asks me to choose a number:
Choose a number: 16:
What is it? I didn't found it in the readme. So next, I enter group and artefact id, version, package. It doesn't ask me to enter JavaGameClassName.

Then I get more errors. One of them:
[ERROR] Unable to add module to the current project as it is not of packaging type 'pom' org.apache.maven.archetype.old.ArchetypeTemplateProcessingException: Unable to add module to the current project as it is not of packaging type 'pom'

any help?
console_log.txt

@eduyayo
Copy link

eduyayo commented Feb 3, 2022

Those steps are missing one: create a dir and run the generate inside. The error is given because mvn is using the current pom.xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants