codehaus.org Repositories Should Be Removed From Your Nexus Instance

Any Maven 2 proxy repository with a remote URL that includes the domain name codehaus.org should be removed from your Nexus instance.

Why?

codehaus.org has been effectively shut down as an artifact repository.

While the domain name remained active for some time, proxying any artifacts from that domain since the repository was shut down has become no longer valid.

Any proxy repository which references codehaus.org should be deleted or disabled.

As of Nexus Repository Manager 2.12, we no longer ship with a proxy repository to codehaus.org.

Example (may be incomplete ) remote URLS which are no longer valid include:

http://repository.codehaus.org
http://snapshots.repository.codehaus.org
http://nexus.codehaus.org
http://fisheye.codehaus.org

Recommended Actions in Priority Order

If the Auto Blocking feature is enabled Nexus may have automatically blocked your codehaus proxy, however this is not adequate protection. At a minimum, manually block the repository before deleting it. For each repository, edit the Configuration. Change Automatically Block to False. Save. Immediately right-click the repository in the repositories list and choose Block proxy. This manually blocks the proxy and now Nexus will no longer keep trying to unblock these invalid repositories.

Next remove the codehaus proxy repositories from any Repository Groups.

Finally delete a Codehaus proxy repository in Nexus , use the Delete button while selecting each repository in the repositories list.

If your codehaus proxy repositories contain RELEASE artifacts that older internal builds may depend on, you should source these from some other place ( ie. Central). If you have a SNAPSHOT codehaus repository, we recommend deleting it as SNAPSHOTs will never be published at that domain again.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk