Mvn error updating group repository metadata

Sometimes you'll receive 404 responses when trying to retrieve artifacts from a repository, but you know the artifact is present in the server. User can work around by increasing the HTTP read timeouts in Nexus (either globally or per proxy repository). Nexus caches items which are not found in a repository for a period of time specified in the repository's configuration. Typical reasons for artifacts to be in NFC: Most likely cause is a firewall which has virus scanning turned on.Version 1.2 is compatible with Nexus Repository Manager Pro 2.3, Version 1.4.4 is compatible with Nexus Repository Manager Pro 2.4, Version 1.4.8 is compatible with Nexus Repository Manager Pro 2.5 and 2.6.1.5 and 1.6.x can be used for Nexus Repository Manager Pro 2.7 to 2.10.DOCTYPE' - IGNORING [INFO] artifact org.apache.velocity:velocity: checking for updates from atlassian-contrib [INFO] artifact org.apache.velocity:velocity: checking for updates from central [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact.

It is recommended that all JBoss projects use Maven 3.One nice technique is to find the artifact in Nexus UI and paste the XML from the Artifact information panel into the This demonstrates a nice way to avoid this problem in the future.What additional privileges apart from the Nexus Deployment Role do I need to assign to my user to be able to update maven-metadata.xml?Thanks You also need to grant the user privileges to write artifacts into the target repository.

Leave a Reply