CentOS系统中Maven编译出错 dependencies could not be resolved
2016-09-02 11:03
357 查看
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building zkui 2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://maven.oschina.net/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.983 s
[INFO] Finished at: 2016-09-01T19:53:30-07:00
[INFO] Final Memory: 11M/95M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5
from/to osc (http://maven.oschina.net/content/groups/public/): maven.oschina.net: Temporary failure in name resolution: Unknown host maven.oschina.net: Temporary failure in name resolution -> [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/PluginResolutionException
解决方法:把/etc/resolv.conf文件打开,最末尾加上以下两行:
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building zkui 2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://maven.oschina.net/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.983 s
[INFO] Finished at: 2016-09-01T19:53:30-07:00
[INFO] Final Memory: 11M/95M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5
from/to osc (http://maven.oschina.net/content/groups/public/): maven.oschina.net: Temporary failure in name resolution: Unknown host maven.oschina.net: Temporary failure in name resolution -> [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/PluginResolutionException
解决方法:把/etc/resolv.conf文件打开,最末尾加上以下两行:
# Generated by NetworkManager nameserver 8.8.8.8 nameserver 8.8.4.4
相关文章推荐
- Maven编译的时候遇到【one of its dependencies could not be resolved】
- 【已解决】NDK下Eclipse中交叉编译C项目出错:Symbol ‘NULL’ could not be resolved(JNI)
- Myeclipse和Maven整合maven-resources-plugin:2.4.3 or one of its dependencies could not be resolved
- maven-compiler-plugin:3.5.2 or one of its dependencies could not be resolved: Failure to find org.ap
- Maven Could not resolve dependencies, artifacts could not be resolved
- Eclipse创建maven项目时报错:maven-resources-plugin:2.5 or one of its dependencies could not be resolved
- CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-compiler-plugin:3.1 or one of its dependencies could not be resolved
- Eclipse导入maven项目时报错:maven-resources-plugin:2.5 or one of its dependencies could not be resolved
- 新系统中导入maven失败出错,Could not calculate build plan
- Android NDK开发编译时提示 Native method not found,NDK *** could not be resolved
- 解决Eclipse交叉编译环境下出现Symbol"NULL" could not be resolved
- android--jni编译错误的解决方案:.c源文件出现类似Type 'jstring' could not be resolved
- maven构建 出错:cannot be resolved to absolute file path because it does not reside in the file system
- Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be r
- Plugin org.apache.maven.plugins:maven-compiler-plugin:2.0.2 or one of its dependencies could not be
- Eclipse之NDK编译-- Type 'jint' could not be resolved, and JNIEnv, jclass错误解决办法
- android NDK开发编译时出现Type 'jint' could not be resolved和Unresolved inclusion: <jni.h>的解决办法
- Maven编译错误:Could not generate DH keypair: Prime size must be multiple of 64...
- 编译jni时遇到错误提示:Symbol 'ANDROID_LOG_INFO' could not be resolved
- 管理工具---Maven系列(一)编译问题Could not resolve dependencies for project