首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >eclipse maven错误-存储库中没有包含某个范围的工件的版本

eclipse maven错误-存储库中没有包含某个范围的工件的版本
EN

Stack Overflow用户
提问于 2011-01-05 19:17:22
回答 3查看 5.6K关注 0票数 1

我正在尝试制作一个项目,它抛出了我的错误,说插件无法解决。我能够从命令行运行mvn install,它工作得很好。当从eclipse (Helios)调用mvn install时,它给出了如下错误。我验证了jars是否存在于我的本地存储库(c:\users....m2\repository)中

代码语言:javascript
复制
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to construct build plan for: Unnamed - myapp:myapp-ecom:war:1.0
Id: myapp:myapp-ecom:war:1.0
task-segment: [install]. Reason: Failed to resolve plugin for mojo binding: org.codehaus.mojo:weblogic-maven-plugin:2.9.1:listapps
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:414)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:235)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.eclipse.iam.core.embedder.internal.EclipseMaven.executeRequest(EclipseMaven.java:325)
at org.eclipse.iam.core.embedder.internal.EclipseMavenRequest.run(EclipseMavenRequest.java:160)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.apache.maven.lifecycle.plan.LifecyclePlannerException: Failed to resolve plugin for mojo binding: org.codehaus.mojo:weblogic-maven-plugin:2.9.1:listapps
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescriptor(DefaultBuildPlanner.java:345)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.findForkModifiers(DefaultBuildPlanner.java:192)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addForkedLifecycleModifiers(DefaultBuildPlanner.java:179)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0(DefaultBuildPlanner.java:117)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice(DefaultBuildPlanner.java:403)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:1)
at org.eclipse.iam.core.embedder.internal.EclipseMavenBuildPlanner.constructBuildPlan(EclipseMavenBuildPlanner.java:43)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:400)
... 12 more
Caused by: org.apache.maven.plugin.loader.PluginLoaderException: Failed to load plugin. Reason: No versions are present in the repository for the artifact with a range [9.0,11.0)
weblogic:weblogic:jar:null

from the specified remote repositories:
codehaus.org (http://repository.codehaus.org),
snapshots (http://snapshots.repository.codehaus.org),
central (http://central)
Path to dependency:
1) org.codehaus.mojo:weblogic-maven-plugin:maven-plugin:2.9.1


at org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:89)
at org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:52)
at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescriptor(DefaultBuildPlanner.java:322)
... 19 more
Caused by: org.apache.maven.artifact.versioning.OverConstrainedVersionException: No versions are present in the repository for the artifact with a range [9.0,11.0)
weblogic:weblogic:jar:null

from the specified remote repositories:
codehaus.org (http://repository.codehaus.org),
snapshots (http://snapshots.repository.codehaus.org),
central (http://central)
Path to dependency:
1) org.codehaus.mojo:weblogic-maven-plugin:maven-plugin:2.9.1


at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:496)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:138)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:423)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:394)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:337)
at org.apache.maven.plugin.DefaultPluginManager.getPluginArtifacts(DefaultPluginManager.java:436)
at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:279)
at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:211)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:186)
at org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:79)
... 21 more
EN

回答 3

Stack Overflow用户

回答已采纳

发布于 2011-01-05 20:47:44

也许你正在使用this issue或者类似的工具。看起来你的pom有一个weblogic-maven-plugin依赖的版本范围。您可以尝试更改它,看看这是否有帮助。

票数 0
EN

Stack Overflow用户

发布于 2011-10-15 04:34:09

Eclipse >>窗口>首选项> Maven >安装

票数 1
EN

Stack Overflow用户

发布于 2011-01-05 20:49:32

我想您使用的是m2eclipse插件。它使用的是一个嵌入式maven 3版本(参见Preferences -> Maven -> Installation),该版本可能与从命令行运行maven的版本不同。

您应该在此处添加您的外部maven安装,并使用它在eclipse中获得与在命令行中相同的结果。

我不确切地知道maven 2和maven 3之间的变化,但听说在指定版本范围时对快照版本的不同处理。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/4603450

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档