私有库 nexus Dependency ‘SNAPSHOT‘ not found

原创 于 2024-03-30 14:53:12 发布 · 816 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#java #开发语言

文章讲述了开发者在使用私有库Nexus时遇到的SNAPSHOT依赖找不到的问题，原因是仅在dependencyManagement中声明了引用，而未在dependencies中实际指定。作者强调了基础设置的重要性，提醒大家注意在Maven中正确配置依赖关系。

私有库 nexus 提示 Dependency 'SNAPSHOT' not found

jar包无法下载，困扰了很久，后来才发现，是因为只在 dependencyManagement 里写了引用，没有在具体的  dependencies 里引用，导致无法获取到jar包，低级错误，以后要避免。还是基础不牢，浪费自己的时间。

dependencyManagement 只是管理引用的，并不真正的引用jar包。

真正需要引用，得在单独的 dependencies 节点里引用。

参考：Maven中关于dependencyManagement和普通dependencies的区别_dependencymanagement 下会导入jar包吗-CSDN博客

运行tomcat服务器失败？！！error显示-D:......XXX-1.0-SNAPSHOT not found for the web module.让我来看看
ysy1119的博客
01-29 888
这两天做项目一直出现的一个问题，在gitee上下拉了队友的代码后，队友一直没有clean，“target”包里还存留着XXX-1.0-SNAPSHOT这个文件夹，而我在拉代码过来后习惯性clean（target包会清理）结果一运行tomcat，omg，失败了直接给我弹“黄牌”。试了网上的一些教程，都不得行，后面结合 了一下问题解决了， 我这里就总结一下我的方法。
NEXUS 上传到私仓的SNAPSHOT 包下载不下来
爬到松树上的猪
10-15 2565
原文地址：http://www.cnblogs.com/acm-bingzi/p/maven-nexus-snapshot.html   使用NEXUS 上传 SNAPSHOT版本的jar包到服务器上，但是下载不下来，报错提示：Dependency ... not found 后来百度到一句话： 　　Maven内置的插件远程仓库配置，关闭了对SNAPSHOT的支持，防止不稳定的构建 所以解...
org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT was not found in https://repository.apache.org/snapsho
wufabao的博客
03-14 1万+
报错内容 Java操作Hive数据库，引入了hive-jdbc驱动，在使用maven-assembly-plugin插件进行打包时报错 org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT was not found in https://repository.apache.org/snapshots during a previous attempt. This failure was cached in the local repository and resolu
Maven异常：0.0.1-SNAPSHOT: Could not find artifact
小枫哥的博客
03-07 1万+
解决方案 将父项目install到本地仓库，重新对子项目进行打包 报错情景 父项目需要用到子项目，会将子项目加入POM的依赖 比如： <dependencyManagement> <dependencies> <dependency> <groupId>com.tonited</groupId&g...
自建 Nexus OSS 私库无法下载Snapshot版本依赖的问题
adminmy的博客
05-13 1012
自建 Nexus OSS 私库无法下载Snapshot版本依赖的问题 无法从Nexus OSS中下载对应的SNAPSHOT版依赖，但该依赖确实存在于仓库中，而获取Release版依赖却又正常。 错误信息： ERROR : Could not find artifact com.example:example:jar:1.0-SNAPSHOT 原因： 从Release仓库下载Snapshot版依赖包，这当然找不到啦，我的原因是没有在Maven的setting.xml
解决Dependency ‘org.csource:fastdfs-client-java:1.29-SNAPSHOT‘ not found（解决maven仓库中找不到依赖）的问题
langhuage的博客
11-29 1457
解决maven仓库中找不到依赖
Dependency 'com.itheima:Ckm_work_common:1.0-SNAPSHOT' not found
06-20
如果依赖存在于某个私有仓库中（例如公司内部的Nexus或Artifactory），需要在项目的`pom.xml`文件中添加相应的仓库配置。例如： ```xml <id>private-repo <url>...
[INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.431 s [INFO] Finished at: 2025-07-07T16:56:29+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project tsp_group_api-graphflow: Could not resolve dependencies for project com.sankuai.tsp.group:tsp_group_api-graphflow:jar:1.0-SNAPSHOT [ERROR] dependency: com.sankuai.tsp.group:tsp_group_api-common:jar:1.0-SNAPSHOT (compile) [ERROR] Could not find artifact com.sankuai.tsp.group:tsp_group_api-common:jar:1.0-SNAPSHOT in meituan-offline-releases (http://maven.offline.sankuai.com/nexus/content/groups/public) [ERROR] com.sankuai.tsp.group:tsp_group_api-common:jar:1.0-SNAPSHOT was not found in http://pixel.sankuai.com/repository/mtdp during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of meituan-dianping has elapsed or updates are forced [ERROR] dependency: com.sankuai.tsp.group:phfc_group_integration-infra:jar:1.0-SNAPSHOT (compile) [ERROR] Could not find artifact com.sankuai.tsp.group:phfc_group_integration-infra:jar:1.0-SNAPSHOT in meituan-offline-releases (http://maven.offline.sankuai.com/nexus/content/groups/public) [ERROR] com.sankuai.tsp.group:phfc_group_integration-infra:jar:1.0-SNAPSHOT was not found in http://pixel.sankuai.com/repository/mtdp during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of meituan-dianping has elapsed or updates are forced [ERROR] dependency: com.sankuai.tsp.group:phfc_guide_integration-infra:jar:1.0-SNAPSHOT (compile) [ERROR] Could not find artifact com.sankuai.tsp.group:phfc_guide_integration-infra:jar:1.0-SNAPSHOT in meituan-offline-releases (http://maven.offline.sankuai.com/nexus/content/groups/public) [ERROR] com.sankuai.tsp.group:phfc_guide_integration-infra:jar:1.0-SNAPSHOT was not found in http://pixel.sankuai.com/repository/mtdp during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of meituan-dianping has elapsed or updates are forced [ERROR] dependency: com.sankuai.tsp.group:phfc_general_integration-infra:jar:1.0-SNAPSHOT (compile) [ERROR] Could not find artifact com.sankuai.tsp.group:phfc_general_integration-infra:jar:1.0-SNAPSHOT in meituan-offline-releases (http://maven.offline.sankuai.com/nexus/content/groups/public) [ERROR] com.sankuai.tsp.group:phfc_general_integration-infra:jar:1.0-SNAPSHOT was not found in http://pixel.sankuai.com/repository/mtdp during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of meituan-dianping has elapsed or updates are forced [ERROR] [ERROR] -> [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/DependencyResolutionException 进程已结束，退出代码为 1
07-08
我们面对的是一个Maven构建失败的问题，具体错误是：无法解析项目`com.sankuai.tsp.group:tsp_group_api-graphflow:jar:1.0-SNAPSHOT`的依赖，并且在内部的Nexus仓库中找不到多个`com.sankuai.tsp.group`组下的`1.0-...
我的maven报了如下错误，该如何解决： [ERROR] Failed to execute goal on project api-gateway-openapi-core: Could not collect dependencies for project com.tplink.smb.omada:api-gateway-openapi-core:jar:6.1.0.915-SNAPSHOT [ERROR] Failed to read artifact descriptor for com.tplink.smb.omada:api-gateway-openapi-common:jar:6.1.0.915-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: com.tplink.smb.omada:omada-api-gateway:pom:6.1.0.915-SNAPSHOT (absent): com.tplink.smb.omada:omada-api-gateway:pom:6.1.0.915-SNAPSHOT was not found in https://nexus.crd.tp-link.com/repository/smb-maven-public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of smb-nexus has elapsed or updates are forced [ERROR] Failed to read artifact descriptor for com.tplink.smb.omada:api-gateway-common:jar:6.1.0.910-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: com.tplink.smb.omada:omada-api-gateway:pom:6.1.0.915-SNAPSHOT (absent): com.tplink.smb.omada:omada-api-gateway:pom:6.1.0.915-SNAPSHOT was not found in https://nexus.crd.tp-link.com/repository/smb-maven-public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of smb-nexus has elapsed or updates are forced
最新发布
11-29
深层原因都是由于同一个依赖项`com.tplink.smb.omada:omada-api-gateway:pom:6.1.0.915-SNAPSHOT`无法从公司的私有仓库`https://nexus.crd.tp-link.com/repository/smb-maven-public/`中解析，并且这个失败已经被...
[ERROR] Failed to execute goal on project ruoyi-admin: Could not resolve dependencies for project com.ruoyi:ruoyi-admin:jar:4.8.0 [ERROR] dependency: com.ruoyi:ruoyi-framework:jar:4.8.0 (compile) [ERROR] com.ruoyi:ruoyi-framework:jar:4.8.0 was not found in https://maven.aliyun.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of public has elapsed or updates are forced [ERROR] com.ruoyi:ruoyi-framework:jar:4.8.0 was not found in https://maven.aliyun.com/nexus/content/groups/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of alimaven has elapsed or updates are forced [ERROR] dependency: com.ruoyi:ruoyi-quartz:jar:4.8.0 (compile) [ERROR] com.ruoyi:ruoyi-quartz:jar:4.8.0 was not found in https://maven.aliyun.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of public has elapsed or updates are forced [ERROR] com.ruoyi:ruoyi-quartz:jar:4.8.0 was not found in https://maven.aliyun.com/nexus/content/groups/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of alimaven has elapsed or updates are forced [ERROR] dependency: com.ruoyi:ruoyi-generator:jar:4.8.0 (compile) [ERROR] com.ruoyi:ruoyi-generator:jar:4.8.0 was not found in https://maven.aliyun.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of public has elapsed or updates are forced [ERROR] com.ruoyi:ruoyi-generator:jar:4.8.0 was not found in https://maven.aliyun.com/nexus/content/groups/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the
07-09
如果项目使用私有仓库（如公司内部库），在`<repositories>`中添加对应配置。 - **常见错误**：`settings.xml`中仓库URL错误或镜像覆盖不全，导致依赖下载失败[^2]。 #### 步骤3: 清理本地仓库并强制更新 - **...
Non-resolvable parent POM for com.cmcc.cmit.devops.platform.agile:agile:3.0.0-SNAPSHOT: The following artifacts could not be resolved: com.ai:zeus:pom:2.0-SNAPSHOT (absent): com.ai:zeus:pom:2.0-SNAPSHOT was not found in https://maven.aliyun.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of aliyunmaven has elapsed or updates are forced and 'parent.relativePath' points at no local POM idea在构建Maven时候出现错误
07-23
由于错误信息提到“not found in aliyun repository”，我们需要确认阿里云仓库是否支持SNAPSHOT版本的下载。默认情况下，阿里云中央仓库（配置为<mirrorOf>central）不提供SNAPSHOT版本。因此，需要为SNAPSHOT仓库...
maven私服有包 却NOT find， Nexus提示(Not Locally Cached)
哎呀的博客
03-14 5112
maven项目老是提示找不到包，可是明明包都存在，包是自己写的需要发布：发布到自己的私服（nexus搭建）。可是当用maven update 的时候 Could not find artifact 确认位置URL 都正确，在Nexus 中也能看到自己上传上去的包，点击Download 却发现404 - Not FoundThe path xxx/xxx.jar is cached until 20...
nexus3 无法上传release与snapshot版本问题与解决方法
我还会大跳的博客
03-05 8700
nexus3 无法上传release与snapshot版本问题与解决方法
maven TestNg 测试框架 not found
jiaobuchong的专栏
11-05 2811
在用TestNG测试框架进行单元测试时，在我的pom.xml中写的依赖： org.testng testng 6.9.4 test Maven说他在中央仓库没有没有找到，我在下面这两个maven仓库的网站查找我的TestNG也没有找到： http://mvnrepository
执行compile后，maven报错：could not find artifact com.xxx-SNAPSHOT
热门推荐
kite的博客
05-08 2万+
执行compile后，maven报错： could not find artifact com.JavaDemo:ssm_pojo:pom:1.0-SNAPSHOT 表示maven在本地仓库找不到这个资源包。 我们可以在maven的本地仓库查看该资源包是否存在，大概率是不存在的。 解决办法是：在该资源包所在的模块下，执行maven生命周期中的"install"将资源包安装在本地仓库： 日志中输出build success后，可以在本地仓库中看到资源包了。 然后就可以正常的执行compile了。 记住
解决云尚办公系统中，Could not find artifact com.atguigu:common:pom:1.0-SNAPSHOT尝试使用 -U 标记(强制更新快照)运行 Maven 导入
m0_74099927的博客
03-21 789
解决云尚办公系统中，Could not find artifact com.atguigu:common:pom:1.0-SNAPSHOT尝试使用 -U 标记(强制更新快照)运行 Maven 导入
maven的SNAPSHOT依赖，找不到类解决方法
breezylee09的专栏
05-03 3250
  现象： 在maven的pom.xml依赖配置里加了一个SNAPSHOT版本的依赖： &lt;dependency&gt; &lt;groupId&gt;com.yame.ecpark&lt;/groupId&gt; &lt;artifactId&gt;ecpark-cache-driver&lt;/artifactId&gt; &lt;version&gt;1...
记一次nexus启动报错，java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext
cjq1027484794的博客
12-15 495
记一次nexus启动报错，java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext 由于最近在学习搭建maven的私服搭建，但是由于第一次的nexus install，nexus start，nexus stop 都没有什么问题，就觉得已经搭建好了，但是隔了几天在重新nexus start的时候报错了java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext，通过百度，有人说是jdk
maven构建报错程序包org.testng不存在
iSelenium
04-11 1万+
[INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /D:/Jenkins/workspace/mav...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值