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?