79752961

Date: 2025-09-01 23:28:03
Score: 1
Natty:
Report link

The URL of the Maven repo uses HTTPS protocol, not HTTP. Run mvn help:effective-pom and inspect the result for definitions. They should be at least:

    <pluginRepositories>
      <pluginRepository>
        <releases>
          <updatePolicy>never</updatePolicy>
        </releases>
        <snapshots>
          <enabled>false</enabled>
        </snapshots>
        <id>central</id>
        <name>Central Repository</name>
        <url>https://repo.maven.apache.org/maven2</url>
      </pluginRepository>
    </pluginRepositories>

Consider mirroring of the default Central Maven repository (the last resort to look in) with a statement in your settings.xml like:

    <mirror>
      <id>public-local</id>
      <mirrorOf>central</mirrorOf>
      <name>Let the default Maven Central repository is resolved in the local Nexus' public repository</name>
      <url>http://localhost:8081/repository/maven-public/</url>
    </mirror>

From the log above I see that you use a local Archiva, so change the URL accordingly, but still Archiva does not find the needed plugins - maybe it is not defined as a proxy of Maven Central?

Reasons:
  • Long answer (-1):
  • Has code block (-0.5):
  • Ends in question mark (2):
  • Low reputation (0.5):
Posted by: Rusi Popov