Create Maven project, failed to resolve archetype, connection was rejected

Question

Create Maven project, failed to resolve archetype, connection was rejected

I suspect I have a problem with the Maven proxy. When I create a new project:

1) File -> New -> Maven Project

2) I choose the archetype : in org.apache.maven.archetypes → maven-archetype-webapp

3) And I get this error:

Failed to resolve archetype org.apache.maven.archetypes: maven-archetype-webapp: RELEASE from any of the configured repositories.
Creating maven-archetype-webapp 'ran into a problem. Failed to resolve archetype org.apache.maven.archetypes: maven-archetype-webap p: RELEASE from any of the configured repositories.

In detail:

Failed to resolve archetype org.apache.maven.archetypes: maven-archetype-webapp: RELE ASE from any of the configured repositories. Could not resolve artifact org.apache.maven.archetypes: maven-archetype-webapp: p om: RELEASE Could not resolve version for org.apache.maven.archetypes: maven-archetype-webapp: pom: RELEASE: Could not find org metadata .apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvreVm2 \ repository) Unable to solve version for org.apache.maven.archetypes: maven-archetype-webapp: pom : RELEASE: Could not find metadata org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvreVm2 \ repository)

And in the .log file:

ENTRY org.eclipse.m2e.logback.appender 2 0 2015-05-18 09: 30: 10.373 MESSAGE Error transferring org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml from repo.maven.apache .org / maven2 has been cached in the local repository, permission will not be reloaded until the update interval of the central expiration or update is forced. Original error: failed to transfer metadata to org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml from / to central (repo.maven.apache.org/maven2): connection rejected: connect
ENTRY org.eclipse.m2e.logback.appender 2 0 2015-05-18 09: 30: 13.259 MESSAGE Error transferring org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml from repo.maven.apache .org / maven2 has been cached in the local repository, permission will not be reloaded until the update interval of the central expiration or update is forced. Original error: failed to transfer metadata to org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml from / to central (repo.maven.apache.org/maven2): connection rejected: connect
ENTRY org.eclipse.m2e.core 4 -1 2015-05-18 09: 30: 13.329 MESSAGE Failed to resolve archetype org.apache.maven.archetypes: maven-archetype-webapp: RELEASE from any of the configured repositories. STACK 1 org.eclipse.core.runtime.CoreException: failed to resolve the org.apache.maven.archetypes artifact: maven-archetype-webapp: pom: RELEASE on org.eclipse.m2e.core.internal.embedder.MavenImpl $ 5.call (MavenImpl.java:769) at org.eclipse.m2e.core.internal.embedder.MavenImpl $ 5.call (MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext. java: 166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:109) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.ava on org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java:736) on org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java:713) on org.eclipse .m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype (ProjectConfigurationManager.java:829) on org.eclipse.m2e.core .internal.project.ProjectConfigurationManager.createArchetypeProjects0 (ProjectConfigurationManager.java:743) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager $ 5.call (ProjectConfigurationManager.java:719) at.m.ecl. project.ProjectConfigurationManager $ 5.call (ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext.java:166) at org.eclipse.m2e.corederMonternal.ed .execute (MavenExecutionContext.java:142) on org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:96) on org.eclipse.m2e.core.internal.embedder.MavenImpl.execute (MaenExecutionContext.java:96) .java: 1348) on org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects (ProjectConfigurationManager.java:717) on org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard $ 5.doCreateMaven ProjectWizard.java:244) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob $ 1.doCreateMavenProjects (AbstactCreateMavenProjectJob.java:46) at org.eclipse.m2e.core.ui.internal.wizrer ) : 38) on org.eclipse.core.internal.jobs.Worker.run (Worker.java:54) Contains: Could not resolve version for org.apache.maven.archetypes: maven-archetype-webapp: pom: RELEASE: Not managed to find metadata org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvre.m2 \ repository) org.eclipse.aether.resolution.VersionResolutionException: failed It was possible to resolve the version for org.apache.maven.archetypes: maven-archetype-webapp: pom: RELEASE: could not find the metadata org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvre.m2 \ repository) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion (DefaultVersionResolver.javahaps12) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve18 Default ) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:262) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifavaeces23esol internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:295) at org.eclipse.m2e.core.internal.embedder.MavenImpl $ 5.call (MavenImpl.java:746) at org.eclipse.m2e.core.internal.embedder .MavenI mpl $ 5.call (MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext.java:166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContextexexex (MavenExecutionContext.java:109) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:96) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java : 736) on org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java:713) on org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype (ProjectConfigurationManager.java:829) org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0 (ProjectConfigurationManager.java:743) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager $ 5.call (ProjectConfigurationManager.j .m2e.core.internal.project.ProjectConfigurationManager $ 5.cal l (ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext.java:166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.extextuteexonuteexexute java: 142) on org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:96) on org.eclipse.m2e.core.internal.embedder.MavenImpl.execute (MavenImpl.java:1348) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects (ProjectConfigurationManager.java:717) at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard $ 5.doCreateMavenProjects (maveno org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob $ 1.doCreateMavenProjects (AbstactCreateMavenProjectJob.java:46) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectspejectrejectespejectrejectespejectrejectspejectrejectespejectrejects on the org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace (AbstactCreateMavenProjectJob.java:50) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run (InternalWorkspaceJob.ava.ava. core.internal.jobs.Worker.run (Worker.java:54) Called: org.eclipse.aether.transfer.MetadataNotFoundException: could not find metadata org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata. xml in local (D: \ Users \ dlefebvre.m2 \ repository) at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve (DefaultMetadataResolver.java:260) at org.eclipse.aether.internal.impl.DefaultMetadataResolveololol (DefaultMetadataResolver.java:218) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion (DefaultVersionResolver.java:250) ... 26 more SUBENTRY 1 org.eclipse.m2e.core 4 -1 2015-05-18 09: 30: 13.334 MESSAGE Failed allow artifact org.apache.maven.archetypes: maven-archetype-webapp: pom: RELEASE SUBENTRY 2 org.eclipse.m2e.core 4 -1 2015-05-18 09: 30: 13.334 MESSAGE Could not solve the version for org.apache .maven.archetypes: maven-archetype-webapp: pom: RELEASE: Could not find the metadata org.apache.maven.archetypes: maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvre.m2 \ storage)! STACK 0 org.eclipse.aether.resolution.VersionResolutionException: could not resolve version for org.apache.maven.archetypes: maven-archetype-webapp: pom: RELEASE: could not find metadata org.apache.maven.archetypes: maven-archetype -webapp / maven-metadata.xml in local (D: \ Users \ dlefebvre.m2 \ repository) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion (DefaultVersionResolver.javahaps12) at org.eclipse.aether. internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java{ DefaultArtifactResolver.java:239) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:295) at org.eclipse.m2e.core.internal.embedder.MavenImpl $ 5.cal l (MavenImpl.java:746) at org.eclipse.m2e.core.internal.embedder.MavenImpl $ 5.call (MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext .java: 166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:109) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecavaContext. ) on org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java:736) on org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve (MavenImpl.java:713) in org. eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype (ProjectConfigurationManager.java:829) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0 (ProjectConjava.m2ec2 configuration core.internal.project.ProjectConfigurationManager $ 5.call (ProjectConfigurationManager.java:719) a t org.eclipse.m2e.core.internal.project.ProjectConfigurationManager $ 5.call (ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare (MavenExecutionContext.java:166) eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:142) on org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute (MavenExecutionContext.java:96) on org.ecl. core.internal.embedder.MavenImpl.execute (MavenImpl.java:1348) on org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects (ProjectConfigurationManager.java:717) on org.eclipse.m2ecore.ui internal.wizards.MavenProjectWizard $ 5.doCreateMavenProjects (MavenProjectWizard.java:244) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob $ 1.doCreateMavenProjectl.j.jec. ui.internal.wizards.AbstractCreateMavenPro jectsOperation.run (AbstractCreateMavenProjectsOperation.java:62) on org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace (AbstactCreateMavenProjectJob.java:50) on org.eclipseource.core.core.core. InternalWorkspaceJob.java:38) on org.eclipse.core.internal.jobs.Worker.run (Worker.java:54) Called: org.eclipse.aether.transfer.MetadataNotFoundException: could not find metadata org.apache.maven.archetypes : maven-archetype-webapp / maven-metadata.xml in local (D: \ Users \ dlefebvre.m2 \ repository) on org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve (DefaultMetadataResolver.java:260) at org. eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata (DefaultMetadataResolver.java:218) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion (DefaultVersionResolver.java:250)

We can see the origin of the problem: Connection rejected: connect

I already did this:

1) Window → Settings → General → Network Connections . I introduced the Guide with the url and port of my proxy for HTTP . It works because the Spring Tool Suite did not want to update before. After that, everything is in order.

2) Window → Settings → Maven → User Settings . The Global Settings is empty. In user settings, I put the path in settings.xml . In this file I have:

<settings> <proxies> <proxy> <active>true</active> <protocol>http</protocol> <host>my.proxy.fr</host> <port>3128</port> </proxy> </proxies> </settings>

In this Section: Create a Maven Project in Eclipse Complains “Cannot resolve archetype” The problem was resolved with the addition of the remote directory http://repo1.maven.org/maven2/archetype-catalog.xml . For me, he said that the directory is empty.

My configuration: Windows 7 Pro 64-bit, Spring toolkit 3.6.4.RELEASE based on Eclipse Luna SR1 (4.4.2), Java version 8 Update 45, No authenticated proxy

Why can't I create a new Maven project?

+8

java spring eclipse maven proxy

Damienl May 18, '15 at 8:03

source share

6 answers

Abdelo · Answer 1 · 2016-11-16T18:48:25+0000

I had the same problem, I think that at a certain time you tried to create this maven application without a connection like me, and what causes this problem. Since the first time Maven creates an empty directory, try downloading everything you need to create a project. After creating any project, maven Maven continues to search only in this directory without downloading things from the Internet. I believe that the easiest way to solve this problem is to close Eclipse (or sts) and delete the .m2 directory located in (in my case) "c: /Users/myname/.m2". and then reopen the IDE you used. Good luck.

eGhoul · Answer 2 · 2015-11-22T02:01:13+0000

I had the same problem. I fixed it by adding the maven archetype directory for the eclipse. The steps are below:

Open window
Open Maven Settings
Archetypes Click Add Remote
Directory "and add the following:

Catalog file: http://repo1.maven.org/maven2/archetype-catalog.xml
Description: maven directory

Maque bermans · Answer 3 · 2017-05-31T19:59:46+0000

I also had the same problem, I solved it by deleting .m2 in c:/user/{user_name}/.m2

Hope this helps.

Srikanthkumar · Answer 4 · 2017-10-16T10:20:58+0000

Restart eclipse after changing proxy settings in c: / user / {user_name} /. m2

Siva · Answer 5 · 2018-12-07T06:51:51+0000

Failed to resolve the archetype org.apache.maven.archetypes: maven-archetype-quickstart: 1.1 from any of the configured repositories

Sidharth · Answer 6 · 2019-05-23T17:06:00+0000

It seems that Maven is trying to find a jar for a relative web application (or quick launch, in some cases), and when he cannot find it, he throws this error. According to the available documentation, Maven should install all the necessary files / banks automatically, but for some reason this is not possible in some cases.

I downloaded "maven-archetype-webapp-1.0.jar" from here and put it in the following folder in the .m2 folder, and it worked:

 <Your path up until .m2>\.m2\repository\org\apache\maven\archetypes\maven.archetype.webapp

Create Maven project, failed to resolve archetype, connection was rejected

More articles: