Maven-Projekt erstellen, Archetyp konnte nicht aufgelöst werden, Verbindung verweigert

Question

Ich vermute, dass ich ein Maven-Proxy-Problem habe. Wenn ich ein neues Projekt zu erstellen:

1) Datei -> Neu -> Maven Projekt

2) wähle ich den Urbild: in org.apache.maven.archetypes ->Maven-Urbild-Webapp

3) Und ich bekomme diese Fehlermeldung:

Could not resolve archetype org.apache.maven.archetypes:maven-archetype-webapp:RELEASE from any of the configured repositories.

Creating maven-archetype-webapp' has encountered a problem. Could not resolve archetype org.apache.maven.archetypes:maven-archetype-webap p:RELEASE from any of the configured repositories.

Detail:

Und in .log Datei:

ENTRY org.eclipse.m2e.logback.appender 2 0 2015-05-18 09:30:10.373 !MESSAGE Failure to transfer org.apache.maven.archetypes:maven-archetype-webapp/maven-metadata.xml from repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.archetypes:maven-archetype-webapp/maven-metadata.xml from/to central (repo.maven.apache.org/maven2): Connection refused: connect

ENTRY org.eclipse.m2e.logback.appender 2 0 2015-05-18 09:30:13.259 !MESSAGE Failure to transfer org.apache.maven.archetypes:maven-archetype-webapp/maven-metadata.xml from repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.archetypes:maven-archetype-webapp/maven-metadata.xml from/to central (repo.maven.apache.org/maven2): Connection refused: connect

ENTRY org.eclipse.m2e.core 4 -1 2015-05-18 09:30:13.329 !MESSAGE Could not resolve archetype org.apache.maven.archetypes:maven-archetype-webapp:RELEASE from any of the configured repositories. !STACK 1 org.eclipse.core.runtime.CoreException: Could not resolve artifact org.apache.maven.archetypes:maven-archetype-webapp:pom:RELEASE at 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.java:96) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:736) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:713) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:829) at 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 org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.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:142) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) at 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(MavenProjectWizard.java:244) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: Failed to 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) org.eclipse.aether.resolution.VersionResolutionException: Failed to 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.java:312) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:318) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239) at org.eclipse.aether.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.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.java:96) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:736) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:713) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:829) at 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 org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.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:142) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) at 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(MavenProjectWizard.java:244) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: 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.DefaultMetadataResolver.resolveMetadata(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 Could not resolve 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 Failed to 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) !STACK 0 org.eclipse.aether.resolution.VersionResolutionException: Failed to 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.java:312) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:318) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239) at org.eclipse.aether.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.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.java:96) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:736) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:713) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:829) at 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 org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.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:142) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) at 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(MavenProjectWizard.java:244) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: 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.DefaultMetadataResolver.resolveMetadata(DefaultMetadataResolver.java:218) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion(DefaultVersionResolver.java:250) ... 26 more

wir den Ursprung des Problems sehen: Connection refused: connect

Ich habe dies bereits tun:

1) Fenster -> Einstellungen -> Allgemein -> Netzwerkverbindungen. Ich habe in Handbuch mit dem url und Port meiner Proxy für HTTP Protokoll. Es funktioniert, weil Spring Tool Suite zuvor nicht aktualisiert werden wollte. Danach ist es okay.

2) Fenster -> Einstellungen -> Maven -> Benutzereinstellungen. In Globale Einstellungen, ist leer. In Benutzereinstellungen, legte ich den Pfad zu settings.xml. In dieser Datei, ich habe:

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

in diesem Thema: Create a Maven project in Eclipse complains "Could not resolve archetype" Das Problem mit dem Hinzufügen des Fern Kataloges http://repo1.maven.org/maven2/archetype-catalog.xml gelöst wurde. Für mich hieß es, dass der Katalog leer ist.

Meine Konfiguration: Windows 7 Pro 64 Bit, Frühlings- und Tool-Suite 3.6.4.RELEASE auf Basis von Eclipse Luna SR1 (4.4.2), Java-Version 8 45-Update, keine authentifizierten Proxy

Warum kann Ich erstelle ein neues Maven-Projekt?

Answer 1

Ich hatte das gleiche Problem. Ich habe es behoben, indem ich den Maven Archetype-Katalog zu Eclipse hinzugefügt habe.Die Schritte sind unten angegeben:

1. Open Window
2. Einstellungen öffnen Maven
3. Urbilder Klicken Sie auf 'Add Remote
4. Katalog' und fügen Sie folgendes:

Catalog File: http://repo1.maven.org/maven2/archetype-catalog.xml

Description: maven catalog

Answer 2

Ich hatte das gleiche Problem, ich denke in einer bestimmten Zeit hast du versucht, diese Maven App ohne Verbindung wie ich zu erstellen und das, was dieses Problem verursacht. Weil Maven zum ersten Mal ein leeres Verzeichnis erstellt, versuchen Sie, alles herunterzuladen, was zum Erstellen des Projekts nötig ist. Nach jedem Maven-Projekt, das Sie erstellen, sucht Maven einfach in diesem Verzeichnis nach, ohne etwas aus dem Internet herunterzuladen. Ich glaube, der einfachste Weg, um dieses Problem zu lösen, ist, Eclipse (oder sts) zu schließen und das Verzeichnis .m2 in (in meinem Fall) "c: /Users/myname/.m2" zu löschen. und dann öffne die IDE, die du benutzt hast. Viel Glück

Answer 3

ich hatte auch das gleiche Problem, ich beschlossen, es von .m2 in c:/user/{user_name}/.m2

löschen Ich hoffe, es kann helfen.

Answer 4

Eclipse Neustart nach Proxy-Einstellungen in c Ändern:./User/{user_name}/m2