2011-01-05 17 views
1

我試圖編譯一個項目,它會引發錯誤,指出插件無法解析。我能夠從命令行運行mvn install,並且工作完美。從eclipse(Helios)調用mvn install時,它給了我下面給出的錯誤。我驗證了罐子存在於我的本地庫(C:\用戶....平方米\庫)eclipse maven error - 存儲庫中沒有任何版本,其範圍爲

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 

回答

0

也許你打this issue或類似的一個。看起來你的pom有一個weblogic-maven-plugin依賴項的版本範圍。你可以嘗試改變它,看看是否有幫助。

+1

我在我的pom.xml中指定了一個特定的版本。然而,你的回答是一個眼睛。隨同weblogic-maven-plugin一起提供的pom文件提到了對創建問題的版本範圍的依賴性。我在.pom文件中手動更改了版本,並且它工作正常。 – coolguy 2011-01-05 13:35:46

0

我想你使用m2eclipse插件。這使用了一個嵌入式maven 3版本(請參閱首選項 - > Maven - >安裝),它可能與從命令行運行maven不同。

你應該在這裏添加你的外部maven安裝並使用它在eclipse中得到和命令行一樣的結果。

我不確切地知道maven 2和3之間的變化,但在指定版本範圍時聽說過對SNAPSHOT版本的不同處理。

+0

我沒有在我的eclipse(Helios)中看到Maven安裝的任何部分。 – coolguy 2011-01-05 13:33:22

1

Eclipse >> Window> Preferences> Maven> Installations

相關問題