blocks|key|842675|text|您提到了两个不同的groupIds，com.morrislgn.merchandising.common和com.johnlewis.jec.webpim.common。也许这就是问题所在。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|842676|entityMap^0|I|Y|1H|V|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

You mention two different groupIds, <code>com.morrislgn.merchandising.common</code> and <code>com.johnlewis.jec.webpim.common</code>. Maybe this is the problem.

blocks|key|842739|text|我通过删除除.jar和.pom文件之外的所有显示此错误的存储库文件夹解决了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|842740|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I solved this issue by deleting in the repository folders where this error was shown everything except the .jar and .pom files.

blocks|key|627179|text|“无法读取工件描述符”问题通常表示maven存储库中依赖项的pom文件有问题。我建议您仔细检查pom文件的名称是否与maven期望的名称相同，并检查pom文件内容是否有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627180|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

"Failed to read artifact descriptor" problems generally indicate a problem with the dependency's pom file in the maven repository. I would suggest you to double check if the pom file's name is the same with the name maven expects, and also to check if the pom file contents are valid.

blocks|key|627208|text|您可以随时尝试mvn+-U+clean+install|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|627209|-U强制检查远程存储库上的更新版本和快照。|627210|entityMap^0|7|K|0|0|2|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

You can always try <code>mvn -U clean install</code>

<code>-U</code> forces a check for updated releases and snapshots on remote repositories.

blocks|key|627283|text|我知道我来晚了，但我也有这个问题。我想问题出在我公司的防火墙上。我的解决方案是断开网络连接，连接到我们开放的无线网络，然后通过Eclipse强制更新。这就解决了所有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627284|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I know I'm pretty late to the conversation, but I had this problem too. I think the issue was my company's firewall. My solution was to unplug from the network, connect to our open wireless and then force an update via Eclipse. This resolved everything.

blocks|key|842978|text|没有任何幸运的更新通过eclipse。必须使用mvn全新安装-U+(这解决了所有问题)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|842979|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Did not have any luck updating via eclipse. Had to use mvn clean install -U (which resolved everything).

blocks|key|843071|text|对我来说，这与在内部设置"User+Setting.xml“有关|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843072|Window+>+preferences+>+Maven+>+User+Settings+>+and+then+browsing+to+the+user+Settings+inside+the+{+maven+unarchived+directory+/+}/apache-maven-2.2.1/conf/settings.xml+.+|code-block|syntax|javascript|843073|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For me , it was related to setting the "User Setting.xml" inside 

<pre><code>Window &gt; preferences &gt; Maven &gt; User Settings &gt; and then browsing to the user Settings inside the { maven unarchived directory / }/apache-maven-2.2.1/conf/settings.xml . 
</code></pre>

blocks|key|627487|text|如果您有一些引用父pom的子项目，并且您尚未从父pom目录安装(从父目录运行mvn+install+)，则可能会出现此问题。其中一个子项目可能依赖于兄弟项目，当它读取兄弟项目的pom时，它将失败并出现问题中提到的错误，除非您至少从父pom目录安装了一次。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|627488|当我把一个项目移到一台新电脑上时，我就遇到了这个问题。我习惯于从子项目运行命令，而不是在父项目上运行install。|627489|entityMap^0|12|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

This problem can occur if you have some child projects that refer to a parent pom and you have not installed from the parent pom directory (run <code>mvn install</code> from the parent directory). One of the child projects may depend on a sibling project and when it goes to read the pom of the sibling, it will fail with the error mentioned in the question unless you have installed from the parent pom directory at least once.

I just ran into this problem when moving a project to a new computer. I was in the habit of running commands from the child project and didn't run install on the parent.

blocks|key|843176|text|参考Maven+error+"Failure+to+transfer..."|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|843177|find+~/.m2++-name+"*.lastUpdated"+-exec+grep+-q+"Could+not+transfer"+{}+\;+-print+-exec+rm+{}+\;|code-block|syntax|javascript|843178|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/5074063/maven-error-failure-to-transfer^0|2|10|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Reference 
<a href="https://stackoverflow.com/questions/5074063/maven-error-failure-to-transfer">Maven error &quot;Failure to transfer...&quot;</a>

<pre><code>find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;
</code></pre>

blocks|key|627566|text|我在eclipse中遇到了这个问题，mvn+-U+clean+install不起作用，但是右键单击项目并选择Maven->Update+project修复它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|627567|entityMap^0|I|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had this problem in eclipse, <code>mvn -U clean install</code> didn't work but right clicking the project and selecting Maven->Update Project fixed it.

blocks|key|627630|text|对我来说，这似乎是一个依赖POM的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627631|我通过使用jitpack虚拟存储库解决了这个问题，通过它，您可以根据github存储库的URL而不是它们自己的POM+(在我的例子中似乎是错误的)来包含github存储库。|627632|++++<repository>
++++++++<id>jitpack.io</id>
++++++++<url>https://jitpack.io</url>
++++</repository>|code-block|syntax|javascript|627633|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For me, it seems to actually have been a problem with the dependency POM.

I worked around it by using the jitpack virtual repository, with which you can include github repositories based on their URL instead of their own POM (which seems to have been erroneous in my case).

<pre><code> &lt;repository&gt;
 &lt;id&gt;jitpack.io&lt;/id&gt;
 &lt;url&gt;https://jitpack.io&lt;/url&gt;
 &lt;/repository&gt;
</code></pre>

blocks|key|843384|text|我通过更改maven+setting.xml和存储库解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843385|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I solved this problem by changing the maven setting.xml and repository

blocks|key|627741|text|有一段时间我遇到了同样的问题，尽管我做了mvn+-U+clean+install，但问题并没有得到解决！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|627742|我最终解决了这个问题，删除了整个.m2文件夹，然后重启了我的集成开发环境，问题就解决了！|627743|因此，有时问题会因为本地maven存储库中的一些不兼容或问题而出现。|627744|entityMap^0|K|K|0|G|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

I had the same problem for a while and despite doing <code>mvn -U clean install</code> the problem was not getting solved!

I finally solved the problem by deleting the whole <code>.m2</code> folder and then restarted my IDE and the problem was gone!

So sometimes the problem would rise because of some incompatibilities or problems in your local maven repository.

blocks|key|843518|text|我也遇到过类似的问题。在我的例子中，.m2/repositories文件夹中的testng版本已经损坏，但当我删除它并再次进行maven更新时，一切正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843519|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a similar problem. In my case, the version of testng in my .m2/repositories folder was corrupt, but when I deleted it &amp; did a maven update again, everything worked fine.

blocks|key|843596|text|我在使用IntelliJ时也遇到了同样的问题。我通过右键单击pom.xml+>+Maven+>+Reimport解决了问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843597|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had same problem using IntelliJ. I solved with right click on pom.xml > Maven > Reimport

blocks|key|843661|text|这对我很有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843662|从集成开发环境(在我的例子中是Red+Studio+)。|843663|->+->显示视图Windows终端->打开/添加本地终端|843664|按如下方式运行命令>|843665|$+cd+/pom-file-path/|offset|length|style|CODE|843666|$+mvn+-U+clean+install|843667|entityMap^0|0|0|0|0|2|I|0|2|K|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$J|W|K|X|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@$J|Z|K|10|L|M]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

This helped me:

From the IDE (Red Hat CodeReady Studio in my case).

Windows -> Show View -> Terminal -> Open/Add local terminal

Run commands as follows > 

$ <code>cd /pom-file-path/</code>

$ <code>mvn -U clean install</code>

blocks|key|628016|text|我知道我很勇敢，九年后的问题...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|628017|对我来说，这是一个没有找到子依赖关系的问题。我最终通过查看包含An+internal+error+occurred+during:+"Building".-line的“错误日志”-view找到了真正的问题所在。双击它显示了一个带有堆栈跟踪的弹出窗口，最后一个原因最终揭示了我本地存储库中的一个损坏的JAR。我把它清理干净了，Eclipse/m2e又可以工作了。|offset|length|style|CODE|628018|entityMap^0|0|V|1A|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I know I'm brave, nine years after the question...
For me it was a problem where sub-dependencies weren't found. I finally found the real issue by looking at the &quot;Error Log&quot;-view that held a <code>An internal error occurred during: &quot;Building&quot;.</code>-line. Double-clicking it showed a pop-up with a stacktrace and the last cause finally disclosed a broken JAR in my local repository. I cleaned that up and Eclipse/m2e was able to work again.

I am hoping someone can help me with a problem I am struggling with.

When I try to build my project from the terminal I get this error:

<pre><code>Failed to read artifact descriptor for com.morrislgn.merchandising.common:test-data-utils:jar:0.3b-SNAPSHOT: Could not find artifact com.morrislgn.merchandising:merchandising:pom:0.3b-SNAPSHOT
</code></pre>

The <code>common.test-data-utils</code> jar is created by a separate project and shared between this and another project (the other project doesn't build either, but that is down to another problem). 

I am able to build <code>com.morrislgn.merchandising.common:test-data-utils</code> without issue, I can see the entry it makes in the <code>.m2</code> local repository on my machine. I have reindexed my repository in Eclipse also. 

The POM for my project has this entry:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;com.morrislgn.merchandising.common&lt;/groupId&gt;
 &lt;artifactId&gt;test-data-utils&lt;/artifactId&gt;
 &lt;version&gt;0.3b-SNAPSHOT&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

Which appears to be correct to me - the POM doesn't report any errors either when it is viewed in Eclipse.

Can some one tell me what I am missing here or doing wrong?

Maven: Failed to read artifact descriptor

集成开发环境

防火墙

Windows

Eclipse

我希望有人能帮助我解决一个我正在努力解决的问题。当我试图从终端构建我的项目时，我得到了这个错误：Failed to read artifact descriptor for com.morrislgn.merchandising.common:test-data-utils:jar:0.3b-SNAPSHOT: Cou...

问Maven:无法读取项目描述符
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Maven:无法读取项目描述符EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Maven:无法读取项目描述符
EN