【问题标题】:eclipse maven error - No versions are present in the repository for the artifact with a rangeeclipse maven错误-存储库中不存在具有范围的工件的版本
【发布时间】:2011-01-05 11:17:21
【问题描述】:

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

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

【问题讨论】:

    标签: eclipse maven-2 m2eclipse


    【解决方案1】:

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

    【讨论】:

      【解决方案2】:

      也许您正在点击this issue 或类似的。看起来您的 pom 具有 weblogic-maven-plugin 依赖项的版本范围。您可以尝试更改它,看看是否有帮助。

      【讨论】:

      • 我在我的 pom.xml 中指定了一个特定的版本。但是,您的回答令人大开眼界。 weblogic-maven-plugin 附带的 pom 文件提到了对创建问题的版本范围的依赖。我在 .pom 文件中手动更改了版本,它工作正常。
      【解决方案3】:

      我想你使用 m2eclipse 插件。这使用嵌入式 maven 3 版本(请参阅首选项 -> Maven -> 安装),它可能与从命令行运行 maven 的版本不同。

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

      我不确切了解 maven 2 和 3 之间的变化,但听说过在指定版本范围时对 SNAPSHOT 版本的不同处理。

      【讨论】:

      • 我在 Eclipse (Helios) 中没有看到任何 maven 安装部分。
      猜你喜欢
      • 2014-08-10
      • 1970-01-01
      • 2012-06-05
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2019-10-11
      • 1970-01-01
      相关资源
      最近更新 更多