Forum Discussion
al0
13 years agoOccasional Contributor
For me 4.0.2 results into a much more basic error
Note, that if I change to 4.0.0 or 4.0.1 no artifact resolution issues arise.
And eviware repository in in the POM
[ERROR] Plugin eviware:maven-soapui-pro-plugin:4.0.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT -> [Help 1]
13-Mar-2012 15:26:42 org.apache.maven.plugin.PluginResolutionException: Plugin eviware:maven-soapui-pro-plugin:4.0.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT
13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129)
13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142)
13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261)
13-Mar-2012 15:26:42 at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:152)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:139)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:129)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:92)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
13-Mar-2012 15:26:42 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
13-Mar-2012 15:26:42 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
13-Mar-2012 15:26:42 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
13-Mar-2012 15:26:42 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
13-Mar-2012 15:26:42 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
13-Mar-2012 15:26:42 at java.lang.reflect.Method.invoke(Method.java:597)
13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT
13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)
13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279)
13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115)
13-Mar-2012 15:26:42 ... 25 more
13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT
13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281)
13-Mar-2012 15:26:42 ... 28 more
13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT
13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
13-Mar-2012 15:26:42 ... 31 more
Note, that if I change to 4.0.0 or 4.0.1 no artifact resolution issues arise.
And eviware repository in in the POM
<pluginRepositories>
<pluginRepository>
<id>maven2-eviware-repository</id>
<name>Eviware Maven 2 Repository (for SoapUI)</name>
<url>http://www.eviware.com/repository/maven2/</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
Related Content
- 8 years ago
- 8 years ago
- 9 years ago
Recent Discussions
- 22 days ago