[mojo-dev] [jira] (MVERSIONS-261) Build doe not fail when version not found

[Steve Boardwell (JIRA)]

Title: Message Title

Steve Boardwell created an issue   Mojo's Versions Maven Plugin / MVERSIONS-261 Build doe not fail when version not found Issue Type: Bug Affects Versions: 2.1 Assignee: Unassigned Created: 25/Jul/14 4:12 AM Priority: Major Reporter: Steve Boardwell I'm really not sure if this is a bug or a feature. The update-parent goal is not very strict when executing. Here's my scenario: I want to update the parent version of my project from snapshot to a specific version before building. If the specified version cannot be found in the repository, I would expect that the build fails, since it's wasn't able to do the done requested. Instead, a warning is written and the build is marked as SUCCESSFUL: [WARNING] Not updating version: could not resolve any versions [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ or [WARNING] Not updating version: could not find com.example.project:example-root:pom:1.1.0-1163 org.apache.maven.artifact.resolver.ArtifactNotFoundException: The repository system is offline but the artifact com.example.project:example-root:pom:1.1.0-1163 is not available in the local repository. com.example.project:example-root:pom:1.1.0-1163 from the specified remote repositories: nexus (http://my-nexus-server:8081/nexus/content/groups/public/, releases=true, snapshots=true), nexus-releases (http://my-nexus-server:8081/nexus/content/repositories/releases, releases=true, snapshots=true), nexus-snapshots (http://my-nexus-server:8081/nexus/content/repositories/snapshots, releases=true, snapshots=true), at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:219) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveAlways(DefaultArtifactResolver.java:163) at org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.shouldApplyUpdate(AbstractVersionsUpdaterMojo.java:439) at org.codehaus.mojo.versions.UpdateParentMojo.update(UpdateParentMojo.java:114) at org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.process(AbstractVersionsUpdaterMojo.java:322) at org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.execute(AbstractVersionsUpdaterMojo.java:257) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: The repository system is offline but the artifact com.example.project:example-root:pom:1.1.0-1163 is not available in the local repository. at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:213) ... 26 more Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: The repository system is offline but the artifact com.example.project:example-root:pom:1.1.0-1163 is not available in the local repository. at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:348) ... 30 more [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ My questions: Is there an option 'strictUpdate' or similar, which could toggle between: WARNING and the build continues ERROR and the build fails. If there is no such option, could we have one, or is there maybe another way to solve this problem? Thanks for all your help. Steve Add Comment   This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email