The POM for XXX:jar:${com.ld.base.service.version} is missing, no dependency information available

最近有个jar改了名字后,有个依赖它的工程死活引用的是老名字,导致打包的时候出错,如下所示:

[INFO] ------------------------------------------------------------------------
[INFO] Building com.ld.base.runtime 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.jxls:jxls:jar:1.0.8 is missing, no dependency information available
[WARNING] The POM for com.ld.base:com.ld.base.service:jar:${com.ld.base.service.version} is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.644 s
[INFO] Finished at: 2016-11-21T12:02:22+08:00
[INFO] Final Memory: 7M/18M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project com.ld.base.runtime: Could not resolve dependencies for project com.ld.base:com.ld.base.runtime:war:1.0.0-SNAPSHOT: Failure to find com.ld.base:com.ld.base.service:jar:${com.ld.base.service.version} in https://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 -> [Help 1]
[ERROR]

仔细检查了,肯定没有引用了,并且本地仓库、可能的classpath都删除重新force update了、工程都删除重新从svn更新了,还是报这个错。

最后实在没辙,通过人工添加个不存在引用来绕过去,如下所示:

<properties>
<com.ld.base.service.version>1.0.0-SNAPSHOT</com.ld.base.service.version>
</properties>

<dependency>
<groupId>com.ld.base</groupId>
<artifactId>com.ld.base.service</artifactId>
<version>${com.ld.base.service.version}</version>
<scope>system</scope>
<systemPath>d:/jar/com.ld.base.service-1.0.0-SNAPSHOT.jar</systemPath>
</dependency>

时间: 2024-11-01 14:05:16

The POM for XXX:jar:${com.ld.base.service.version} is missing, no dependency information available的相关文章

The POM for cn.e3mall:e3mall-common:jar:0.0.1-SNAPSHOT is missing, no dependency information available

[WARNING] The POM for cn.e3mall:e3mall-common:jar:0.0.1-SNAPSHOT is missing, no dependency information available[INFO] ------------------------------------------------------------------------[INFO] Reactor Summary:[INFO] [INFO] e3mall-manager .......

The POM for com.qingmu:entity:jar:1.0.0-SNAPSHOT is missing, no dependency information available

The POM for com.qingmu:entity:jar:1.0.0-SNAPSHOT is missing, no dependency information available 当出现这个异常的情况,因为我用的是父子工程.所以,出现这种情况的时候,需要在本地使用maven插件进行install一下. 原文地址:https://www.cnblogs.com/qingmuchuanqi48/p/12287358.html

Failed to execute goal on project MakeFriends: Could not resolve dependencie The POM for .chengpai.jtd:jtd-service-api:jar:1.0-SNAPSHOT is missing, no dependency information available

本笔者在学习maven的基础,然后建立了一个maven的项目,然后想对其进行依赖操作,pom.xml进行依赖操作时候出现了这样的错误,说是找不到这个依赖的包,但是事实上已经导入了这个包. 同时,也在maven的包环境中找得到它的依赖包 执行clean是成功的,但是test和Install就会显示丢失包,并且加载失败 解决方法: 1.首先,更改了test文件的名字,保持它与类的名字相同 2.对其依赖的maven项目进行clean和test install操作 3.重新对自己设置的这个maven项目

The POM for ... is missing, no dependency information available

今天在重温淘淘商城的项目,准备用idea重写次,换个bootstrap的前端框架,但是在用idea构建maven项目后编译时却报错了: 经再三确认,common工程自身并没有任何问题,引用这个工程的地方写法也没有任何问题,那么问题可能出在maven,或者说库和配置上,于是搜罗了一番Stack Overflow和国内的一些论坛,均为找到实质性能解决问题的办法,但是逛了半天也没白逛,经由启发,我给我的maven库增加了一个镜像配置: <mirrors> <mirror> <id&

Intellij Error:Cannot build Artifact &#39;XXX:war exploded&#39; because it is included into a circular dependency

https://stackoverflow.com/questions/42335718/intellij-errorcannot-build-artifact-xxxwar-exploded-because-it-is-included-i 基本按这个来就好了 如果到了build artfact哪里按钮是灰色 就要手动建了 https://jingyan.baidu.com/album/0a52e3f43d9f69bf62ed72f9.html?picindex=8 这里的百度经验真是久违的不

Error:Cannot build artifact &#39;XXX:war exploded&#39; because it is included into a circular dependency (artifact &#39;XXXX:war exploded&#39;, artifact &#39;XXX:war exploded&#39;) Idea启动项目报错解决方案

在Idea中使用Maven创建父子工程,第一个Model的那个项目可以很好的运行,在创建一个Model运行时报这个错.原因是tomcat部署了多个Web项目,可能最开始是两个项目的配置文件混用用,最后就报这个错. 网上找的解决方案: 步骤:File--  Porject Struccture ---- Artifacts 在Tomcat部署时war和war exploded区别: war模式:将WEB工程以包的形式上传到服务器 : war exploded模式:将WEB工程以当前文件夹的位置关系

maven的pom文件报错: must be &quot;pom&quot; but is &quot;jar&quot;

Project build error: Invalid packaging for parent POM com.test:hello-parent:0.0.1-SNAPSHOT (E:\eclipse-workspace\hello-parent\pom.xml), must be "pom" but is "jar" 解决办法 parent工程的pom.xml文件的project节点下加入如下节点: <packaging>pom</packa

Error: Unable to access xxx.jar

在cmd中运行java -jar xxx.jar出现如下错误: 解决方法: 使用绝对路径:java -jar D:\Program Files (x86)\xxx.jar 此时依然报错: Error: Unable to access jarfile D:\Program 添加双引号:java -jar "D:\Program Files (x86)\xxx.jar" 原文地址:https://www.cnblogs.com/tyk766564616/p/10316388.html

解决部署报错No main manifest attribute, in XXX.jar

将build中的入口改为如下即可解决: <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals> <goal>repa