Re: Maven SCM plugin fails to do a scm:update after a scm:checkout with strange error message "Command failed.The git-log command failed."
Hi Andreas, sorry its actually a private Git repo, I just replaced/obfuscated the domain name Sebastian Am 01.03.2013 20:56 schrieb "Andreas Gudian" : > Hi, > > Don't you have to use the https or ssh transport for github write access? > The git protocol is read-only on github. > > Anyway you're right, the error message is a bit confusing. ;) > > Andreas > > Am Donnerstag, 28. Februar 2013 schrieb seba.wag...@gmail.com : > > > Hi, > > > > I have configured a Maven project to checkout a Git project using: > > > > > > scm:git:g...@git.github.com: > > example/myproject.git > > > > > > > > Using: mvn scm:checkout > > > > The project checks out fine into target/checkout > > > > I would expect if do a "scm:update" it would simply work, cause > > scm:checkout works. But it doesn't. By running with the "-e" option (mvn > -e > > scm:update) to get the full stack trace, it will show some obscure error > > message: > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-scm-plugin:1.8.1:update (default-cli) > > on project mysampleproject: Command failed.The git-log command failed. > > -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.apache.maven.plugins:maven-scm-plugin:1.8.1:update > > (default-cli) on project mysampleproject: Command failed.The git-log > > command failed. > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > > 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:601) > > 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.apache.maven.plugin.MojoExecutionException: Command > > failed.The git-log command failed. > > at > > > org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:439) > > at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93) > > at > > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > > ... 19 more > > [ERROR] > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > > > Now what should this error tell me ? > > > > "git log" of course works. If I cd to the directory that Maven did > checkout > > using "scm:checkout", I can perform "git log" and will get the correct > > output. > > > > I have found the source code that produces the the Maven error: > > > > > > > http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/xref/org/apache/maven/scm/provider/git/gitexe/command/update/GitUpdateCommand.html > > > > "The git-log command failed." > > > > :) But it does not really tell me why "git-log" failed or what I > could > > do to resolve it. > > > > Any ideas about how I can further debug or resolve that issue? > > > > Sebastian > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > seba.wag...@gmail.com > > >
Re: Maven SCM plugin fails to do a scm:update after a scm:checkout with strange error message "Command failed.The git-log command failed."
Hi, Don't you have to use the https or ssh transport for github write access? The git protocol is read-only on github. Anyway you're right, the error message is a bit confusing. ;) Andreas Am Donnerstag, 28. Februar 2013 schrieb seba.wag...@gmail.com : > Hi, > > I have configured a Maven project to checkout a Git project using: > > > scm:git:g...@git.github.com: > example/myproject.git > > > > Using: mvn scm:checkout > > The project checks out fine into target/checkout > > I would expect if do a "scm:update" it would simply work, cause > scm:checkout works. But it doesn't. By running with the "-e" option (mvn -e > scm:update) to get the full stack trace, it will show some obscure error > message: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-scm-plugin:1.8.1:update (default-cli) > on project mysampleproject: Command failed.The git-log command failed. > -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-scm-plugin:1.8.1:update > (default-cli) on project mysampleproject: Command failed.The git-log > command failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > 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:601) > 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.apache.maven.plugin.MojoExecutionException: Command > failed.The git-log command failed. > at > org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:439) > at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > [ERROR] > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > Now what should this error tell me ? > > "git log" of course works. If I cd to the directory that Maven did checkout > using "scm:checkout", I can perform "git log" and will get the correct > output. > > I have found the source code that produces the the Maven error: > > > http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/xref/org/apache/maven/scm/provider/git/gitexe/command/update/GitUpdateCommand.html > > "The git-log command failed." > > :) But it does not really tell me why "git-log" failed or what I could > do to resolve it. > > Any ideas about how I can further debug or resolve that issue? > > Sebastian > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com >
RE: maven-scm-plugin fails
Thanks, I updated my local POM to use this version and everything seems to work fine now. Mario. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: vrijdag 15 juli 2005 12:39 To: Maven Users List Subject: Re: maven-scm-plugin fails I updated the plugin pom to a released version(2.0-alpha-3) of plugin-parent and redeploy it. It will be synchronize with ibiblio in few hours. Emmanuel Van Steenberghe Mario (GFDI) wrote: > Hi, > > The maven-scm-plugin is successfully downloaded now, but it seems to > fail to find the maven-plugin-parent:2.0-beta-1-SNAPSHOT:pom dependency, > which is not yet available from the http://repo1.maven.org/maven2 > repository. Is there any other repository I could use in the meantime ? > > Thanks, > Mario. > > Stack trace: > > [INFO] > > > [ERROR] BUILD ERROR > [INFO] > > > [INFO] Diagnosis: Error configuring plugin for execution of > 'scm:checkout'. > [INFO] > > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error configuring plugin > for execution of 'scm:checkout'. > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa > nager.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default > LifecycleExecutor.java:169) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa > l(DefaultLifecycleExecutor.java:150) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL > ifecycleExecutor.java:133) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:103) > at > org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) > at org.codehaus.classworlds.Launcher.main(Launcher.java:363) > Caused by: org.apache.maven.plugin.PluginConfigurationException: Cannot > resolve plugin dependencies > at > org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComp > lete(DefaultPluginManager.java:616) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl > uginManager.java:493) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa > nager.java:373) > ... 15 more > Caused by: > org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: > Unable to read the metadata file > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMeta > dataSource.java:88) > at > org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComp > lete(DefaultPluginManager.java:564) > ... 17 more > Caused by: org.apache.maven.project.ProjectBuildingException: Unable to > find the POM in the repository > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit > ory(DefaultMavenProjectBuilder.java:238) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa > ultMavenProjectBuilder.java:491) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > ojectBuilder.java:297) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( > DefaultMavenProjectBuilder.java:220) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMeta > dataSource.java:81) > ... 18 more > Caused by: > org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable > to download the artifact from any repository > org.apache.maven.plugins:maven-plugin-parent:2.0-beta-1-SNAPSHOT:pom > > from the specified remote repositories: > http://repo1.maven.org/maven2 > at > org.apache
Re: maven-scm-plugin fails
Memory: 1M/3M [INFO] -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: vrijdag 15 juli 2005 10:47 To: Maven Users List Subject: Re: maven-scm-plugin fails Can you retry? I upload the missing file. For run the checkout goal, you need to provide a connection url : m2 -DconnectionUrl=scm:svn: scm:checkout Emmanuel Van Steenberghe Mario (GFDI) wrote: Hi, We're trying to setup a build system using maven2, but the following error occurs while trying to checkout a project from cvs. It seems that the maven-scm-plugin cannot be downloaded from the maven repository due to a missing release file. When I try to manually download and install the plugin, there are some dependency problems. Is there anyone who knows how to get around this problem ? Thanks, Mario. - [EMAIL PROTECTED] ~/projects/jade2/scripts/gfdi/projects/fwk2/fwk_client $ m2 -e scm:checkout + Error stacktraces are turned on. [INFO] [INFO] Building Client Framework [INFO] [INFO] maven-scm-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-scm-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De faultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-scm-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveRelea seVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi nVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De faultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-scm-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveRelea seVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrie veFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolv eVersion(AbstractVersionTransformation.java:104) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transf ormForResolve(ReleaseArtifactTransformation.java:51) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resol
RE: maven-scm-plugin fails
Hi, The maven-scm-plugin is successfully downloaded now, but it seems to fail to find the maven-plugin-parent:2.0-beta-1-SNAPSHOT:pom dependency, which is not yet available from the http://repo1.maven.org/maven2 repository. Is there any other repository I could use in the meantime ? Thanks, Mario. Stack trace: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Error configuring plugin for execution of 'scm:checkout'. [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for execution of 'scm:checkout'. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:169) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:150) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.plugin.PluginConfigurationException: Cannot resolve plugin dependencies at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComp lete(DefaultPluginManager.java:616) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java:493) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:373) ... 15 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMeta dataSource.java:88) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComp lete(DefaultPluginManager.java:564) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find the POM in the repository at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:238) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:491) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:297) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:220) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMeta dataSource.java:81) ... 18 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to download the artifact from any repository org.apache.maven.plugins:maven-plugin-parent:2.0-beta-1-SNAPSHOT:pom from the specified remote repositories: http://repo1.maven.org/maven2 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:116) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:233) ... 22 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul tWagonManager.java:224) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:104) ... 23 more [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Fri Jul 15 11:52:23 CEST 2005 [INFO] Final Memory: 1M/3M [INFO] -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: vrijdag 15 juli 2005 10:47 To: Maven Users List Su
Re: maven-scm-plugin fails
Can you retry? I upload the missing file. For run the checkout goal, you need to provide a connection url : m2 -DconnectionUrl=scm:svn: scm:checkout Emmanuel Van Steenberghe Mario (GFDI) wrote: Hi, We're trying to setup a build system using maven2, but the following error occurs while trying to checkout a project from cvs. It seems that the maven-scm-plugin cannot be downloaded from the maven repository due to a missing release file. When I try to manually download and install the plugin, there are some dependency problems. Is there anyone who knows how to get around this problem ? Thanks, Mario. - [EMAIL PROTECTED] ~/projects/jade2/scripts/gfdi/projects/fwk2/fwk_client $ m2 -e scm:checkout + Error stacktraces are turned on. [INFO] [INFO] Building Client Framework [INFO] [INFO] maven-scm-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-scm-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-scm-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-scm-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:51) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:84) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.
maven-scm-plugin fails
Hi, We're trying to setup a build system using maven2, but the following error occurs while trying to checkout a project from cvs. It seems that the maven-scm-plugin cannot be downloaded from the maven repository due to a missing release file. When I try to manually download and install the plugin, there are some dependency problems. Is there anyone who knows how to get around this problem ? Thanks, Mario. - [EMAIL PROTECTED] ~/projects/jade2/scripts/gfdi/projects/fwk2/fwk_client $ m2 -e scm:checkout + Error stacktraces are turned on. [INFO] [INFO] Building Client Framework [INFO] [INFO] maven-scm-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-scm-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-scm-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-scm-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-scm-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:51) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:84) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:310) at org.apache.maven.artifact.manager.DefaultWago
