This can usually be fixed by running rebuild metadata on the affected artifact. If the version referenced by the maven-metadata.xml is not there you will get a 404. SNAPSHOT look-ups, or version ranges, or unversioned dependencies (typically plugins) will trigger metadata look-up. Note: Usually the end user is unaware that IT has changed the firewall, so it may not be obvious this could be the real problem. User can work around by increasing the HTTP read timeouts in Nexus (either globally or per proxy repository). Most likely cause is a firewall which has virus scanning turned on. There is a repository route defined which is preventing access to the GAV from the group repository.The hosted/proxy repository is not in the group repository.Note that group repositories do not have an NFC cache, only repositories contained in groups. To clear the cache, have the user right click on the repository and run 'expire cache'. User has manually restored artifacts into a hosted repository (retrieved them from Nexus trash, for instance).The repository is a proxy, and an attempt was made to retrieve the artifact before it was available on the remote.Typical reasons for artifacts to be in NFC: Nexus caches items which are not found in a repository for a period of time specified in the repository's configuration. NFC ( Not found Cache )Īrtifacts may be in the NFC (not found cache). There are a number of things which can cause this. Sometimes you'll receive 404 responses when trying to retrieve artifacts from a repository, but you know the artifact is present in the server.

Download sonatype nexus