-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
I'm trying to reload this maven project using default maven settings, but it doesn't work with the message
[WARNING] commons-io:commons-io/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata commons-io:commons-io/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
[WARNING] org.apache.logging.log4j:log4j-api/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.logging.log4j:log4j-api/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
[WARNING] org.apache.logging.log4j:log4j-core/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.logging.log4j:log4j-core/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
[WARNING] org.eclipse.core:org.eclipse.core.commands/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.core:org.eclipse.core.commands/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
[WARNING] org.hamcrest:hamcrest-all/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.hamcrest:hamcrest-all/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
[WARNING] org.junit.jupiter:junit-jupiter/maven-metadata.xml failed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.junit.jupiter:junit-jupiter/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-eclipse-repo (http://maven-eclipse.github.io/maven, default, releases+snapshots)]
I think it might come from the repositories config in pom.xml:
<repositories>
<repository>
<id>maven-eclipse-repo</id>
<url>http://maven-eclipse.github.io/maven</url>
</repository>
<repository>
<id>545ch4</id>
<url>https://raw.githubusercontent.com/545ch4/maven-eclipse.github.io/master/maven</url>
</repository>
</repositories>the maven-eclipse-repo is http instead of http. What's the purpose of it anyway? I would delete it from the POM, nobody uses eclipse anymore...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels