使用eclipse创建maven项目出现的一个问题

错误信息

This error occurs when you employ a plugin that Maven could not download. Possible causes for this error are:

You are referring to a non-existing plugin, e.g. by means of a typo in its group id, artifact id or version.
You are using a third-party Maven plugin that is not deployed to the central Maven repository and your POM/settings is missing the required  to download the plugin. Note that  declarations are not considered when looking for the plugin and its dependencies, only  are searched for plugins.
The plugin repository you have configured requires authentication and Maven failed to provide the correct credentials to the server. In this case, make sure your ${user.home}/.m2/settings.xml contains a  declaration whose  matches the  of the plugin repository to use. See the Maven Settings Reference for more details.
There is a general network problem that prevents Maven from accessing any remote repository, e.g. a missing proxy configuration.
Maven failed to save the files to your local repository, see LocalRepositoryNotAccessibleException for more details.
The plugin repository you have configured is disabled for the specific version of the plugin you requested. For instance, if you want to use a SNAPSHOT version of a plugin, make sure you don't have false configured. Likewise, in order to resolve a released version of the plugin, the plugin repository should not be configured with false. See the POM Reference for more information on repository configuration.
In those cases, check your POM and/or settings for the proper contents. If you configured the plugin repository in a profile of your settings.xml, also verify that this profile gets actually activated, e.g. via invoking mvn help:active-profiles.

In case of a general network-related problem, you could also consult the following articles:

Configuring a Proxy
Security and Deployment Settings
Guide to Remote Repository Access through Authenticated HTTPS
Note: For performance reasons, Maven caches the information that the plugin could not be downloaded. Depending on your setup, you might need to clear this cache by adding the flag -U to the command line for your corrections to take effect.

原因分析

根据提示,查找该错误的官方分析链接
当您使用Maven无法下载的插件时，会发生此错误。这个错误的可能原因是：

1. 您指的是一个不存在的插件，例如通过其组ID、工件ID或版本中的键入。
   
2. 您正在使用未部署到中央Maven存储库的第三方Maven插件，而您的POM/设置缺少所需的“插件库”来下载插件。注意，在查找插件及其依赖项时，不考虑“存储库>声明”，只搜索插件库。
   
3. 您配置的插件库需要身份验证，Maven无法向服务器提供正确的凭据。在这种情况下，请确保${Huff.Hoe}//M2/Stuts.xml包含一个声明，其与插件库的匹配使用。有关更详细的信息，请参见Maven设置参考。
   
4. 存在一个一般的网络问题，它阻止Maven访问任何远程存储库，例如缺少的代理配置。
   
5. Maven无法将文件保存到本地存储库中，请参阅LoalAlpLogiTyNoAccess。
   
6. 您所配置的插件库对于请求的插件的特定版本是禁用的。例如，如果您想使用插件的快照版本，请确保没有“快照> <启用”>错误/启用> 。同样，为了解决插件的发布版本，插件库不应该被配置为 >启用>错误> /使能> /发行版>。有关存储库配置的更多信息，请参见POM参考。
   
7. 在这些情况下，检查您的POM和/或设置的适当内容。如果您在Stutux.xml的配置文件中配置了插件库，还验证此配置文件实际上被激活，例如通过调用MVN帮助：活动配置文件。
   
8. 在一般网络相关问题的情况下，您也可以参考以下文章：
   • 配置代理
     
   • 安全和部署设置
     
   • 通过认证HTTPS的远程存储库访问指南

解决方法:

1. 删除maven库里面文件：.m2\repository\org\apache\maven\plugins
   右击maven项目,maven->update project,利用eclipse重新下载本地仓库
   参考文章
   • 效果:没有作用

2. 修改pom.xml文件

   1. 在pom.xml中添加新的dependency：
      org.apache.maven.plugins maven-compiler-plugin 3.1 maven-plugin
      • 效果: 没有作用
   2. 在build中添加：

         
           
             org.apache.maven.plugins
             maven.compiler.plugin
             
             1.5
             1.5
             true
             
          
        
       

   • 效果:没有作用

3. 更改setting.xml 文件的mirror镜像

   1. 更改为
      mirrorId repositoryId Human Readable Name for this Mirror. http://mvnrepository.com/
      • 没有作用
   2. 更改为
      alimaven central aliyun maven http://maven.aliyun.com/nexus/content/groups/public/
      • 下载很慢,有作用

以上解决办法是基于我公司内部网络的情况下进行,我的没有作用不代表不好使.最后在一个文章中发现, https://repo.maven.apache.org/maven2网站被禁,不知道消息是否靠谱.

转载于:https://www.cnblogs.com/donfaquir/p/9286035.html