[maven-scm-plugin] Why does scm:update fail on a branch?
I am using the maven-scm-plugin with git. I find that the following succeeds: mvn -DscmVersion=abc -DscmVersionType=branch scm:bootstrap whereas the following, seemingly identical except for the command fails: mvn -X -DscmVersion=rpm -DscmVersionType=branch scm:update [ERROR] Provider message: [ERROR] The git-log command failed. [ERROR] Command output: [ERROR] fatal: ambiguous argument 'rpm': unknown revision or path not in the working tree. Use '--' to separate paths from revisions This looks like a bug in the plugin, but I don't really know. Why would the same specification fail for update but succeed for bootstrap? Other commands, such as scm:diff, scm:status, smc:checkout also work. Is this a bug and is there a workaround?
RE: [maven-scm-plugin] Why does scm:update fail on a branch?
The error message below should have been: [ERROR] fatal: ambiguous argument 'abc': unknown revision or path not in the working tree. - Original Message - Subject: [maven-scm-plugin] Why does scm:update fail on a branch? From: sco...@javactivity.org Date: 12/8/15 9:33 am To: users@maven.apache.org I am using the maven-scm-plugin with git. I find that the following succeeds: mvn -DscmVersion=abc -DscmVersionType=branch scm:bootstrap whereas the following, seemingly identical except for the command fails: mvn -X -DscmVersion=rpm -DscmVersionType=branch scm:update [ERROR] Provider message: [ERROR] The git-log command failed. [ERROR] Command output: [ERROR] fatal: ambiguous argument 'rpm': unknown revision or path not in the working tree. Use '--' to separate paths from revisions This looks like a bug in the plugin, but I don't really know. Why would the same specification fail for update but succeed for bootstrap? Other commands, such as scm:diff, scm:status, smc:checkout also work. Is this a bug and is there a workaround?
[ANN] Apache Maven SCM Plugin 1.9 Released
The Apache Maven team is pleased to announce the release of the Apache Maven SCM Plugin, version 1.9 The SCM Plugin offers vendor independent access to common scm commands by offering a set of command mappings for the configured scm. http://maven.apache.org/scm/maven-scm-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.9/version /plugin Release Notes - Maven SCM Plugin - Version 1.9 Bug [SCM-435] - can not work with local copy [SCM-503] - create a native Java GIT provider using JGit [SCM-650] - HgChangeLogConsumer generates phantom 'null' changeset at the end [SCM-681] - Git blame fails to report line authors on windows with core.autocrlf = true [SCM-702] - Incorrect documentation for parameter skip of goal check-local-modification of the plugin [SCM-705] - Git pushes tag ambigiously [SCM-709] - REGRESSION: git status doesn't work if repository root is not the working directory [SCM-733] - Bugfixes to mercurial changelog [SCM-737] - can't build CVS provider from source release zip file due to missing CVS test repository Improvement [SCM-487] - support --parents option for svn copy (tag commands) (svn 1.5 required) [SCM-565] - scm:validate should not fork the build [SCM-636] - Provide documentation about connection and developerConnection [SCM-736] - update plugin to use plugin-tools java 5 annotations New Feature [SCM-727] - integrate scm-provider based on jgit Enjoy, -The Apache Maven team -- Dominik Bartholdi
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 developerConnectionscm:git:g...@git.github.com: example/myproject.git/developerConnection /scm 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 javascript:;
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 andreas.gud...@gmail.com: 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 developerConnectionscm:git:g...@git.github.com: example/myproject.git/developerConnection /scm 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 javascript:;
Re: maven-scm-plugin example/help
Hi, If you want to release your project (i.e creating a tag then deploying the version) you must have a look at the release plugin which will will do the stuff for you. 2012/5/2 Billy Newman newman...@gmail.com: I was looking at possibly using the maven-scm-plugin to tag my releases in scm. A couple quick questions. Does anyone have a quick example of creating a tag from an scm trunk inside of a maven build, maybe a profile? What about only running the scm:tag goal if the version I am deploying is not a SNAPSHOT. IE I don't want to tag my snapshots, only releases deployed that are not SNAPSHOTs. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-scm-plugin example/help
Release plugin looks ok but thinking scm plugin might work a little better in my dev environment. Anyone know if the scm plugin can do what I want (see first post)? Thanks. On May 2, 2012, at 1:35 AM, Olivier Lamy ol...@apache.org wrote: Hi, If you want to release your project (i.e creating a tag then deploying the version) you must have a look at the release plugin which will will do the stuff for you. 2012/5/2 Billy Newman newman...@gmail.com: I was looking at possibly using the maven-scm-plugin to tag my releases in scm. A couple quick questions. Does anyone have a quick example of creating a tag from an scm trunk inside of a maven build, maybe a profile? What about only running the scm:tag goal if the version I am deploying is not a SNAPSHOT. IE I don't want to tag my snapshots, only releases deployed that are not SNAPSHOTs. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-scm-plugin example/help
The option could be having a profile which call the tag goal of the maven scm plugin Something like plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.7/version executions execution goals goaltag/goal /goals /execution /executions /plugin But honestly, I have never tested that :-) 2012/5/2 Billy Newman newman...@gmail.com: Release plugin looks ok but thinking scm plugin might work a little better in my dev environment. Anyone know if the scm plugin can do what I want (see first post)? Thanks. On May 2, 2012, at 1:35 AM, Olivier Lamy ol...@apache.org wrote: Hi, If you want to release your project (i.e creating a tag then deploying the version) you must have a look at the release plugin which will will do the stuff for you. 2012/5/2 Billy Newman newman...@gmail.com: I was looking at possibly using the maven-scm-plugin to tag my releases in scm. A couple quick questions. Does anyone have a quick example of creating a tag from an scm trunk inside of a maven build, maybe a profile? What about only running the scm:tag goal if the version I am deploying is not a SNAPSHOT. IE I don't want to tag my snapshots, only releases deployed that are not SNAPSHOTs. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-scm-plugin example/help
Thanks Olivier, I will give that a go. I would like to only tag if the version is not a SNAPSHOT, not sure if I can do that or not. I.E. pretty sure that I will not be able to control flow like that. Basically I have a jenkins job that runs my 'deploy'. We developers update the code they can just run the jenkins job to deploy a release to our local repository (SNAPSHOT or otherwise). I would like that job to automatically create a tag when a developer runs the job with a version that is not a SNAPSHOT. On Wed, May 2, 2012 at 10:26 AM, Olivier Lamy ol...@apache.org wrote: The option could be having a profile which call the tag goal of the maven scm plugin Something like plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.7/version executions execution goals goaltag/goal /goals /execution /executions /plugin But honestly, I have never tested that :-) 2012/5/2 Billy Newman newman...@gmail.com: Release plugin looks ok but thinking scm plugin might work a little better in my dev environment. Anyone know if the scm plugin can do what I want (see first post)? Thanks. On May 2, 2012, at 1:35 AM, Olivier Lamy ol...@apache.org wrote: Hi, If you want to release your project (i.e creating a tag then deploying the version) you must have a look at the release plugin which will will do the stuff for you. 2012/5/2 Billy Newman newman...@gmail.com: I was looking at possibly using the maven-scm-plugin to tag my releases in scm. A couple quick questions. Does anyone have a quick example of creating a tag from an scm trunk inside of a maven build, maybe a profile? What about only running the scm:tag goal if the version I am deploying is not a SNAPSHOT. IE I don't want to tag my snapshots, only releases deployed that are not SNAPSHOTs. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-scm-plugin example/help
I was looking at possibly using the maven-scm-plugin to tag my releases in scm. A couple quick questions. Does anyone have a quick example of creating a tag from an scm trunk inside of a maven build, maybe a profile? What about only running the scm:tag goal if the version I am deploying is not a SNAPSHOT. IE I don't want to tag my snapshots, only releases deployed that are not SNAPSHOTs. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven SCM plugin and CCRC
I'm having an issue getting the Maven SCM Plugin configured to use CCRC (ClearCase Remote Client v7.1.1). 1. What should the clearcase-settings.xml for Clear Case and location 2. What are the SCM setting SCM settings /SCM 3. Is there anything in the POM that is needed for configuration of the SCM plugin Thanks, Jeff CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: Maven SCM plugin and CCRC
I tried to get this to work but have up after getting no where for a few days. Chris On Oct 20, 2010, at 12:59, Lucas, Jeffrey A. jeffrey.lu...@anthem.com wrote: I'm having an issue getting the Maven SCM Plugin configured to use CCRC (ClearCase Remote Client v7.1.1). 1. What should the clearcase-settings.xml for Clear Case and location 2. What are the SCM setting SCM settings /SCM 3. Is there anything in the POM that is needed for configuration of the SCM plugin Thanks, Jeff CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven SCM plugin and CCRC
Hello, as far as I know, there is no scm implementation of CCRC for Maven. Clearcase Base/UCM are partially supported, it is far from perfect to be able to do the checkout/release roundtrip. I am guessing you read the documentation for the Clearcase (heavy client) implementation Cheers, Vincent 2010/10/20 Lucas, Jeffrey A. jeffrey.lu...@anthem.com I'm having an issue getting the Maven SCM Plugin configured to use CCRC (ClearCase Remote Client v7.1.1). 1. What should the clearcase-settings.xml for Clear Case and location 2. What are the SCM setting SCM settings /SCM 3. Is there anything in the POM that is needed for configuration of the SCM plugin Thanks, Jeff CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- Vincent
Re: Maven SCM plugin and CCRC
Some time ago I investigated this and found some mail from an IBM guy looking into this. Apparently they had some support customer asking. However, not too surprisingly he didn't report back... /Anders On Wed, Oct 20, 2010 at 20:04, Vincent Latombe vincent.lato...@gmail.comwrote: Hello, as far as I know, there is no scm implementation of CCRC for Maven. Clearcase Base/UCM are partially supported, it is far from perfect to be able to do the checkout/release roundtrip. I am guessing you read the documentation for the Clearcase (heavy client) implementation Cheers, Vincent 2010/10/20 Lucas, Jeffrey A. jeffrey.lu...@anthem.com I'm having an issue getting the Maven SCM Plugin configured to use CCRC (ClearCase Remote Client v7.1.1). 1. What should the clearcase-settings.xml for Clear Case and location 2. What are the SCM setting SCM settings /SCM 3. Is there anything in the POM that is needed for configuration of the SCM plugin Thanks, Jeff CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- Vincent
Re: maven scm plugin: accurev scm provider
Thanks! can you give me an example of how the connectionUrl should look like with accurev? E. On Fri, Apr 23, 2010 at 11:04 AM, Grant Gardner gdgard...@optusnet.com.auwrote: If you want to use the new version, take the code attached to issue, bump parent version to 1.3 and change the artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Eyal Edri
Re: maven scm plugin: accurev scm provider
the site documentation for that version is available here http://lastweekend.com.au/projects/maven-scm-provider-accurev/site/ On Wed, 28 Apr 2010 14:11:07 +0300, eyal edri eyal.e...@gmail.com wrote: Thanks! can you give me an example of how the connectionUrl should look like with accurev? E. On Fri, Apr 23, 2010 at 11:04 AM, Grant Gardner gr...@lastweekend.com.auwrote: If you want to use the new version, take the code attached to issue, bump parent version to 1.3 and change the artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven scm plugin: accurev scm provider
If you want to use the new version, take the code attached to issue, bump parent version to 1.3 and change the artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven scm plugin: accurev scm provider
Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. -- Eyal Edri
how to use maven-scm-plugin to checkout a CVS tag
Hi every one,
I have a need to checkout a CVS tag at build time, and have no idea
how to configure the tag. Any advice is greatly appreciated
here is my configuration
configuration
connectionUrl${cvsroot}:mymodule/connectionUrl
/configuration
Thanks
-Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: how to use maven-scm-plugin to checkout a CVS tag
never mind,
The secret is in scmVersionType adn scmVervsion configuration
On Thu, Mar 18, 2010 at 1:02 AM, Dan Tran dant...@gmail.com wrote:
Hi every one,
I have a need to checkout a CVS tag at build time, and have no idea
how to configure the tag. Any advice is greatly appreciated
here is my configuration
configuration
connectionUrl${cvsroot}:mymodule/connectionUrl
/configuration
Thanks
-Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use maven-scm-plugin with subversion and without a command line
On Fri, Jul 10, 2009 at 8:19 AM, Benson Marguliesbimargul...@gmail.com wrote: The doc for the svn piece of the scm-plugin has several tantalizing hints that suggest that there is some way to use an API to svn instead of running commands. Since I've got some people on Windows with cygwin, where the command line is not working, I'd like to try that out. Could someone please post the recipe? I'd be willing to type it into Confluence if I just knew what it was. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org You probably want to join the subversion users mailing list [information and a link to the list archives over at http://subversion.tigris.org ] Subversion itself exposes a high level API [C calling conventions] this is what the svn command line client, and the 'javahl' library use. There is also at least one pure java svn client library [svnkit] and it is likely that the scm plugin can use either the svnkit or the javahl libraries, as they are designed to maintain compatibility. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use maven-scm-plugin with subversion and without a command line
We didn't understand each other, but I can now post the answer for the record. If you look at http://maven.apache.org/scm/plugins/update-mojo.html#privateKey, you will see a reference to 'javasvn'. It turns out that this is a separate plugin: http://code.google.com/p/maven-scm-provider-svnjava/ On Mon, Jul 13, 2009 at 2:38 PM, Dave Levittdave.lev...@gmail.com wrote: On Fri, Jul 10, 2009 at 8:19 AM, Benson Marguliesbimargul...@gmail.com wrote: The doc for the svn piece of the scm-plugin has several tantalizing hints that suggest that there is some way to use an API to svn instead of running commands. Since I've got some people on Windows with cygwin, where the command line is not working, I'd like to try that out. Could someone please post the recipe? I'd be willing to type it into Confluence if I just knew what it was. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org You probably want to join the subversion users mailing list [information and a link to the list archives over at http://subversion.tigris.org ] Subversion itself exposes a high level API [C calling conventions] this is what the svn command line client, and the 'javahl' library use. There is also at least one pure java svn client library [svnkit] and it is likely that the scm plugin can use either the svnkit or the javahl libraries, as they are designed to maintain compatibility. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to use maven-scm-plugin with subversion and without a command line
The doc for the svn piece of the scm-plugin has several tantalizing hints that suggest that there is some way to use an API to svn instead of running commands. Since I've got some people on Windows with cygwin, where the command line is not working, I'd like to try that out. Could someone please post the recipe? I'd be willing to type it into Confluence if I just knew what it was. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-scm-plugin
Can I use this plugin for the following purpose?
Project A build has a folder in its directory structure that holds assets
from a different svn location/project (project B) that I want to include in
my build. During my build before the compile phase I would like to use this
plugin to do an svn update and get the latest file from Project B and store
it in this folder.
I am setting up my pom like this
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.2/version
configuration
usernameme/username
password*/password
basedir${tomcat.home}/webapps/pub/swf/basedir
connectionTypeconnection/connectionType
connectionUrlscm:svn:https://projectB/trunk/bin/connectionUrl
/configuration
executions
execution
idgetting_updated_swf/id
phaseprocess-resources/phase
goals
goalupdate/goal
/goals
/execution
/executions
/plugin
My build is throwing errors and I am confused as to why:
[INFO] [scm:update]
[INFO] Executing: cmd.exe /X /C svn --username me --password *
--non-interactive update C:\Program Files\Apache Software Foundation\Tomcat
6.0\webapps\pub\swf
[INFO] Working directory: C:\Program Files\Apache Software Foundation\Tomcat
6.0\webapps\pub\swf
[ERROR]
While building project:
Reason: Cannot run update command :
The working directory is the correct directory i want to update but the one
in the update command is not the connectionURL.
Is this possible?
Can anyone help me work through the error message?
Thanks,
Barry
Re: Maven-scm-plugin define -Dmaven.scm.provider.cvs.implementation in pom?
2009/3/16 Eric B. ebe...@hotmail.com: I've been trying to figure out if there is a way to specify the maven.scm.provider.cvs.implementation in the pom or in a profile, but haven't been able to find anything. I know I can specify -Dmaven.scm.provider.cvs.implementation=cvs_native on the command line, but would like to do it from the pom. I did find http://jira.codehaus.org/browse/SCM-303, but I am running scm 2.0-beta-8 and I still cant seem to get it to work. I can only confirm that it doesn't work for me either. I tried it with putting the property in an always active profile in my settings.xml. I am running Maven 2.0.9 on Windows 2000SP4 Ringo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven-scm-plugin define -Dmaven.scm.provider.cvs.implementation in pom?
Hi, I've been trying to figure out if there is a way to specify the maven.scm.provider.cvs.implementation in the pom or in a profile, but haven't been able to find anything. I know I can specify -Dmaven.scm.provider.cvs.implementation=cvs_native on the command line, but would like to do it from the pom. I did find http://jira.codehaus.org/browse/SCM-303, but I am running scm 2.0-beta-8 and I still cant seem to get it to work. Does anyone have any ideas? Thanks, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
CI checkout on floating tag, then using maven-scm-plugin to update pom.xml to latest?
Hello, I am trying to use Hudson to perform automated software releases based on a floating CVS tag. When developers move the floating tag on the sources, they indicate that the tagged code can go in a next build. Hudson then checks out the code and executes a release:prepare. Problem now is that the changes to pom.xml (done by the release plugin) can't be checked in since the CVS information indicates that the version retrieved is a sticky tag (although usually it is the latest version). To get around this, I want to use maven-scm-plugin (in the validate phase of my Maven run) to update pom.xml to the latest version. However, I tried several goals (update, checkout, export) but pom.xml remains the the version based on the tag. Can anyone tell me how to update pom.xml to the latest version coming from the branch configured in the connectionUrl/developerConnectionUrl info from the POM? Also, my experiments so far seem to indicate that includes/excludes configuration is ignored in the goals tried. Known bug? Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes �ventuelles peuvent contenir des informations confidentielles et/ou prot�g�es par des droits de propri�t� intellectuelle. Ce message est adress� exclusivement � son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou compl�te sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez re�u ce message par erreur, veuillez pr�venir l'exp�diteur du message et en d�truire le contenu. *
Using a previous version of release and/or the maven SCM plugin
I seem to be stumbling hard over a few bugs that have already been identified, reported, and it looks like patches are available - http://jira.codehaus.org/browse/SCM-415. Almost all of my environment is using token based authentication with Perforce, so I thought I'd just push back to the previous version of the Maven SCM plugin (1.0) until a fix is formally released. Unfortunately, I don't seem to be quite grokking how to do that. I've tried adding the following into my project POM stanza, but it's not terribly happy about it: build plugins groupIdorg.apache.maven.release/groupId artifactIdmaven-release/artifactId version4/version /plugins ... /build I've also tried just aiming it at the SCM plugin: build plugins groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm/artifactId version1.0/version /plugins ... /build I've got 1.0 working fine on another system, but I'm at a complete loss on how to specify that I want to use an earlier version of the SCM or release plugin (and it's dependencies) until the kinks get worked out of this latest version. Can anyone enlighten me? -joe Joseph Heck Disney Interactive Media Group - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using a previous version of release and/or the maven SCM plugin
Ah, nevermind - After I asked, I tried a few more variations, finally actually LOOKING at the super-pom to find out where it was supposed to go. GFor the reference archives, my solution is: build ... pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-7/version /plugin /plugins /pluginManagement ... /build -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Heck, Joe Sent: Wednesday, November 05, 2008 3:27 PM To: Maven Users List Cc: Jackson, Brian R Subject: Using a previous version of release and/or the maven SCM plugin I seem to be stumbling hard over a few bugs that have already been identified, reported, and it looks like patches are available - http://jira.codehaus.org/browse/SCM-415. Almost all of my environment is using token based authentication with Perforce, so I thought I'd just push back to the previous version of the Maven SCM plugin (1.0) until a fix is formally released. Unfortunately, I don't seem to be quite grokking how to do that. I've tried adding the following into my project POM stanza, but it's not terribly happy about it: build plugins groupIdorg.apache.maven.release/groupId artifactIdmaven-release/artifactId version4/version /plugins ... /build I've also tried just aiming it at the SCM plugin: build plugins groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm/artifactId version1.0/version /plugins ... /build I've got 1.0 working fine on another system, but I'm at a complete loss on how to specify that I want to use an earlier version of the SCM or release plugin (and it's dependencies) until the kinks get worked out of this latest version. Can anyone enlighten me? -joe Joseph Heck Disney Interactive Media Group - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can use Maven SCM plugin API to Move some versiond SVN File from one folde to another?
I find a pure java SVN client here:http://svnkit.com/ and I can use mvn move,mvn commit.in java client. 2008/10/20 sean.chen(陈思淼) [EMAIL PROTECTED] I have some project have bad structure and I want to modify it to SVN fold structure, If do it manually, i will be time consuming and easily make mistakes. I want to ask ,can Maven SCM API Help me do this kind of things?
Can use Maven SCM plugin API to Move some versiond SVN File from one folde to another?
I have some project have bad structure and I want to modify it to SVN fold structure, If do it manually, i will be time consuming and easily make mistakes. I want to ask ,can Maven SCM API Help me do this kind of things?
Maven2, maven-scm-plugin, svn, interactive mode
Hi all, I'm trying to use the scm plugin to bootstrap a project from a SVN repository. Using: mvn scm:bootstrap -DconnectionUrl=scm:svn:$SCM_PATH -DscmVersion=$SCM_REVISION -DscmVersionType=$SCM_REVISION_TYPE -Dusername=$SCM_USER -Dpassword=$SCM_PWD -Dgoals=install All works well However, the end user of this script would like SVN to prompt for username, password, and certificate trusting... Per the svn scm provider plugin, I created a config file with useNonInteractivefalse/, which works: maven calls SVN without the -non-interactive option. However, it seems that maven doesn't pipe the svn command's inputs and outputs: On windows (xp sp2), it just hangs (no cpu), as if it were waiting for input, but there is no message On Solaris (5.6, sh), I do get a request for a password, based on the current user (although this isn't the user I want to use, this seems to be a logical svn behaviour), but doesn't react to input. Has anyone had any success using the interactive mode for svn with the scm plugin? Also, are there any known plans on making the interactive mode available via a -D switch? [Based on my reading of maven-scm-provider-svn-commons-1.1-sources maven-scm-provider-svnexe-1.1-sources, there is nothing in that direction so far] My current workaround is to prompt for username password in the script, and pass these to maven, using the non-interactive default mode, although this does not cater for certificate problems. Thanks in advance, Jonathan Winterflood Capgemini Ouest - Agence de Brest
Custom locations with maven-scm-plugin (SVN)
Hi everyone, I am trying to structure a complex Maven structure for a multi-module-multi-projects delivery chain, based on a set of Subversion repositories. I have been browsing around the maven-scm-plugin configuration and usage, but could not solve this simple problem: - how to define a custom checkout location ? I don't (necessarily) want the pom.xml to be located in the Subversion repository configured under the scm, nor do I want this repository to be checked-out right under the current working directory... - IF this is done in the $user.home/.scm/???-settings.xml, how can I instruct Maven to actually look into another place for this file ? (i.e. the purpose is to have different checkout locations for different projects) Any help appreciated! Thanks Olivier -- *Olivier Gies* *Delivery Manager Customs Tax Software Engineering Center Bull, Architect of an Open World ^TM Phone: +86 (10) 65978001 - Ext 555 * *www.bull.com http://www.bull.com/* *This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.*
maven-scm-plugin connectionUrl scm:svn:file:///
I am trying to use the SCM plugin to commit a file back to SVN after the build is complete. The build takes place on our CI server, which causes a buildnumber to increment, which we need stored in svn. So while our SVN repo is remote to my development box, it is actually local to the CI server (svn and CI on the same box) For me to hitup svn, I have a username and password and use svn+ssh, but for a commit from the same box, we have the scm connection url set to scm:file. Everything goes well until the commit after the build where we are getting [INFO] [scm:checkin] [INFO] Executing: svn --username tomcat --password * --non-interactive commit --file /tmp/maven-scm-1772422631.commit [INFO] Working directory: /usr/local/.../hudson/jobs/projectname/workspace/projectname [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: Commit failed (details follow): svn: Can't create directory '/usr/local/.../svnrepos/projectname/db/transactions/205-1.txn': Permission denied I can scm:update, scm:changelog, or whatever else I want, but I can't checkin because of this permission denied. My configuration is plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-rc1/version configuration connectionTypeconnection/connectionType includesbuildNumber.properies/includes message automated build, incremented buildnumber /message usernamemyusername/username passwordmypassword/password connectionUrl scm:svn:file:///usr/local/.../svnrepos/project /connectionUrl /configuration executions execution idchecking_incremented_buildnumber/id phasepost-integration-test/phase goals goalcheckin/goal /goals /execution /executions /plugin My question is: is the username and password ignored when the connection is scm:file ?? Another question I suppose is does the error that is occurring look like its a result of a username and password being invalid or not supplied? Thanks. -- View this message in context: http://n2.nabble.com/maven-scm-plugin-connectionUrl-scm%3Asvn%3Afile%3Atp681339p681339.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-scm-plugin connectionUrl scm:svn:file:///
I don't think SVN is able to use the username and password for filesystem changes since that won't change the active system user. You should have to run the command as a user that has permission to write to the file repository, or use a different front end like SVN. I don't think this is related to the Maven plugins at all, or that there is anything they can do to help, sorry. Cheers, Brett 2008/8/9 mikenereson [EMAIL PROTECTED]: I am trying to use the SCM plugin to commit a file back to SVN after the build is complete. The build takes place on our CI server, which causes a buildnumber to increment, which we need stored in svn. So while our SVN repo is remote to my development box, it is actually local to the CI server (svn and CI on the same box) For me to hitup svn, I have a username and password and use svn+ssh, but for a commit from the same box, we have the scm connection url set to scm:file. Everything goes well until the commit after the build where we are getting [INFO] [scm:checkin] [INFO] Executing: svn --username tomcat --password * --non-interactive commit --file /tmp/maven-scm-1772422631.commit [INFO] Working directory: /usr/local/.../hudson/jobs/projectname/workspace/projectname [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: Commit failed (details follow): svn: Can't create directory '/usr/local/.../svnrepos/projectname/db/transactions/205-1.txn': Permission denied I can scm:update, scm:changelog, or whatever else I want, but I can't checkin because of this permission denied. My configuration is plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-rc1/version configuration connectionTypeconnection/connectionType includesbuildNumber.properies/includes message automated build, incremented buildnumber /message usernamemyusername/username passwordmypassword/password connectionUrl scm:svn:file:///usr/local/.../svnrepos/project /connectionUrl /configuration executions execution idchecking_incremented_buildnumber/id phasepost-integration-test/phase goals goalcheckin/goal /goals /execution /executions /plugin My question is: is the username and password ignored when the connection is scm:file ?? Another question I suppose is does the error that is occurring look like its a result of a username and password being invalid or not supplied? Thanks. -- View this message in context: http://n2.nabble.com/maven-scm-plugin-connectionUrl-scm%3Asvn%3Afile%3Atp681339p681339.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-scm-plugin : how to ignore target directory while checkin
Hi, I am using maven-scm-plugin to checkin the sources while deploy phase. We only manage the real source in SVN and don't want to add target directory to scm. So, how do I ignore the target directory while checkin. If I run mvn scm:checkin on clean directory - all is Ok. If I run mvn clean deploy, I get: -- [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: Commit failed (details follow): svn: Directory 'C:\Dev\MyPath\Core\target\.svn' containing working copy admin area is missing -- Configuration: -- plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0/version configuration connectionTypeconnection/connectionType messagemy message/message /configuration executions execution phasedeploy/phase goals goalcheckin/goal /goals /execution /executions /plugin -- P.S. I tryed to add excludestarget/excludes but it doesn't help. Regards, Uri. -- View this message in context: http://www.nabble.com/maven-scm-plugin-%3A-how-to-ignore-target-directory-while-checkin-tf4935595s177.html#a14127254 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven-Scm Plugin with CVS: Wrong password exception
I am trying to use maven scm plugin to checkout some files from CVS but I always get a Wrong Password exception. Here is what I am tying: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0/version executions execution idcheckout/id phasepackage/phase goals goalcheckout/goal /goals configuration connectionUrlscm:cvs:pserver:[EMAIL PROTECTED]:/home/cvs/idev:module/connectionUrl passwordabc123/password /configuration /execution /executions /plugin I am sure that password is correct but what can be wrong then? Regards, Usman
Using maven-scm-plugin
Hi
We are using maven2.0.6 and SVN in our project. Now the requirement is
we need to create a list of all the developers who have cheed-in the
files in the SVN in a day. And this report will be generated each n
every day by EOD. Now as it is given on apache site that
maven-scm-plugin is used for the same purpose. So what I have done is
created 1 separate project and the conent inside that is given below.
And then run the project as : mvn scm:changelog . After this the build
result that I could get is BuildSuccessful but there is no target
directory where I could see the report. So could anyone please tell me
what I am doing wrong.
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.bskyb.nop.foundation/groupId
artifactIdskyreport/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
nameskyreport/name
urlhttp://maven.apache.org/url
repositories
repository
idcentral/id
nameMyCompany Central Repository/name
urlhttp://10.210.17.131:/repository/url
snapshots
enabledtrue/enabled
/snapshots
releases
enabledtrue/enabled
/releases
/repository
/repositories
pluginRepositories
pluginRepository
idapache.snapshots/id
urlhttp://people.apache.org/repo/m2-snapshot-repository//url
releases
enabledfalse/enabled
/releases
/pluginRepository
pluginRepository
idcopy/id
urlhttp://quebbemann.kicks-ass.net/maven2/repository//url
/pluginRepository
pluginRepository
idapache/id
urlhttp://repo1.maven.org/maven2//url
/pluginRepository
/pluginRepositories
ciManagement
systemContinuum/system
urlhttp://localhost:8080/continuum//url
notifiers
notifier
typemail/type
configuration
address[EMAIL PROTECTED]/address
/configuration
/notifier
/notifiers
/ciManagement
scm
connectionscm:svn:https://scm1.del.rs.sapient.com/svn/repos/sky_founda
tion_and_news/sky_joint_fusion/trunk/Development/Code/javasource//conne
ction
developerConnectionscm:svn:https://scm1.del.rs.sapient.com/svn/repos/s
ky_foundation_and_news/sky_joint_fusion/trunk/Development/Code/javasourc
e/developerConnection
urlhttps://scm1.del.rs.sapient.com/svn/repos/sky_foundation_and_news/s
ky_joint_fusion/trunk/Development/Code/javasource//url
/scm
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.0/version
/plugin
/plugins
/reporting
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.0/version
configuration
startDate2007-10-29/startDate
endDate2007-10-29/endDate
/configuration
/plugin
/plugins
/build
distributionManagement
repository
idinternal/id
nameInternal Release Repository/name
url${mvn2.repository}/[EMAIL PROTECTED]/url
/repository
snapshotRepository
idinternal-snapshots/id
nameInternal Snapshot Repository/name
url${mvn2.repository}/[EMAIL PROTECTED]/url
/snapshotRepository
!--site
idwebsite/id
url
file:///webbuild/apps/ci/sites/${pom.artifactId}
/url
/site--
/distributionManagement
/project
Regards
Vishal
Re: Using maven-scm-plugin
scm:changelog print the output on the command line and not to a file.
Maybe the changelog plugin would be better for you:
http://maven.apache.org/plugins/maven-changelog-plugin/
Emmanuel
Vishal Pahwa a écrit :
Hi
We are using maven2.0.6 and SVN in our project. Now the requirement is
we need to create a list of all the developers who have cheed-in the
files in the SVN in a day. And this report will be generated each n
every day by EOD. Now as it is given on apache site that
maven-scm-plugin is used for the same purpose. So what I have done is
created 1 separate project and the conent inside that is given below.
And then run the project as : mvn scm:changelog . After this the build
result that I could get is BuildSuccessful but there is no target
directory where I could see the report. So could anyone please tell me
what I am doing wrong.
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.bskyb.nop.foundation/groupId
artifactIdskyreport/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
nameskyreport/name
urlhttp://maven.apache.org/url
repositories
repository
idcentral/id
nameMyCompany Central Repository/name
urlhttp://10.210.17.131:/repository/url
snapshots
enabledtrue/enabled
/snapshots
releases
enabledtrue/enabled
/releases
/repository
/repositories
pluginRepositories
pluginRepository
idapache.snapshots/id
urlhttp://people.apache.org/repo/m2-snapshot-repository//url
releases
enabledfalse/enabled
/releases
/pluginRepository
pluginRepository
idcopy/id
urlhttp://quebbemann.kicks-ass.net/maven2/repository//url
/pluginRepository
pluginRepository
idapache/id
urlhttp://repo1.maven.org/maven2//url
/pluginRepository
/pluginRepositories
ciManagement
systemContinuum/system
urlhttp://localhost:8080/continuum//url
notifiers
notifier
typemail/type
configuration
address[EMAIL PROTECTED]/address
/configuration
/notifier
/notifiers
/ciManagement
scm
connectionscm:svn:https://scm1.del.rs.sapient.com/svn/repos/sky_founda
tion_and_news/sky_joint_fusion/trunk/Development/Code/javasource//conne
ction
developerConnectionscm:svn:https://scm1.del.rs.sapient.com/svn/repos/s
ky_foundation_and_news/sky_joint_fusion/trunk/Development/Code/javasourc
e/developerConnection
urlhttps://scm1.del.rs.sapient.com/svn/repos/sky_foundation_and_news/s
ky_joint_fusion/trunk/Development/Code/javasource//url
/scm
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.0/version
/plugin
/plugins
/reporting
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.0/version
configuration
startDate2007-10-29/startDate
endDate2007-10-29/endDate
/configuration
/plugin
/plugins
/build
distributionManagement
repository
idinternal/id
nameInternal Release Repository/name
url${mvn2.repository}/[EMAIL PROTECTED]/url
/repository
snapshotRepository
idinternal-snapshots/id
nameInternal Snapshot Repository/name
url${mvn2.repository}/[EMAIL PROTECTED]/url
/snapshotRepository
!--site
idwebsite/id
url
file:///webbuild/apps/ci/sites/${pom.artifactId}
/url
/site--
/distributionManagement
/project
Regards
Vishal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven-scm-plugin sometimes fails to checkin file
I have the plugin configured to checkin a built ear file into CVS.The
configuration is shown below :
execution
idcheckin-ear/id
phasepost-integration-test/phase
configuration
connectionUrlscm:cvs:pserver:jeffm:[EMAIL
PROTECTED]:/var/lib/cvsroot:Eportal/depl/eportal-releases/eportal/dev3/connectionUrl
includes**/*.ear/includes
messageMaven ear file commit/message
workingDirectorytarget/checkout/workingDirectory
/configuration
goals
goalcheckin/goal
/goals
/execution
However , sometimes the checkin does not go through , even though
there's no error message.I can see from browsing the repository that
the commit didnt happen since the version of the ear file in CVS
remains the same, as well as the last commit date.The output I get is
:
[INFO] [scm:checkin {execution: checkin-ear}]
[DEBUG] cvsRoot: :pserver:[EMAIL PROTECTED]:2401/var/lib/cvsroot
[DEBUG] passFile: D:\Documents and Settings\jeffm\.cvspass
[DEBUG] cvsroot :pserver:[EMAIL PROTECTED]:2401/var/lib/cvsroot already exis
t in D:\Documents and Settings\jeffm\.cvspass. SKIPPED.
[INFO] Executing: cvs -z3 -f -q commit -R -F C:\DOCUME~1\jeffm\LOCALS~1\Temp\s
cm-commit-message49260.txt
[INFO] Working directory: D:\CONTINUUM-BUILDS\continuum\working-directory\86\epo
rtal-functional-tests\target\checkout
[DEBUG] Executing CVS command: commit -F C:\DOCUME~1\jeffm\LOCALS~1\Temp\scm-c
ommit-message49260.txt
Sometimes it works.What could be causing this?
--
Don't take the name of root in vain.
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-scm-plugin verbose
On 6/13/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: you can use the mvn -X parameter. Well , I'm using Continuum to launch the maven builds Don't take the name of root in vain. Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-scm-plugin verbose
On 6/14/07, Jeff Mutonho [EMAIL PROTECTED] wrote: On 6/13/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: you can use the mvn -X parameter. Well , I'm using Continuum to launch the maven builds Hi Jeff, So? Add the -X switch to the arguments list of your continuum build definition. Cheers Jo
maven-scm-plugin verbose
Is there some undocumented feature/way to make maven-scm-plugin more verbose during checkout and checkin? -- Don't take the name of root in vain. Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-scm-plugin verbose
you can use the mvn -X parameter. Jeff Mutonho a écrit : Is there some undocumented feature/way to make maven-scm-plugin more verbose during checkout and checkin? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem using wagon-scm and maven-scm-plugin together
Hello all, I'm having a problem trying to use the wagon-scm plugin. I have added the following to my pom (in this case, a parent pom): build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-2-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-manager-plexus/artifactId version1.0-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-svnexe/artifactId version1.0-SNAPSHOT/version /extension /extensions /build However, when I now try to build my project from the child pom, an execution which uses the scm checkout goal stops working. The execution is: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-SNAPSHOT/version executions execution phasevalidate/phase configuration checkoutDirectorySOME_DIR/checkoutDirectory connectionUrlscm:svn:http://SOMEHOST/etc/connectionUrl skipCheckoutIfExistsfalse/skipCheckoutIfExists /configuration goals goalcheckout/goal /goals /execution /executions /plugin The error I get is: [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-scm-plugin:1.0-SNAPSHOT:checkout': Unable to find the mojo 'org.apache. maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' in the plugin 'org.apache.ma ven.plugins:maven-scm-plugin' Note that this execution starts working again if I comment out the extensions element from the parent pom, and the wagon-scm plugin works if I comment out the maven-scm-plugin execution. Also, the problem arises even though the wagon-scm plugin is not (to my knowledge) being used. I have also tried various versions of wagon-scm and maven-scm-plugin, but the same problem always occurs. I have attached the full stack trace of the error. Thanks for any help, Dean. [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-scm-plugin:1.0-SNAPSHOT:checkout': Unable to find the mojo 'org.apach e.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' in the plugin 'org.apach e.maven.plugins:maven-scm-plugin' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the pl ugin manager executing goal 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPS HOT:checkout': Unable to find the mojo 'org.apache.maven.plugins:maven-scm-plugi n:1.0-SNAPSHOT:checkout' in the plugin 'org.apache.maven.plugins:maven-scm-plugi n' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:538) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mo jo 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' in the plug in 'org.apache.maven.plugins:maven-scm-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:533) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more Caused
Re: Problem using wagon-scm and maven-scm-plugin together
For anyone else having this problem, it seems to be fixed in maven-2.0.5-SNAPSHOT. Best wishes, Dean. On 1/3/07, Dean Jones [EMAIL PROTECTED] wrote: Hello all, I'm having a problem trying to use the wagon-scm plugin. I have added the following to my pom (in this case, a parent pom): build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-2-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-manager-plexus/artifactId version1.0-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-svnexe/artifactId version1.0-SNAPSHOT/version /extension /extensions /build However, when I now try to build my project from the child pom, an execution which uses the scm checkout goal stops working. The execution is: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-SNAPSHOT/version executions execution phasevalidate/phase configuration checkoutDirectorySOME_DIR/checkoutDirectory connectionUrlscm:svn:http://SOMEHOST/etc/connectionUrl skipCheckoutIfExistsfalse/skipCheckoutIfExists /configuration goals goalcheckout/goal /goals /execution /executions /plugin The error I get is: [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-scm-plugin:1.0-SNAPSHOT:checkout': Unable to find the mojo 'org.apache. maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' in the plugin 'org.apache.ma ven.plugins:maven-scm-plugin' Note that this execution starts working again if I comment out the extensions element from the parent pom, and the wagon-scm plugin works if I comment out the maven-scm-plugin execution. Also, the problem arises even though the wagon-scm plugin is not (to my knowledge) being used. I have also tried various versions of wagon-scm and maven-scm-plugin, but the same problem always occurs. I have attached the full stack trace of the error. Thanks for any help, Dean. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 with VSS: Has maven scm plugin implemented scm:checkout for VSS?
scm:checkout is supported for VSS but not in the release version, only in our svn. We'll release a new version in few days. Emmanuel [EMAIL PROTECTED] a écrit : try command line mvn scm:checkout following error found, Embedded error: No such command 'checkout' Anyone can help? Thanks! Regards, Joy IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 with VSS: Has maven scm plugin implemented scm:checkout for VSS?
try command line mvn scm:checkout following error found, Embedded error: No such command 'checkout' Anyone can help? Thanks! Regards, Joy IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com.
Failed maven-scm-plugin: Check in
I'm trying to check in an ear file into CVS .When I run the command 'mvn scm:checkin' , the check in is failing with the following message : [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT :checkin' -- [DEBUG] (f) basedir = D:\MAVEN-WORK\eportal-ear [DEBUG] (f) connectionType = developerConnection [DEBUG] (s) connectionUrl = scm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/ lib/cvsroot:pragmaticusEportal/dev/eportal-ear [DEBUG] (f) developerConnectionUrl = scm:cvs:pserver:mutonj:[EMAIL PROTECTED] .14:/var/lib/cvsroot:pragmaticusEportal/dev/eportal-ear [DEBUG] (f) includes = **/*.ear [DEBUG] (f) message = Ear file test commit [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [scm:checkin] [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/var/lib/cvsroot -q commit -R -F C:\DOCUME~1\mutonhj\LOCALS~1\Temp\scm-commit-message61509.txt [INFO] Working directory: D:\MAVEN-WORK\eportal-ear [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: [ERROR] cvs commit: in directory .: cvs [commit aborted]: there is no version here; run 'cvs checkout' first [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Command failed.The cvs command failed. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.The cvs c ommand failed. My plugin is configured as shown below : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-SNAPSHOT/version configuration connectionUrlscm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/lib/cvsroot:pragmaticusEportal/dev/eportal-ear//connectionUrl includes**/*.ear/includes messageEar file test commit/message /configuration goals goalcheckin/goal /goals /plugin I've googled for the error and the only explanation I can find seems to be pointing to the idea that I'm trying to add the ear file to a non-existent sub-directory , which isn't the case because pragmaticusEportal/dev/eportal-ear/ is indeed existent. -- Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failed maven-scm-plugin: Check in
You can't commit a file if you aren't in a working copy directory. Emmanuel Jeff Mutonho a écrit : I'm trying to check in an ear file into CVS .When I run the command 'mvn scm:checkin' , the check in is failing with the following message : [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT :checkin' -- [DEBUG] (f) basedir = D:\MAVEN-WORK\eportal-ear [DEBUG] (f) connectionType = developerConnection [DEBUG] (s) connectionUrl = scm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/ lib/cvsroot:pragmaticusEportal/dev/eportal-ear [DEBUG] (f) developerConnectionUrl = scm:cvs:pserver:mutonj:[EMAIL PROTECTED] .14:/var/lib/cvsroot:pragmaticusEportal/dev/eportal-ear [DEBUG] (f) includes = **/*.ear [DEBUG] (f) message = Ear file test commit [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [scm:checkin] [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/var/lib/cvsroot -q commit -R -F C:\DOCUME~1\mutonhj\LOCALS~1\Temp\scm-commit-message61509.txt [INFO] Working directory: D:\MAVEN-WORK\eportal-ear [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: [ERROR] cvs commit: in directory .: cvs [commit aborted]: there is no version here; run 'cvs checkout' first [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Command failed.The cvs command failed. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.The cvs c ommand failed. My plugin is configured as shown below : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-SNAPSHOT/version configuration connectionUrlscm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/lib/cvsroot:pragmaticusEportal/dev/eportal-ear//connectionUrl includes**/*.ear/includes messageEar file test commit/message /configuration goals goalcheckin/goal /goals /plugin I've googled for the error and the only explanation I can find seems to be pointing to the idea that I'm trying to add the ear file to a non-existent sub-directory , which isn't the case because pragmaticusEportal/dev/eportal-ear/ is indeed existent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failed maven-scm-plugin: Check in
On 11/27/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You can't commit a file if you aren't in a working copy directory. Emmanuel Thanks Emmanuel.The log says [INFO] Working directory: D:\MAVEN-WORK\eportal-ear .Do you mean I should run this from the directory where the actual ear file is located (which in my case is D:\MAVEN-WORK\eportal-ear\target) ? Is that what you mean by working copy directory. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failed maven-scm-plugin: Check in
A working copy directory is the directory where you done the checkout. For CVS, it must contains a CVS directory. Emmanuel Jeff Mutonho a écrit : On 11/27/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You can't commit a file if you aren't in a working copy directory. Emmanuel Thanks Emmanuel.The log says [INFO] Working directory: D:\MAVEN-WORK\eportal-ear .Do you mean I should run this from the directory where the actual ear file is located (which in my case is D:\MAVEN-WORK\eportal-ear\target) ? Is that what you mean by working copy directory. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failed maven-scm-plugin: Check in
On 11/27/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: A working copy directory is the directory where you done the checkout. For CVS, it must contains a CVS directory. Emmanuel Thanks.Seems sorted now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-scm-plugin: Check in
I've got a requirement to use maven to check in a war file into some CVS repository.I know the maven-scm-plugin has a 'checkin' goal , but I'm not sure how its used.May someone show me an example of how I can use the 'checkin' goal to put a war file into a CVS repository. Thanx -- Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-scm-plugin: Check in
since scm:checkin doc is available, could you give it a try ? On 11/23/06, Jeff Mutonho [EMAIL PROTECTED] wrote: I've got a requirement to use maven to check in a war file into some CVS repository.I know the maven-scm-plugin has a 'checkin' goal , but I'm not sure how its used.May someone show me an example of how I can use the 'checkin' goal to put a war file into a CVS repository. Thanx -- Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why don't need maven-scm-plugin and password?
Hello, I checked the matter carefully. Then found that all is my fault. In fact, Maven had downloaed maven-scm-plugin, occasionally, I didn't monitor the action at that time. And I have serveral local repositories, and I searched a wrong one. God! a cup of Java, cheers! Sha Jiang jiangshachina wrote: Although I set the fowllowing at pom.xml plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-beta-3/version /plugin maven-scm-plugin wasn't downloaded. a cup of Java, cheers! Sha Jiang jiangshachina wrote: Hi guys, I set scm(CVS) connection in pom.xml scm connection scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module /connection /scm then I run mvn scm:checkout, the files were checkout sccusessfully. But I'm very puzzled! I didn't set password! maven-scm-plugin didn't downloaded! When I used scm:cvs:pserver:myuser:[EMAIL PROTECTED]:port:repository:module it was sucessful, too. a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Why-don%27t-need-maven-scm-plugin-and-password--tf2663461s177.html#a7468198 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why don't need maven-scm-plugin and password?
Hi, I think that's right. Thanks very much! a cup of Java, cheers! Sha Jiang Gisbert Amm-3 wrote: jiangshachina wrote: Hi guys, I set scm(CVS) connection in pom.xml scm connection scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module /connection /scm then I run mvn scm:checkout, the files were checkout sccusessfully. But I'm very puzzled! I didn't set password! You certainly did a cvs login on the command line prompt before, otherwise pserver would have give you an error. In this case, the CVS password was stored lightly encrypted in a file named .cvspass in your $HOME directory. See http://cvsbook.red-bean.com/cvsbook.html#login -Gisbert Amm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Why-don%27t-need-maven-scm-plugin-and-password--tf2663461s177.html#a7463993 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why don't need maven-scm-plugin and password?
Hi guys, I set scm(CVS) connection in pom.xml scm connection scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module /connection /scm then I run mvn scm:checkout, the files were checkout sccusessfully. But I'm very puzzled! I didn't set password! maven-scm-plugin didn't downloaded! When I used scm:cvs:pserver:myuser:[EMAIL PROTECTED]:port:repository:module it was sucessful, too. a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Why-don%27t-need-maven-scm-plugin-and-password--tf2663461s177.html#a7428158 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why don't need maven-scm-plugin and password?
Although I set the fowllowing at pom.xml plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-beta-3/version /plugin maven-scm-plugin wasn't downloaded. a cup of Java, cheers! Sha Jiang jiangshachina wrote: Hi guys, I set scm(CVS) connection in pom.xml scm connection scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module /connection /scm then I run mvn scm:checkout, the files were checkout sccusessfully. But I'm very puzzled! I didn't set password! maven-scm-plugin didn't downloaded! When I used scm:cvs:pserver:myuser:[EMAIL PROTECTED]:port:repository:module it was sucessful, too. a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Why-don%27t-need-maven-scm-plugin-and-password--tf2663461s177.html#a7428186 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-scm-plugin : pupose of scm:status goal ?
Hi, I would like to know the purpose of scm:status goal in maven-scm-plugin, becuase I am not able to get clear view about the functionality provided by this goal with regard to MKS proivder counterpart command ? Could somebody give some idea on this please ? Regards.
RE: maven-scm-plugin goals question
Emmanuel, It would be helpful, if it is possible to give me small hint about the operations each goal provides, while some of them are self explanatory, given the fact that different providers has bit different naming and hence confusing a bit : - 'status' - what it does ? - 'update' - what is does ? - 'status' - ? - 'tag'- ? - 'unedit' - ? - 'edit' - ? Thanks, Jaikumar -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 3:02 PM To: Maven Users List Subject: Re: maven-scm-plugin goals question Sharma, Jaikumar a écrit : Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. A login action is important for scm connection but not as a maven goal. Users prefer that the login action is embedded in other goal, so it's transparent. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? You can implement actions you want, missing actions won't be available in maven. release plugin requires checkout, commit, tag and status actions changelog plugin require changelog action continuum require checkout, update and changelog actions other important actions are add, remove ant list actions that are used by wagon-scm provider Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
RE: maven-scm-plugin goals question
They coorespond to svn commands. See any svn book or manual. -Original Message- From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006 3:09 AM To: Maven Users List Subject: RE: maven-scm-plugin goals question Emmanuel, It would be helpful, if it is possible to give me small hint about the operations each goal provides, while some of them are self explanatory, given the fact that different providers has bit different naming and hence confusing a bit : - 'status' - what it does ? - 'update' - what is does ? - 'status' - ? - 'tag'- ? - 'unedit' - ? - 'edit' - ? Thanks, Jaikumar -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 3:02 PM To: Maven Users List Subject: Re: maven-scm-plugin goals question Sharma, Jaikumar a écrit : Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. A login action is important for scm connection but not as a maven goal. Users prefer that the login action is embedded in other goal, so it's transparent. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? You can implement actions you want, missing actions won't be available in maven. release plugin requires checkout, commit, tag and status actions changelog plugin require changelog action continuum require checkout, update and changelog actions other important actions are add, remove ant list actions that are used by wagon-scm provider Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-scm-plugin goals question
Thanks. Well, this was a advice, and of course, this can always be implmented / wrapped in another goal (like I have also wrapped this in validate goal). Thanks. Jaikumar -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 9:32 AM To: Maven Users List Subject: Re: maven-scm-plugin goals question As a user, I always want to _do_ something. Logging in is, inherently, a null operation. Sure, it changes my state (from non-logged in to logged in) but only insomuch as to do the action that I _really_ want to do (such as, commit or checkout). The issue with ANT is that it is procedural. It makes you take steps (login, checkout, logout). Maven is not procedural, it is declarative. From that point of view, what good does it do anyone to declare log me in? It is the steps _after_ this operation that are fruitful, so this is what the goals focus on. To log oneself in turns a declared operation into a procedure. Consider the example goal: mvn scm:commit versus the alternate proposal: mvn scm:login scm:commit See how that becomes procedural? I'm no longer just declaring the action I want to take (commit), but now instead am directing how to take the action. Thanks; Eric On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Thanks Eric, I was not sure whether I should post this questions to maven users list or developer list.Though, to me it looks, more developer list question than user list. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? I do not believe that logging in into a system / repository is not an action, if this would have been like that then what is meaning of security and why operating system providers (Microsoft , open source Linux to name a few) implemented this behaviour into their system ? Thanks , Jaikumar -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 2:39 AM To: Maven Users List Subject: Re: maven-scm-plugin goals question Please do not cross-post between lists. More below. On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Of course, but that's not important. If an implementation does not provide for a particular goal, then it just will not be available. SCM is just like any other API. Sometimes an implementation of an API cannot provide all required functionality. Naturally, it is best to try, but if your provider does not have tag for example, naturally that goal cannot be used correctly. Regards, Jaikumar Thanks; Eric - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
Re: maven-scm-plugin goals question
Sharma, Jaikumar a écrit : Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. A login action is important for scm connection but not as a maven goal. Users prefer that the login action is embedded in other goal, so it's transparent. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? You can implement actions you want, missing actions won't be available in maven. release plugin requires checkout, commit, tag and status actions changelog plugin require changelog action continuum require checkout, update and changelog actions other important actions are add, remove ant list actions that are used by wagon-scm provider Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-scm-plugin goals question
Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Regards, Jaikumar
Re: maven-scm-plugin goals question
Please do not cross-post between lists. More below. On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Of course, but that's not important. If an implementation does not provide for a particular goal, then it just will not be available. SCM is just like any other API. Sometimes an implementation of an API cannot provide all required functionality. Naturally, it is best to try, but if your provider does not have tag for example, naturally that goal cannot be used correctly. Regards, Jaikumar Thanks; Eric
RE: maven-scm-plugin goals question
Thanks Eric, I was not sure whether I should post this questions to maven users list or developer list.Though, to me it looks, more developer list question than user list. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? I do not believe that logging in into a system / repository is not an action, if this would have been like that then what is meaning of security and why operating system providers (Microsoft , open source Linux to name a few) implemented this behaviour into their system ? Thanks , Jaikumar -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 2:39 AM To: Maven Users List Subject: Re: maven-scm-plugin goals question Please do not cross-post between lists. More below. On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Of course, but that's not important. If an implementation does not provide for a particular goal, then it just will not be available. SCM is just like any other API. Sometimes an implementation of an API cannot provide all required functionality. Naturally, it is best to try, but if your provider does not have tag for example, naturally that goal cannot be used correctly. Regards, Jaikumar Thanks; Eric
Re: maven-scm-plugin goals question
As a user, I always want to _do_ something. Logging in is, inherently, a null operation. Sure, it changes my state (from non-logged in to logged in) but only insomuch as to do the action that I _really_ want to do (such as, commit or checkout). The issue with ANT is that it is procedural. It makes you take steps (login, checkout, logout). Maven is not procedural, it is declarative. From that point of view, what good does it do anyone to declare log me in? It is the steps _after_ this operation that are fruitful, so this is what the goals focus on. To log oneself in turns a declared operation into a procedure. Consider the example goal: mvn scm:commit versus the alternate proposal: mvn scm:login scm:commit See how that becomes procedural? I'm no longer just declaring the action I want to take (commit), but now instead am directing how to take the action. Thanks; Eric On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Thanks Eric, I was not sure whether I should post this questions to maven users list or developer list.Though, to me it looks, more developer list question than user list. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? I do not believe that logging in into a system / repository is not an action, if this would have been like that then what is meaning of security and why operating system providers (Microsoft , open source Linux to name a few) implemented this behaviour into their system ? Thanks , Jaikumar -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 2:39 AM To: Maven Users List Subject: Re: maven-scm-plugin goals question Please do not cross-post between lists. More below. On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Of course, but that's not important. If an implementation does not provide for a particular goal, then it just will not be available. SCM is just like any other API. Sometimes an implementation of an API cannot provide all required functionality. Naturally, it is best to try, but if your provider does not have tag for example, naturally that goal cannot be used correctly. Regards, Jaikumar Thanks; Eric
Re: maven-scm-plugin goals question
maven-scm-api does haave login interface, however provider like svn, starteam, clearcase, etc does not have login action and therefor not implement that interface. That is why you dont see login action surfaces to maven-scm-plugin. About missing goal's doc, please file JIRA -D On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Thanks Eric, I was not sure whether I should post this questions to maven users list or developer list.Though, to me it looks, more developer list question than user list. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? I do not believe that logging in into a system / repository is not an action, if this would have been like that then what is meaning of security and why operating system providers (Microsoft , open source Linux to name a few) implemented this behaviour into their system ? Thanks , Jaikumar -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 2:39 AM To: Maven Users List Subject: Re: maven-scm-plugin goals question Please do not cross-post between lists. More below. On 7/7/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote: Dear all, As I see at the following URL goals provided by maven-scm-plugin, these goals are general goals, but at the same time, certain actions / operations which are specific to a particular SCM does not really match (for readibility / documentation reasons) to these goals. http://maven.apache.org/scm/plugins/plugin-info.html http://maven.apache.org/scm/plugins/plugin-info.html For instance, take the login action, which I think every provider implements for it repository, and in most of the cases with other providers which are implemented, login has been wrapped in URL in the pom and there itself login take place. Is it not worthwhile to provide login as a seperate goal ? or there are some good reasons to not to provide this ? What would be the value in a goal that logs in, but does not perform any actions? Next, I would appreciate, if somebody could point me to the purpose of the following goals with repect to the provider repository : scm:diff scm:status scm:tag scm:unedit If I do not implement any of the goals or only implement which are relevent / common goals which are relevent to my provider , then at the higher level would I be missing any of the functinality provided by Maven ? Of course, but that's not important. If an implementation does not provide for a particular goal, then it just will not be available. SCM is just like any other API. Sometimes an implementation of an API cannot provide all required functionality. Naturally, it is best to try, but if your provider does not have tag for example, naturally that goal cannot be used correctly. Regards, Jaikumar Thanks; Eric
RE: How to run multiple goals via maven-scm-plugin on a scm provi der plugin
Hi Dan, Thanks again for your response. I would definitely use normal build process, but I was thinking about the possiblity of running the multiple goals. The configuration you have mentioned below does not show scm provider plugin configuration ? How provider plugin has to be configured in this configuration ? Regards. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 12:44 PM To: scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin build plugins plugin artifactIdmaven-scm-plugin/artifactId goals goalbootstrap/goal goals executions execution configuration goalsa,b,c,etc/goals /configuration /execution /executions /plugin /plugins? Btw, this question should go to user list. Also, not sure why you want to do this thou, why dont you use normal maven build process? -Dan On 6/26/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: could you please mention this using a small example using xml constructs ? Regards, -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:33 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin it is not normal to build thru scm:bootstrap by specify in the pom, but you can certainly do so, by binding scm:boostrap mojo to a phase in your pom. -Dan On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks Dan, I think, what you have mentioned is command line option ? how to achieve this in pom.xml ? Regards. -Original Message- From: dan tran [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:18 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provider plugin The answer is no, but you can run mvn scm:bootstrap -Dgoals=goal1,goal2, goal2, etc -D On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Emmanuel, Is it possible to run multiple goals in sequence via maven-scm-plugin like the following : scm connectionscm:mks:[EMAIL PROTECTED]@[EMAIL PROTECTED]/connection !-- eventually, I can wrap the connect comand after the above url's validation is done, since there is no login goal is available in maven-scm-plugin -- how to specify other goal here, which might be next step like creating a sandbox on local machine ? scm Is scm providers plugins are always works as dependency to maven-scm-plugin ? Regards. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin
That seems wrong... it should be: build plugins plugin artifactIdmaven-scm-plugin/artifactId configuration put here plugin configurations that is common to all the executions /configuration executions execution id/ configuration/ -- put here configurations applicable to this execution only goals goal/ -- plugin goal for this execution /goals /execution /executions /plugin /plugins /build to run multiple goals, you may either put several goal in goals or sevearal execution in executions Sharma, Jaikumar wrote: Hi Dan, Thanks again for your response. I would definitely use normal build process, but I was thinking about the possiblity of running the multiple goals. The configuration you have mentioned below does not show scm provider plugin configuration ? How provider plugin has to be configured in this configuration ? Regards. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 12:44 PM To: scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin build plugins plugin artifactIdmaven-scm-plugin/artifactId goals goalbootstrap/goal goals executions execution configuration goalsa,b,c,etc/goals /configuration /execution /executions /plugin /plugins? Btw, this question should go to user list. Also, not sure why you want to do this thou, why dont you use normal maven build process? -Dan On 6/26/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: could you please mention this using a small example using xml constructs ? Regards, -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:33 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin it is not normal to build thru scm:bootstrap by specify in the pom, but you can certainly do so, by binding scm:boostrap mojo to a phase in your pom. -Dan On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks Dan, I think, what you have mentioned is command line option ? how to achieve this in pom.xml ? Regards. -Original Message- From: dan tran [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:18 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provider plugin The answer is no, but you can run mvn scm:bootstrap -Dgoals=goal1,goal2, goal2, etc -D On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Emmanuel, Is it possible to run multiple goals in sequence via maven-scm-plugin like the following : scm connectionscm:mks:[EMAIL PROTECTED]@[EMAIL PROTECTED]/connection !-- eventually, I can wrap the connect comand after the above url's validation is done, since there is no login goal is available in maven-scm-plugin -- how to specify other goal here, which might be next step like creating a sandbox on local machine ? scm Is scm providers plugins are always works as dependency to maven-scm-plugin ? Regards. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept
RE: How to run multiple goals via maven-scm-plugin on a scm provi der plugin
Thanks Edwin and Dan both. I would like to know, where my maven-scm-provider-mks plugin fits into this configuration ? It has to be specified as a dependency or what ? Regards. -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 1:27 PM To: Maven Users List Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin That seems wrong... it should be: build plugins plugin artifactIdmaven-scm-plugin/artifactId configuration put here plugin configurations that is common to all the executions /configuration executions execution id/ configuration/ -- put here configurations applicable to this execution only goals goal/ -- plugin goal for this execution /goals /execution /executions /plugin /plugins /build to run multiple goals, you may either put several goal in goals or sevearal execution in executions Sharma, Jaikumar wrote: Hi Dan, Thanks again for your response. I would definitely use normal build process, but I was thinking about the possiblity of running the multiple goals. The configuration you have mentioned below does not show scm provider plugin configuration ? How provider plugin has to be configured in this configuration ? Regards. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 12:44 PM To: scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin build plugins plugin artifactIdmaven-scm-plugin/artifactId goals goalbootstrap/goal goals executions execution configuration goalsa,b,c,etc/goals /configuration /execution /executions /plugin /plugins? Btw, this question should go to user list. Also, not sure why you want to do this thou, why dont you use normal maven build process? -Dan On 6/26/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: could you please mention this using a small example using xml constructs ? Regards, -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:33 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin it is not normal to build thru scm:bootstrap by specify in the pom, but you can certainly do so, by binding scm:boostrap mojo to a phase in your pom. -Dan On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks Dan, I think, what you have mentioned is command line option ? how to achieve this in pom.xml ? Regards. -Original Message- From: dan tran [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:18 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provider plugin The answer is no, but you can run mvn scm:bootstrap -Dgoals=goal1,goal2, goal2, etc -D On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Emmanuel, Is it possible to run multiple goals in sequence via maven-scm-plugin like the following : scm connectionscm:mks:[EMAIL PROTECTED]@[EMAIL PROTECTED]/connection !-- eventually, I can wrap the connect comand after the above url's validation is done, since there is no login goal is available in maven-scm-plugin -- how to specify other goal here, which might be next step like creating a sandbox on local machine ? scm Is scm providers plugins are always works as dependency to maven-scm-plugin ? Regards. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged
Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin
I think it should be provided as a dependency under plugin Sharma, Jaikumar wrote: Thanks Edwin and Dan both. I would like to know, where my maven-scm-provider-mks plugin fits into this configuration ? It has to be specified as a dependency or what ? Regards. -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 1:27 PM To: Maven Users List Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin That seems wrong... it should be: build plugins plugin artifactIdmaven-scm-plugin/artifactId configuration put here plugin configurations that is common to all the executions /configuration executions execution id/ configuration/ -- put here configurations applicable to this execution only goals goal/ -- plugin goal for this execution /goals /execution /executions /plugin /plugins /build to run multiple goals, you may either put several goal in goals or sevearal execution in executions Sharma, Jaikumar wrote: Hi Dan, Thanks again for your response. I would definitely use normal build process, but I was thinking about the possiblity of running the multiple goals. The configuration you have mentioned below does not show scm provider plugin configuration ? How provider plugin has to be configured in this configuration ? Regards. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 12:44 PM To: scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin build plugins plugin artifactIdmaven-scm-plugin/artifactId goals goalbootstrap/goal goals executions execution configuration goalsa,b,c,etc/goals /configuration /execution /executions /plugin /plugins? Btw, this question should go to user list. Also, not sure why you want to do this thou, why dont you use normal maven build process? -Dan On 6/26/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: could you please mention this using a small example using xml constructs ? Regards, -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:33 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provi der plugin it is not normal to build thru scm:bootstrap by specify in the pom, but you can certainly do so, by binding scm:boostrap mojo to a phase in your pom. -Dan On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks Dan, I think, what you have mentioned is command line option ? how to achieve this in pom.xml ? Regards. -Original Message- From: dan tran [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Monday, June 26, 2006 12:18 PM To: scm-dev@maven.apache.org mailto:scm-dev@maven.apache.org Subject: Re: How to run multiple goals via maven-scm-plugin on a scm provider plugin The answer is no, but you can run mvn scm:bootstrap -Dgoals=goal1,goal2, goal2, etc -D On 6/25/06, Sharma, Jaikumar [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Emmanuel, Is it possible to run multiple goals in sequence via maven-scm-plugin like the following : scm connectionscm:mks:[EMAIL PROTECTED]@[EMAIL PROTECTED]/connection !-- eventually, I can wrap the connect comand after the above url's validation is done, since there is no login goal is available in maven-scm-plugin -- how to specify other goal here, which might be next step like creating a sandbox on local machine ? scm Is scm providers plugins are always works as dependency to maven-scm-plugin ? Regards. - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - - - - - - - DISCLAIMER
m2 how to tag a build using maven scm plugin java api
Hi Everyone, I would like to tag a build frommy plugin. I noticed there is scm plugin which already has apis to tag a build. Can you tell me if it is possible to use this API from my plugin to tag a build. -- -Gautham Pamu
Re: m2 how to tag a build using maven scm plugin java api
yes you can, take a look at maven-scm-plugin to see how the api is used. Another quick way is to spin off a jvm to call maven-scm-plugin directy using plexus-utils' cli interface. see maven-scm-plugin's boostrap source. -D On 5/1/06, Gautham Pamu [EMAIL PROTECTED] wrote: Hi Everyone, I would like to tag a build frommy plugin. I noticed there is scm plugin which already has apis to tag a build. Can you tell me if it is possible to use this API from my plugin to tag a build. -- -Gautham Pamu
Re: m2 how to tag a build using maven scm plugin java api
Hi Dan, Could you tell me in which module of scm I can find the bootstrap source. I have complete maven plugin code extracted but I did not see bootstrap code. Thanks Gautham Pamu On 5/1/06, dan tran [EMAIL PROTECTED] wrote: yes you can, take a look at maven-scm-plugin to see how the api is used. Another quick way is to spin off a jvm to call maven-scm-plugin directy using plexus-utils' cli interface. see maven-scm-plugin's boostrap source. -D On 5/1/06, Gautham Pamu [EMAIL PROTECTED] wrote: Hi Everyone, I would like to tag a build frommy plugin. I noticed there is scm plugin which already has apis to tag a build. Can you tell me if it is possible to use this API from my plugin to tag a build. -- -Gautham Pamu -- -Gautham Pamu
Re: m2 how to tag a build using maven scm plugin java api
http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java On 5/1/06, Gautham Pamu [EMAIL PROTECTED] wrote: Hi Dan, Could you tell me in which module of scm I can find the bootstrap source. I have complete maven plugin code extracted but I did not see bootstrap code. Thanks Gautham Pamu On 5/1/06, dan tran [EMAIL PROTECTED] wrote: yes you can, take a look at maven-scm-plugin to see how the api is used. Another quick way is to spin off a jvm to call maven-scm-plugin directy using plexus-utils' cli interface. see maven-scm-plugin's boostrap source. -D On 5/1/06, Gautham Pamu [EMAIL PROTECTED] wrote: Hi Everyone, I would like to tag a build frommy plugin. I noticed there is scm plugin which already has apis to tag a build. Can you tell me if it is possible to use this API from my plugin to tag a build. -- -Gautham Pamu -- -Gautham Pamu
[M2] How to get maven-scm-plugin-1.0-alpha-4
I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
the best way is to use the -U parameter on command line for update the plugin Emmanuel Jose Gonzalez Gomez said: As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
I've tried to do that, even deleting the repository before doing it, and I keep getting alpha-3 Jose 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: the best way is to use the -U parameter on command line for update the plugin Emmanuel Jose Gonzalez Gomez said: As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
metadata seems to be wrong in repository, filed an issue and we'll fixed it. Emmanuel Jose Gonzalez Gomez said: I've tried to do that, even deleting the repository before doing it, and I keep getting alpha-3 Jose 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: the best way is to use the -U parameter on command line for update the plugin Emmanuel Jose Gonzalez Gomez said: As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
Do you want me to file the issue? That d in filed an issue makes me doubt :o) 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: metadata seems to be wrong in repository, filed an issue and we'll fixed it. Emmanuel Jose Gonzalez Gomez said: I've tried to do that, even deleting the repository before doing it, and I keep getting alpha-3 Jose 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: the best way is to use the -U parameter on command line for update the plugin Emmanuel Jose Gonzalez Gomez said: As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to get maven-scm-plugin-1.0-alpha-4
yes, please. sorry for my fault. Emmanuel Jose Gonzalez Gomez said: Do you want me to file the issue? That d in filed an issue makes me doubt :o) 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: metadata seems to be wrong in repository, filed an issue and we'll fixed it. Emmanuel Jose Gonzalez Gomez said: I've tried to do that, even deleting the repository before doing it, and I keep getting alpha-3 Jose 2005/11/3, Emmanuel Venisse [EMAIL PROTECTED]: the best way is to use the -U parameter on command line for update the plugin Emmanuel Jose Gonzalez Gomez said: As a workaround, it seems that manually editing the maven-metadata-central.xml file in the local repository and adding the version is enough to make maven download the new version. HTH, best regards Jose 2005/11/3, Jose Gonzalez Gomez [EMAIL PROTECTED]: I'd like to get this version of the scm plugin, as it seems there is a fix for a bug I'm hitting. The version seems to be in the ibiblio repository, but whenever I try to get the latest version I always get 1.0-alpha-3. The problem seems to be related to the plugin metadata: http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-scm-plugin/maven-metadata.xml This seems to state that the latest version of the plugin is 1.0-alpha-3... should/could anybody change this? Is this intended? TIA, best regards Jose - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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
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.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
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.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
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
Maven SCM Plugin 1.5 Released
Hi, This is to announce the release of the Maven SCM plugin 1.5 for Maven 1.0. http://maven.apache.org/reference/plugins/scm/ To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-scm-plugin -Dversion=1.5 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-scm-plugin-1.5.jar Notable changes in this version include: * [MPSCM-32] - Support Subversion * [MPSCM-44] - Skip prompt for tag * [MPSCM-50] - Support starting and ending revision in diff bean/tag * [MPSCM-25] - The goal scm:cvs-create-patch includes differences in whitespace * [MPSCM-29] - scm:cvs-update-project uses developer connection * [MPSCM-33] - maven.scm.bootstrap.pom.dir is not used * [MPSCM-45] - var delim not allways : (on CVSNT |) * [MPSCM-53] - NullPointerException when setting checkout dir - The Apache Maven Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven SCM plugin: where do I get cvs.exe?
What is the error message you get? 2005/5/30, Massimiliano Amato [EMAIL PROTECTED]: Hi. I've cvs.exe in the path but scm plugin still doesn't work I can run cvs from the directory where i lauch maven from I launched maven with -X option and cvs.exe is in the path, what could be the problem? On 5/26/05, bryan ( [EMAIL PROTECTED]) [EMAIL PROTECTED] wrote: google: find cvsnt , install it , add the cvs.exe to your path On 5/26/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, this is my first attempt at using cvs, so bear with me for a moment. I tried: maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=pmd -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -Dmaven.scm.checkout.dir=. to get the latest PMD code, but this fails with the following error: java.io.IOException: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -q checkout -P pmd error=2 Which means that cvs.exe (or .bat) cannot be found. Do I need to install a cvs client or server or what do I need? Basically, I want to start to learn how to contribute to open-source projects. I hope you can help me out. regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven SCM plugin: where do I get cvs.exe?
Thanks but i found the problem. It was the fact that directory contained a space and i was forced to put it between and that make Maven not being too happy about it! As soon as i removed the space from the name and the worked On 5/31/05, Wim Deblauwe [EMAIL PROTECTED] wrote: What is the error message you get? 2005/5/30, Massimiliano Amato [EMAIL PROTECTED]: Hi. I've cvs.exe in the path but scm plugin still doesn't work I can run cvs from the directory where i lauch maven from I launched maven with -X option and cvs.exe is in the path, what could be the problem? On 5/26/05, bryan ( [EMAIL PROTECTED]) [EMAIL PROTECTED] wrote: google: find cvsnt , install it , add the cvs.exe to your path On 5/26/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, this is my first attempt at using cvs, so bear with me for a moment. I tried: maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=pmd -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -Dmaven.scm.checkout.dir=. to get the latest PMD code, but this fails with the following error: java.io.IOException: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -q checkout -P pmd error=2 Which means that cvs.exe (or .bat) cannot be found. Do I need to install a cvs client or server or what do I need? Basically, I want to start to learn how to contribute to open-source projects. I hope you can help me out. regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven SCM Plugin 1.5 RC1 released
Hi, This is to announce the releaes of a release candidate of the Maven SCM plugin for Maven 1.0. http://maven.apache.org/reference/plugins/scm/ To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-scm-plugin -Dversion=1.5-rc1 -Dmaven.repo.remote=http://cvs.apache.org/repository For a manual installation, you can download the plugin here: http://cvs.apache.org/repository/maven/plugins/maven-scm-plugin-1.5-rc1.jar Changes in this version include: * [MPSCM-25 http://jira.codehaus.org/browse/MPSCM-25] - The goal scm:cvs-create-patch includes differences in whitespace * [MPSCM-29 http://jira.codehaus.org/browse/MPSCM-29] - scm:cvs-update-project uses developer connection * [MPSCM-33 http://jira.codehaus.org/browse/MPSCM-33] - maven.scm.bootstrap.pom.dir is not used * [MPSCM-40 http://jira.codehaus.org/browse/MPSCM-40] - Avoid use of jelly empty operator * [MPSCM-45 http://jira.codehaus.org/browse/MPSCM-45] - var delim not allways : (on CVSNT |) * [MPSCM-52 http://jira.codehaus.org/browse/MPSCM-52] - scm:bootstrap fails on SVN project requiring username/password. * [MPSCM-53 http://jira.codehaus.org/browse/MPSCM-53] - NullPointerException when setting checkout dir * [MPSCM-32 http://jira.codehaus.org/browse/MPSCM-32] - Support Subversion * [MPSCM-44 http://jira.codehaus.org/browse/MPSCM-44] - Skip prompt for tag * [MPSCM-50 http://jira.codehaus.org/browse/MPSCM-50] - Support starting and ending revision in diff bean/tag * [MPSCM-41 http://jira.codehaus.org/browse/MPSCM-41] - update documentation after latest changes * [MPSCM-42 http://jira.codehaus.org/browse/MPSCM-42] - implement status check * [MPSCM-48 http://jira.codehaus.org/browse/MPSCM-48] - clarify module notation as used for CVS in regards to Subversion * [MPSCM-49 http://jira.codehaus.org/browse/MPSCM-49] - incorporate a released version of Maven SCM - The Apache Maven Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven SCM plugin: where do I get cvs.exe?
Hi. I've cvs.exe in the path but scm plugin still doesn't work I can run cvs from the directory where i lauch maven from I launched maven with -X option and cvs.exe is in the path, what could be the problem? On 5/26/05, bryan ( [EMAIL PROTECTED]) [EMAIL PROTECTED] wrote: google: find cvsnt , install it , add the cvs.exe to your path On 5/26/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, this is my first attempt at using cvs, so bear with me for a moment. I tried: maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=pmd -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -Dmaven.scm.checkout.dir=. to get the latest PMD code, but this fails with the following error: java.io.IOException: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -q checkout -P pmd error=2 Which means that cvs.exe (or .bat) cannot be found. Do I need to install a cvs client or server or what do I need? Basically, I want to start to learn how to contribute to open-source projects. I hope you can help me out. regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven SCM plugin: where do I get cvs.exe?
Hi, this is my first attempt at using cvs, so bear with me for a moment. I tried: maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=pmd -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -Dmaven.scm.checkout.dir=. to get the latest PMD code, but this fails with the following error: java.io.IOException: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/pmd -q checkout -P pmd error=2 Which means that cvs.exe (or .bat) cannot be found. Do I need to install a cvs client or server or what do I need? Basically, I want to start to learn how to contribute to open-source projects. I hope you can help me out. regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven SCM Plugin 1.5 Beta 3 gets confused over extra output
Hi, it seems the Maven-scm-plugin 1.5 beta 3 gets confused over the output of svn when extrenals are used in svn. The output of my svn command is: svn update --non-interactive Fetching external item into 'common' External at revision 3257. At revision 3257. so, the output of doing: maven scm:update [INFO] Executing: svn update --non-interactive [INFO] Working directory: . [WARNING] Unexpected input, the line must be at least three characters long. Line: ''. [INFO] Unknown file status: 'F'. [INFO] Unknown file status: 'E'. [WARNING] Unexpected input, the line must be at least three characters long. Line: ''. Should the plugin call svn -q ? Or should I set a flag somwhere? Regards Mark Donszelmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven SCM Plugin 1.5 Beta 3 gets confused over extra output
I thought it did pass -q. I'll check. These are just warnings - no need to panic. - Brett On Mon, 14 Feb 2005 15:14:09 -0800, Mark Donszelmann [EMAIL PROTECTED] wrote: Hi, it seems the Maven-scm-plugin 1.5 beta 3 gets confused over the output of svn when extrenals are used in svn. The output of my svn command is: svn update --non-interactive Fetching external item into 'common' External at revision 3257. At revision 3257. so, the output of doing: maven scm:update [INFO] Executing: svn update --non-interactive [INFO] Working directory: . [WARNING] Unexpected input, the line must be at least three characters long. Line: ''. [INFO] Unknown file status: 'F'. [INFO] Unknown file status: 'E'. [WARNING] Unexpected input, the line must be at least three characters long. Line: ''. Should the plugin call svn -q ? Or should I set a flag somwhere? Regards Mark Donszelmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error initialising plugin context for maven-scm-plugin
Hi, I'm trying to set a property within a goal in maven.xml file like this: maven:set plugin=maven-scm-plugin property=maven.scm.cvs.module value=Test / I've done this before with other plugins with out a problem, but with this one I get an Error initialising plugin context error. When I print out the debug message it mentions not being able to find the org.apache.commons.jelly.tags.log.LogTagLibrary class. I deleted my ~/.maven directory and I am getting the latest version of maven-scm-plugin(1.4.1). Anyone have any idea what's causing this? The full debug log is below. Thanks in advance, Eric __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Initializing Plugins! Set plugin source directory to /home/eblack/tools/maven/plugins Set unpacked plugin directory to /home/eblack/.maven/cache Set user plugin directory to /home/eblack/.maven/plugins Loading plugin cache Now mapping cached plugins Loading plugin 'maven-cruisecontrol-plugin-1.6' Loading plugin 'maven-multichanges-plugin-1.1' Loading plugin 'maven-checkstyle-plugin-2.5' Loading plugin 'maven-file-activity-plugin-1.5.1' Loading plugin 'maven-jellydoc-plugin-1.3.1' Loading plugin 'maven-ear-plugin-1.6' Loading plugin 'maven-jdepend-plugin-1.5' Loading plugin 'maven-pom-plugin-1.4.1' Loading plugin 'maven-jira-plugin-1.1.2' Loading plugin 'maven-jar-plugin-1.6.1' Loading plugin 'maven-developer-activity-plugin-1.5.1' Loading plugin 'maven-jboss-plugin-1.5' Loading plugin 'maven-faq-plugin-1.4' Loading plugin 'maven-dist-plugin-1.6.1' Loading plugin 'maven-javadoc-plugin-1.7' Loading plugin 'maven-linkcheck-plugin-1.3.4' Loading plugin 'maven-tasklist-plugin-2.3' Loading plugin 'maven-idea-plugin-1.5' Loading plugin 'maven-jcoverage-plugin-1.0.9' Loading plugin 'maven-junit-report-plugin-1.5' Loading plugin 'maven-plugin-plugin-1.5.2' Loading plugin 'maven-changelog-plugin-1.7.1' Loading plugin 'maven-jxr-plugin-1.4.2' Loading plugin 'maven-ashkelon-plugin-1.2' Loading plugin 'maven-announcement-plugin-1.3' Loading plugin 'maven-xdoc-plugin-1.8' Loading plugin 'maven-eclipse-plugin-1.9' Loading plugin 'maven-shell-plugin-1.1' Loading plugin 'maven-rar-plugin-1.0' Loading plugin 'maven-dashboard-plugin-1.6' Loading plugin 'maven-scm-plugin-1.4.1' Loading plugin 'maven-clover-plugin-1.6' Loading plugin 'maven-uberjar-plugin-1.2' Loading plugin 'maven-war-plugin-1.6.1' Loading plugin 'maven-simian-plugin-1.4' Loading plugin 'maven-ant-plugin-1.8.1' Loading plugin 'maven-ejb-plugin-1.5' Loading plugin 'maven-tjdo-plugin-1.0.0' Loading plugin 'maven-changes-plugin-1.5.1' Loading plugin 'maven-j2ee-plugin-1.5.1' Loading plugin 'maven-release-plugin-1.4.1' Loading plugin 'maven-abbot-plugin-1.1' Loading plugin 'maven-multiproject-plugin-1.3.1' Loading plugin 'maven-nsis-plugin-1.1' Loading plugin 'maven-license-plugin-1.2' Loading plugin 'maven-jdiff-plugin-1.4' Loading plugin 'maven-pmd-plugin-1.6' Loading plugin 'maven-repository-plugin-1.2' Loading plugin 'maven-jbuilder-plugin-1.5' Loading plugin 'maven-console-plugin-1.1' Loading plugin 'maven-webserver-plugin-2.0' Loading plugin 'maven-aspectwerkz-plugin-1.2' Loading plugin 'maven-test-plugin-1.6.2' Loading plugin 'maven-jetty-plugin-1.1' Loading plugin 'maven-docbook-plugin-1.2' Loading plugin 'maven-ccManifest-plugin-1.0.0' Loading plugin 'maven-latka-plugin-1.4.1' Loading plugin 'maven-aspectj-plugin-3.2' Loading plugin 'maven-hibernate-plugin-1.2' Loading plugin 'maven-native-plugin-1.1' Loading plugin 'maven-site-plugin-1.5.2' Loading plugin 'maven-gump-plugin-1.4' Loading plugin 'maven-appserver-plugin-2.0' Loading plugin 'maven-java-plugin-1.5' Loading plugin 'maven-pdf-plugin-2.2.1' Loading plugin 'maven-ccScm-plugin-1.0.0' Loading plugin 'maven-html2xdoc-plugin-1.3.1' Loading plugin 'maven-jdee-plugin-1.1' Loading plugin 'maven-jalopy-plugin-1.3.1' Loading plugin 'maven-jnlp-plugin-1.4.1' Loading plugin 'maven-jdeveloper-plugin-1.4' Loading plugin 'maven-junit-doclet-plugin-1.2' Loading plugin 'maven-wizard-plugin-1.1' Loading plugin 'maven-artifact-plugin-1.4.1' Loading plugin 'maven-javacc-plugin-1.1' Loading plugin 'maven-antlr-plugin-1.2.1' Loading plugin 'maven-struts-plugin-1.3' Loading plugin 'maven-clean-plugin-1.3' Loading plugin 'maven-castor-plugin-1.2' Loading plugin 'maven-latex-plugin-1.4.1' Loading plugin 'maven-genapp-plugin-2.2' Loading plugin 'maven-caller-plugin-1.1' Loading plugin 'maven-vdoclet-plugin-1.2' Now loading uncached plugins Finished initializing Plugins! Using userBuildPropertiesFile: /home/eblack/build.properties Using projectPropertiesFile: /mnt/hda3/eblack/work/Projects/Builds/Portfolio/project.properties Using projectBuildPropertiesFile: /mnt/hda3/eblack/work/Projects/Builds/Portfolio/build.properties Using userBuildPropertiesFile: /home/eblack/build.properties Using projectPropertiesFile: /mnt/hda3/eblack/work/Projects/Builds/project.properties Using
Re: Error initialising plugin context for maven-scm-plugin
I was able to get rid of the error by setting a dependency to commons-jelly-tags-log-1.0.jar in my project.xml file(it was downloaded and installed), but the maven.scm.cvs.module property isn't getting set. Eric Maven Users List users@maven.apache.org on Friday, February 11, 2005 at 3:06 PM + wrote: Hi, I'm trying to set a property within a goal in maven.xml file like this: maven:set plugin=maven-scm-plugin property=maven.scm.cvs.module value=Test / I've done this before with other plugins with out a problem, but with this one I get an Error initialising plugin context error. When I print out the debug message it mentions not being able to find the org.apache.commons.jelly.tags.log.LogTagLibrary class. I deleted my ~/.maven directory and I am getting the latest version of maven-scm-plugin(1.4.1). Anyone have any idea what's causing this? The full debug log is below. Thanks in advance, Eric __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Initializing Plugins! Set plugin source directory to /home/eblack/tools/maven/plugins Set unpacked plugin directory to /home/eblack/.maven/cache Set user plugin directory to /home/eblack/.maven/plugins Loading plugin cache Now mapping cached plugins Loading plugin 'maven-cruisecontrol-plugin-1.6' Loading plugin 'maven-multichanges-plugin-1.1' Loading plugin 'maven-checkstyle-plugin-2.5' Loading plugin 'maven-file-activity-plugin-1.5.1' Loading plugin 'maven-jellydoc-plugin-1.3.1' Loading plugin 'maven-ear-plugin-1.6' Loading plugin 'maven-jdepend-plugin-1.5' Loading plugin 'maven-pom-plugin-1.4.1' Loading plugin 'maven-jira-plugin-1.1.2' Loading plugin 'maven-jar-plugin-1.6.1' Loading plugin 'maven-developer-activity-plugin-1.5.1' Loading plugin 'maven-jboss-plugin-1.5' Loading plugin 'maven-faq-plugin-1.4' Loading plugin 'maven-dist-plugin-1.6.1' Loading plugin 'maven-javadoc-plugin-1.7' Loading plugin 'maven-linkcheck-plugin-1.3.4' Loading plugin 'maven-tasklist-plugin-2.3' Loading plugin 'maven-idea-plugin-1.5' Loading plugin 'maven-jcoverage-plugin-1.0.9' Loading plugin 'maven-junit-report-plugin-1.5' Loading plugin 'maven-plugin-plugin-1.5.2' Loading plugin 'maven-changelog-plugin-1.7.1' Loading plugin 'maven-jxr-plugin-1.4.2' Loading plugin 'maven-ashkelon-plugin-1.2' Loading plugin 'maven-announcement-plugin-1.3' Loading plugin 'maven-xdoc-plugin-1.8' Loading plugin 'maven-eclipse-plugin-1.9' Loading plugin 'maven-shell-plugin-1.1' Loading plugin 'maven-rar-plugin-1.0' Loading plugin 'maven-dashboard-plugin-1.6' Loading plugin 'maven-scm-plugin-1.4.1' Loading plugin 'maven-clover-plugin-1.6' Loading plugin 'maven-uberjar-plugin-1.2' Loading plugin 'maven-war-plugin-1.6.1' Loading plugin 'maven-simian-plugin-1.4' Loading plugin 'maven-ant-plugin-1.8.1' Loading plugin 'maven-ejb-plugin-1.5' Loading plugin 'maven-tjdo-plugin-1.0.0' Loading plugin 'maven-changes-plugin-1.5.1' Loading plugin 'maven-j2ee-plugin-1.5.1' Loading plugin 'maven-release-plugin-1.4.1' Loading plugin 'maven-abbot-plugin-1.1' Loading plugin 'maven-multiproject-plugin-1.3.1' Loading plugin 'maven-nsis-plugin-1.1' Loading plugin 'maven-license-plugin-1.2' Loading plugin 'maven-jdiff-plugin-1.4' Loading plugin 'maven-pmd-plugin-1.6' Loading plugin 'maven-repository-plugin-1.2' Loading plugin 'maven-jbuilder-plugin-1.5' Loading plugin 'maven-console-plugin-1.1' Loading plugin 'maven-webserver-plugin-2.0' Loading plugin 'maven-aspectwerkz-plugin-1.2' Loading plugin 'maven-test-plugin-1.6.2' Loading plugin 'maven-jetty-plugin-1.1' Loading plugin 'maven-docbook-plugin-1.2' Loading plugin 'maven-ccManifest-plugin-1.0.0' Loading plugin 'maven-latka-plugin-1.4.1' Loading plugin 'maven-aspectj-plugin-3.2' Loading plugin 'maven-hibernate-plugin-1.2' Loading plugin 'maven-native-plugin-1.1' Loading plugin 'maven-site-plugin-1.5.2' Loading plugin 'maven-gump-plugin-1.4' Loading plugin 'maven-appserver-plugin-2.0' Loading plugin 'maven-java-plugin-1.5' Loading plugin 'maven-pdf-plugin-2.2.1' Loading plugin 'maven-ccScm-plugin-1.0.0' Loading plugin 'maven-html2xdoc-plugin-1.3.1' Loading plugin 'maven-jdee-plugin-1.1' Loading plugin 'maven-jalopy-plugin-1.3.1' Loading plugin 'maven-jnlp-plugin-1.4.1' Loading plugin 'maven-jdeveloper-plugin-1.4' Loading plugin 'maven-junit-doclet-plugin-1.2' Loading plugin 'maven-wizard-plugin-1.1' Loading plugin 'maven-artifact-plugin-1.4.1' Loading plugin 'maven-javacc-plugin-1.1' Loading plugin 'maven-antlr-plugin-1.2.1' Loading plugin 'maven-struts-plugin-1.3' Loading plugin 'maven-clean-plugin-1.3' Loading plugin 'maven-castor-plugin-1.2' Loading plugin 'maven-latex-plugin-1.4.1' Loading plugin 'maven-genapp-plugin-2.2' Loading plugin 'maven-caller-plugin-1.1' Loading plugin 'maven-vdoclet-plugin-1.2' Now loading uncached plugins Finished initializing Plugins! Using userBuildPropertiesFile: /home/eblack/build.properties Using projectPropertiesFile: /mnt/hda3/eblack/work
Re: Error initialising plugin context for maven-scm-plugin
Sorry for the multiple posts, but maybe someone else might have the same
problem. This is what I was doing:
goal name=projectco
!-- Check the input required variables --
attainGoal name=ccscm:checkvars /
j:set var=module value=${pom.name} /
ant:echo message=MODULE: ${module}/
maven:set plugin=maven-scm-plugin property=maven.scm.cvs.module
value=${module} /
maven:set plugin=maven-scm-plugin property=maven.scm.checkout.dir
value=../../../ /
maven:get plugin=maven-scm-plugin property=maven.scm.cvs.module
var=getmod /
ant:echo message=MODULE: ${getmod} /
attainGoal session=${context.getVariable('maven.session.global',
'parent')} name=scm:checkout-project /
ant:echo message=Done/
/goal
The error I kept getting was that maven.scm.cvs.module was not set when
scm:checkout-project was running. There's alot of debugging messages, but
the jelly:maven:set tag wasn't passing the variable to the
attainGoal(scm:checkout-project), even after I added the session
parameter(I got that hint from jira.codehaus.org). I did get
maven.scm.cvs.module set by using the simple core jelly set tag:
j:set var=maven.scm.cvs.module value=${module} /
I guess what happened is the jelly set tag is actually setting a variable
in the current context, whereas maven:set sets variables in a secondary
top level maven context(sort of like a shell), but attaingoal is running
in the current context.
Please correct me if I'm wrong.
Eric
Maven Users List users@maven.apache.org on Friday, February 11, 2005
at 3:33 PM + wrote:
was able to get rid of the error by setting a dependency to
commons-jelly-tags-log-1.0.jar in my project.xml file(it was downloaded
and installed), but the maven.scm.cvs.module property isn't getting set.
Eric
Maven Users List users@maven.apache.org on Friday, February 11, 2005
at 3:06 PM + wrote:
Hi,
I'm trying to set a property within a goal in maven.xml file like this:
maven:set plugin=maven-scm-plugin property=maven.scm.cvs.module
value=Test /
I've done this before with other plugins with out a problem, but with
this
one I get an
Error initialising plugin context error. When I print out the debug
message it mentions not being able to find the
org.apache.commons.jelly.tags.log.LogTagLibrary class. I deleted my
~/.maven directory and I am getting the latest version of
maven-scm-plugin(1.4.1). Anyone have any idea what's causing this?
The full debug log is below.
Thanks in advance,
Eric
Maven SCM Plugin
Hi The Maven SCM plugin was working with CVS and Subversion until it was changed today to work only with CVS. what happened? are you going to make it work with Subversion back? and if yes how long it will take? thank you in advance, Bahaa Nasrallah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
