You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Edward Kreutzer <el...@usfca.edu> on 2013/06/12 23:20:26 UTC
maven-metadata.xml Error
Currently, I am receiving errors indicating that there is a missing Maven plugin and when the auto-download begins, I also receive an error that the connection is refused. I know that connecting to external sources is prohibited at my company, so I have been manually downloading and installing the plugins required.
However, the maven-metadata.xml file can be found in the /apache/maven/plugins/ directory and the /codehaus/mojo/ directory. I cannot figure out why there is still an error when the maven-metadata.xml file is in both locations. Any insight would be very helpful.
Here is the text of the error:
[INFO] Scanning for projects...
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
[WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
[WARNING] Failure to transfer org.apache.maven.plugins/maven-metadata.xml from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
[WARNING] Failure to transfer org.codehaus.mojo/maven-metadata.xml from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:04.141s
[INFO] Finished at: Mon Jun 10 14:31:09 EDT 2013
[INFO] Final Memory: 5M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'exec' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/export/home/edward.kreutzer/.m2/repository), central (http://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
Thanks,
Ted
Re: maven-metadata.xml Error
Posted by Russell Gold <ru...@gold-family.us>.
If you look closely, you will see that your first error is:
> [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
Given your corporate policy, I suspect that you are behind a proxy server, which is forbidding the download. You say that you are getting around this by manually downloading and installing the plugins. How are you doing that? Are you making sure to install all of their dependencies and all of their dependencies?
I think you need to check on your corporate policy. Most companies who have that rule at least allow you to go through a proxy server. See http://maven.apache.org/guides/mini/guide-proxies.html for how to do this.
- Russ
On Jun 12, 2013, at 5:20 PM, Edward Kreutzer <el...@usfca.edu> wrote:
> Currently, I am receiving errors indicating that there is a missing Maven plugin and when the auto-download begins, I also receive an error that the connection is refused. I know that connecting to external sources is prohibited at my company, so I have been manually downloading and installing the plugins required.
>
> However, the maven-metadata.xml file can be found in the /apache/maven/plugins/ directory and the /codehaus/mojo/ directory. I cannot figure out why there is still an error when the maven-metadata.xml file is in both locations. Any insight would be very helpful.
>
> Here is the text of the error:
>
> [INFO] Scanning for projects...
> Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> Downloading: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
> [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
> [WARNING] Failure to transfer org.apache.maven.plugins/maven-metadata.xml from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
> [WARNING] Failure to transfer org.codehaus.mojo/maven-metadata.xml from http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:04.141s
> [INFO] Finished at: Mon Jun 10 14:31:09 EDT 2013
> [INFO] Final Memory: 5M/245M
> [INFO] ------------------------------------------------------------------------
> [ERROR] No plugin found for prefix 'exec' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/export/home/edward.kreutzer/.m2/repository), central (http://repo.maven.apache.org/maven2)] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
>
> Thanks,
>
> Ted
-----------------
Come read my webnovel, Take a Lemon <http://www.takealemon.com>,
and listen to the Misfile radio play <http://www.gold-family.us/audio/misfile.html>!