Maven 1 has recently started to produce a lot of 301 errors (after attempting to download certain dependencies) when building a project with a clean local repository.
The reason for this is that the public Maven 1 repository is being moved to from Maven 1 doesn’t understand redirects and therefore reports a 301 HTTP error when attempting to download certain dependencies (such as commons-logging for example).
To fix this, you simply have to add to the list of remote repositories in


If you are building old releases with Maven 1 please update your list of repositories. We’ll include the new mirror in all new releases of our software.

Maven 1 repository changes