RE: [M2] maven-release-plugin: debug vs. release version
Hi, CodingPlayer wrote on Wednesday, August 22, 2007 2:20 PM: > Hi, > > i recently asked myself, if there is any possibility to > discriminate between > a debug and a release version (like in the old C++ days). > > what i mean exactly is, that when releasing a project, i > would like to have > the possibility to decide to either generate a > > debug-version: > - containing full debug information (javac -g) > - containing a -sources.jar > - no obfuscation > - active assertions and runtime checks > > or a release-version: > - no debug information (javac -g:none) > - NO -sources.jar > - obfuscated classes > - no assertions and runtime checks > > > an example: > - lets say i want to release 'myproject' current snapshot 2.0-SNAPSHOT > - i would like to release a debug release (2.0) to my > companies (internal) > remote repository (for other developers to have all sources, > and see line > numbers and so on) > - and additionally i would like to release the same version (2.0) to > an (external) repository but containing a release version > (obfuscated, no line numbers, ...) > > > but i don't want to generate two version numbers (because those users > depending on 'myproject' using the latest version, should > always retrieve > either the 'debug' or the 'release' version, depending > whether they are in > my company and can access the internal repository, or not) > > > my only thoughts point to a solution, where i generate a > profile for each > type of release, configuring plugins to generate different > artifacts (JARs) > and running only the release:prepare command, then manually > run the deploy > phase (with the external profile: other repository, changed compiler > settings, ...) and then executing release:perform (for the > default release > to my remote repository). > > > maybe someone knows about a better way of doing so. > > thx 4 help > R.C. use profiles and deploy manually again: 1. perform the normal release 2. go to the target/checkout directory 3. "mvn -Pdebug clean deploy" - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] maven-release-plugin and javadoc @version tags
You have right, it should be better to give more information. I was thinking about something like this [1] (cf section Filtering Source Code) But it's better to have a filter parameter directly in the maven-javadoc-plugin. It seems it's not the case for the moment. Open a jira for this enhancement. HTH, Rémy [1] http://www.jroller.com/rss/l2fprod?catname=/Java
Re: [M2] maven-release-plugin and javadoc @version tags
I'm sorry but i don't know anything about filtering? What do you mean
exactly?
i thought maven-properties are only accessible within the pom.xml file?
What i need is a plugin, that looks at the ${pom.version} and the walks
through all my packages (in my source folder) and change the @version
javadoc tag in every single java class file.
I couldn't find any plugin doing this.
Maybe this filtering you mentioned can help?
thx
R.C.
Rémy Sanlaville wrote:
>
> Hi,
>
> Isn't possible to use filtering with ${pom.version} ?
>
> Rémy
>
> 2007/3/16, CodingPlayer <[EMAIL PROTECTED]>:
>>
>>
>> Hi All,
>>
>> i just was wondering if there is any possibility to tell the
>> maven-release-plugin, to change ALL the source files as well?
>>
>> i mean, it would be nice, if the @version javadoc tag would be
>> automatically
>> changed for each class.
>>
>> For e.g. when releasing version 1.7 and changing to 1.8-SNAPSHOT, all
>> @version tags (for each class) should be changed to 1.8 (right after the
>> release).
>>
>>
>> If someone knows a way to do this pls let me know.
>> Maybe there is another plugin that is capable of this functionality?
>>
>> thx
>> R.C.
>> --
>> View this message in context:
>> http://www.nabble.com/-M2--maven-release-plugin-and-javadoc-%40version-tags-tf3414345s177.html#a9513881
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/-M2--maven-release-plugin-and-javadoc-%40version-tags-tf3414345s177.html#a9514526
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: [M2] maven-release-plugin and javadoc @version tags
Hi,
Isn't possible to use filtering with ${pom.version} ?
Rémy
2007/3/16, CodingPlayer <[EMAIL PROTECTED]>:
Hi All,
i just was wondering if there is any possibility to tell the
maven-release-plugin, to change ALL the source files as well?
i mean, it would be nice, if the @version javadoc tag would be
automatically
changed for each class.
For e.g. when releasing version 1.7 and changing to 1.8-SNAPSHOT, all
@version tags (for each class) should be changed to 1.8 (right after the
release).
If someone knows a way to do this pls let me know.
Maybe there is another plugin that is capable of this functionality?
thx
R.C.
--
View this message in context:
http://www.nabble.com/-M2--maven-release-plugin-and-javadoc-%40version-tags-tf3414345s177.html#a9513881
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: [m2] maven-release-plugin: how about a prompt for customizing commit comment during release preparation ?
Please find it at http://jira.codehaus.org/browse/MRELEASE-156 . For those of you who also want this feature, please vote for it. Thanks, Dário Jorg Heymans wrote: Sounds like a perfectly valid usecase to me, create a ticket on jira.codehaus.org/browse/MRELEASE in case nobody else chips in here. Jorg On 6/6/06, Dario Luis Coneglian Oliveros <[EMAIL PROTECTED]> wrote: Hi there, I've been trying to use maven-release-plugin to prepare a release, but whenever I do that, it fails since I have a SVN precommit hook that integrates with an issue tracking system which in turn waits for a comment containing an issue number. Since release plugin adds its own comment, such as "[maven-release-plugin] prepare release ...", this integration fails. So I was wondering if this could be prompted in the same way for the release and next development iteration versions. How about that ? Please let me know any comments on this. Thanks, Dário - 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] maven-release-plugin: how about a prompt for customizing commit comment during release preparation ?
Sounds like a perfectly valid usecase to me, create a ticket on jira.codehaus.org/browse/MRELEASE in case nobody else chips in here. Jorg On 6/6/06, Dario Luis Coneglian Oliveros <[EMAIL PROTECTED]> wrote: Hi there, I've been trying to use maven-release-plugin to prepare a release, but whenever I do that, it fails since I have a SVN precommit hook that integrates with an issue tracking system which in turn waits for a comment containing an issue number. Since release plugin adds its own comment, such as "[maven-release-plugin] prepare release ...", this integration fails. So I was wondering if this could be prompted in the same way for the release and next development iteration versions. How about that ? Please let me know any comments on this. Thanks, Dário - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [maven-release-plugin] Unknown file status: 'X' as a result of 'mvn release:prepare'
http://jira.codehaus.org/browse/SCM-208 Mike Perham a écrit : Yes, you need to enter a JIRA bug in the Maven SCM project with this detail. -Original Message- From: Dario Luis Coneglian Oliveros [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 2:53 PM To: Maven Users List Subject: [m2] [maven-release-plugin] Unknown file status: 'X' as a result of 'mvn release:prepare' I've been trying to make a release by running 'mvn release:prepare', but got a warning saying that 'X' is an unknown file status. I noticed the release plugin runs the 'svn --non-interactive status' command internally which prints the status of working copy files and directories. Since one of the directories was fetched from a different svn repo thru svn:externals, its status is 'X' and it does not seem to be recognized by the release plugin. Therefore the outcome of 'mvn release:prepare' command is a build failure. Any ideas or comments ? Should I file a JIRA issue ? Thanks, Dário - 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] [maven-release-plugin] Unknown file status: 'X' as a result of 'mvn release:prepare'
Yes, you need to enter a JIRA bug in the Maven SCM project with this detail. -Original Message- From: Dario Luis Coneglian Oliveros [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 2:53 PM To: Maven Users List Subject: [m2] [maven-release-plugin] Unknown file status: 'X' as a result of 'mvn release:prepare' I've been trying to make a release by running 'mvn release:prepare', but got a warning saying that 'X' is an unknown file status. I noticed the release plugin runs the 'svn --non-interactive status' command internally which prints the status of working copy files and directories. Since one of the directories was fetched from a different svn repo thru svn:externals, its status is 'X' and it does not seem to be recognized by the release plugin. Therefore the outcome of 'mvn release:prepare' command is a build failure. Any ideas or comments ? Should I file a JIRA issue ? Thanks, Dário - 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] : maven-release-plugin - about what ?
Thanks Michael! It is really helpful ;-) Regards, Jaikumar -Original Message- From: Michael Meyer [mailto:[EMAIL PROTECTED] Sent: Friday, April 28, 2006 5:44 PM To: Maven Users List Subject: Re: [M2] : maven-release-plugin - about what ? Hi Jaikumar, the functionality of the release plugin is described here: http://maven.apache.org/plugins/maven-release-plugin/introduction.html The plugin assumes that you use a scm system like Subversion or cvs and have got an internal repository in your company for releases. Assume your project has got version 1.2-SNAPSHOT and you think its time to make this version of the project available to others. So you run the release plugin. The plugin will add a tag to your scm (for example 1.2), will create the artifact (for example my-project-1.2.jar) and will upload the artifact to your internal repository. It will also create additional pom and checksum files in your internal repository. Others can now use your released version as dependency in their project. Hope this helps. If I missed the point of the question i apologise ;-) Cheers, michael Sharma, Jaikumar schrieb: > Dear Maven Users. > > What is the purpose of maven-release-plugin ? what features basically > it provides ? I did not find right info about this plugin on Maven > website. Thanks for your help! > > Regards, Jaikumar > > - - - - - - - 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 liablility 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] - - - - - - - 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 liablility for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
RE : [M2] : maven-release-plugin - about what ?
Look at this great link :
http://apollo.ucalgary.ca/tlcprojectswiki/index.php/Public/Project_Versi
oning_-_Best_Practices
-Olivier
-Message d'origine-
De : Michael Meyer [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 28 avril 2006 14:14
À : Maven Users List
Objet : Re: [M2] : maven-release-plugin - about what ?
Hi Jaikumar,
the functionality of the release plugin is described here:
http://maven.apache.org/plugins/maven-release-plugin/introduction.html
The plugin assumes that you use a scm system like Subversion or cvs and
have got an internal repository in your company for releases.
Assume your project has got version 1.2-SNAPSHOT and you think its time
to make this version of the project available to others. So you run the
release plugin. The plugin will add a tag to your scm (for example 1.2),
will create the artifact (for example my-project-1.2.jar) and will
upload the artifact to your internal repository. It will also create
additional pom and checksum files in your internal repository.
Others can now use your released version as dependency in their project.
Hope this helps. If I missed the point of the question i apologise ;-)
Cheers,
michael
Sharma, Jaikumar schrieb:
> Dear Maven Users.
>
> What is the purpose of maven-release-plugin ? what features basically
> it provides ? I did not find right info about this plugin on Maven
> website. Thanks for your help!
>
> Regards, Jaikumar
>
> - - - - - - - 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 liablility 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]
This e-mail, any attachments and the information contained therein ("this
message") are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après "le message" ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] : maven-release-plugin - about what ?
Hi Jaikumar, the functionality of the release plugin is described here: http://maven.apache.org/plugins/maven-release-plugin/introduction.html The plugin assumes that you use a scm system like Subversion or cvs and have got an internal repository in your company for releases. Assume your project has got version 1.2-SNAPSHOT and you think its time to make this version of the project available to others. So you run the release plugin. The plugin will add a tag to your scm (for example 1.2), will create the artifact (for example my-project-1.2.jar) and will upload the artifact to your internal repository. It will also create additional pom and checksum files in your internal repository. Others can now use your released version as dependency in their project. Hope this helps. If I missed the point of the question i apologise ;-) Cheers, michael Sharma, Jaikumar schrieb: Dear Maven Users. What is the purpose of maven-release-plugin ? what features basically it provides ? I did not find right info about this plugin on Maven website. Thanks for your help! Regards, Jaikumar - - - - - - - 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 liablility 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: [M2] maven-release-plugin
Gabriel, Andreas a écrit : Hi! I somehow don't manage to get the maven-release-plugin running with CVS. When I run the mvn release:prepare target, the plugin complains "password is required" when verifying that no local changes were made. I found out, that the plugin is ignoring the "-D project.scm.developerConnection" and uses the connection specified in the pom.xml file (should'nt it be possible to override this with the -D option?). Anyway updating the release.properties file after executing the command once solves this problem. Why don't you want use developerConnection defined in your pom? After that I ran into the next problem: My project needs a plugin that is still in development and therefore includes a SNAPSHOT version in the build section (build-helper-maven-plugin). The release plugin complains "Can't release project due to non released dependencies - org.codehaus.mojo:build-helper-maven-plugin:maven-plugin:1.0-SNAPSHOT". I understand that the plugin does not allow SNAPSHOT dependencies, but why doesn't it allow SNAPSHOT build plugins? Is there any possibility to ignore some dependencies? Snaphot versions aren't allowed because it's possible that the build won't be reproductible. If you want to use this version, try this : - Remove the plugin version from your pom, (this version will be use if it install locally and it's the more recent) - remove your release.properties - restart the release process My configuration is the following: WinXP, JDK 1.5.0_6, Maven 2.0.2, maven-release-plugin 2.0-beta-3 and 2.0-beta-4-SNAPSHOT, CVSNT. Regards, Andreas *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] maven-release-plugin
On 2/13/06, Gabriel, Andreas <[EMAIL PROTECTED]> wrote: > > > Hi! > > > > I somehow don't manage to get the maven-release-plugin running with CVS. > When I run the mvn release:prepare target, the plugin complains > "password is required" when verifying that no local changes were made. I > found out, that the plugin is ignoring the "-D > project.scm.developerConnection" and uses the connection specified in > the pom.xml file (should'nt it be possible to override this with the -D > option?). Anyway updating the release.properties file after executing > the command once solves this problem. Please check the archive, there is work around for your specific problem. After that I ran into the next problem: My project needs a plugin that > is still in development and therefore includes a SNAPSHOT version in the > build section (build-helper-maven-plugin). The release plugin complains > "Can't release project due to non released dependencies - > org.codehaus.mojo:build-helper-maven-plugin:maven-plugin:1.0-SNAPSHOT". > I understand that the plugin does not allow SNAPSHOT dependencies, but > why doesn't it allow SNAPSHOT build plugins? Is there any possibility to > ignore some dependencies? build-helper-maven-plugin-1.0 released today. However, if you'd like to use plugin snapshot when doing the release: 1. Remove plugin version 2. Locally build the plugin so that maven will use SNAPSHOT plugin at run time Or, cut a release yourself and place them in your internal repository. I use the svn revision number as the release number ( ie 1.0-svn-revision ) so that I can track. My configuration is the following: WinXP, JDK 1.5.0_6, Maven 2.0.2, > maven-release-plugin 2.0-beta-3 and 2.0-beta-4-SNAPSHOT, CVSNT. > > > > Regards, > > Andreas -Dan *** > The information in this email is confidential and may be legally > privileged. Access to this email by anyone other than the intended > addressee is unauthorized. If you are not the intended recipient of this > message, any review, disclosure, copying, distribution, retention, or any > action taken or omitted to be taken in reliance on it is prohibited and may > be unlawful. If you are not the intended recipient, please reply to or > forward a copy of this message to the sender and delete the message, any > attachments, and any copies thereof from your system. > > *** >
Re: [M2] - maven-release-plugin cannot load SCM provider
I just thought I would send a quick email mentioning that I have attached an update to the content of the "Guide to Releasing" mini guide. The following issue was raised to keep track of the update. http://jira.codehaus.org/browse/MNG-1564 Any feedback would be great. Hope this helps Trent On 10/11/05, Jason van Zyl <[EMAIL PROTECTED]> wrote: > On Thu, 2005-11-10 at 00:20 +, Trent Rosenbaum wrote: > > I would be more than happy to help out with any documentation. > > What is the process for improving documents? Write something then attach > > it to > > a jira issue to it can be picked up? > > Yes, there are several components for documentation. > > > Trent > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > No problem. Perhaps you could help reword the docs to make it clearer > > > what tagBase does/is? > > > > > > - Brett > > > > > > On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > Brett thanks for taking the time to look into my issues with the > > > > maven-release plugin. > > > > I was able to deploy a release locally. I just thought that because > > > > their was a jira issue with the tagBase property for the plugin I > > > > should be putting the whole URL with the prexfix because the URL > > > > specified int he developerConnection is being used to construct the > > > > tag URL. > > > > > > > > Trent > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > Ah, sorry for the confusion. > > > > > > > > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as > > > > > it is an SVN specific property. > > > > > > > > > > - Brett > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > This is the feedback I got from running mvn release:prepare > > > > > > > > > > > > [INFO] [release:prepare] > > > > > > [INFO] What tag name should be used? > > > > > > 0.1.2 > > > > > > [INFO] Tagging release with the label 0.1.2. > > > > > > Provider message: > > > > > > The svn tag command failed. > > > > > > Command output: > > > > > > svn: Error resolving case of > > > > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > > > > > s\my_repo\bug-control-model\tags\0.1.2' > > > > > > > > > > > > [INFO] > > > > > > - > > > > > > --- > > > > > > [ERROR] BUILD ERROR > > > > > > [INFO] > > > > > > - > > > > > > --- > > > > > > [INFO] An error is occurred in the tag process. > > > > > > > > > > > > > > > > > > The URL for the tagBase is identical to the URL supplied within the > > > > > > developerConnection element but "tags" replaces "trunk". > > > > > > > > > > > > Trent > > > > > > > > > > > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > The bug is for the default of ../tags when used instead of a > > > > > > > tagbase > > > > > > > as you have, so it is different. > > > > > > > > > > > > > > Above that exception, there should have been output from the svn > > > > > > > command. Does that reveal anything? > > > > > > > > > > > > > > - Brett > > > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > > I did not have this pom.xml checked into SVN and so it was > > > > > > > > trying to > > > > > > > > work with the previous revision of my file and this did not > > > > > > > > have a SCM > > > > > > > > URL defined. I have been able to get the plugin to prompt me > > > > > > > > for > > > > > > > > input regarding the tags, but I am falling over in the tagging > > > > > > > > process > > > > > > > > with the following exception: > > > > > > > > > > > > > > > > Is this the same exception that has lead to the creation of the > > > > > > > > following issue in jira? > > > > > > > > > > > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > > > > > > > > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An > > > > > > > > error is occurred in > > > > > > > > the tag process. > > > > > > > > > > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An > > > > > > > > error is occurred > > > > > > > > in the tag process. > > > > > > > > at > > > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > > > > > > eReleaseMojo.java:1414) > > > > > > > > at > > > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > > > > > > leaseMojo.java:246) > > > > > > > > > > > > > > > > > > > > > > > > thanks for taking to time to look into this. > > > > > > > > Trent > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > > I thought I had used windows paths in the SCM URL before > > > > > > > > > without > > > > > > > > > issues, but its worth trying: > > > > > > > > > > > > > > > > > > scm|svn|file:///d:/subversion... > > > >
RE: [M2] - maven-release-plugin cannot load SCM provider
If I may suggest, what has worked for me in the past is to patch an existing document file (they are in subversion) and attach to a JIRA like you said. This makes is easier on the committers to review and apply - a patch. > -Original Message- > From: Trent Rosenbaum [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 09, 2005 6:21 PM > To: Maven Users List > Subject: Re: [M2] - maven-release-plugin cannot load SCM provider > > I would be more than happy to help out with any documentation. > What is the process for improving documents? Write something > then attach it to a jira issue to it can be picked up? > > Trent > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > No problem. Perhaps you could help reword the docs to make > it clearer > > what tagBase does/is? > > > > - Brett > > > > On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > Brett thanks for taking the time to look into my issues with the > > > maven-release plugin. > > > I was able to deploy a release locally. I just thought > that because > > > their was a jira issue with the tagBase property for the plugin I > > > should be putting the whole URL with the prexfix because the URL > > > specified int he developerConnection is being used to > construct the > > > tag URL. > > > > > > Trent > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Ah, sorry for the confusion. > > > > > > > > nulike the connections, tagBase is just the SVN URL > (omit scm:svn) > > > > as it is an SVN specific property. > > > > > > > > - Brett > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > This is the feedback I got from running mvn release:prepare > > > > > > > > > > [INFO] [release:prepare] > > > > > [INFO] What tag name should be used? > > > > > 0.1.2 > > > > > [INFO] Tagging release with the label 0.1.2. > > > > > Provider message: > > > > > The svn tag command failed. > > > > > Command output: > > > > > svn: Error resolving case of > > > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > > > > s\my_repo\bug-control-model\tags\0.1.2' > > > > > > > > > > [INFO] > > > > > > > > > > > - > > > > > --- > > > > > [ERROR] BUILD ERROR > > > > > [INFO] > > > > > > > > > > > - > > > > > --- > > > > > [INFO] An error is occurred in the tag process. > > > > > > > > > > > > > > > The URL for the tagBase is identical to the URL > supplied within > > > > > the developerConnection element but "tags" replaces "trunk". > > > > > > > > > > Trent > > > > > > > > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > The bug is for the default of ../tags when used > instead of a > > > > > > tagbase as you have, so it is different. > > > > > > > > > > > > Above that exception, there should have been output > from the > > > > > > svn command. Does that reveal anything? > > > > > > > > > > > > - Brett > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum > <[EMAIL PROTECTED]> wrote: > > > > > > > I did not have this pom.xml checked into SVN and > so it was > > > > > > > trying to work with the previous revision of my file and > > > > > > > this did not have a SCM URL defined. I have been able to > > > > > > > get the plugin to prompt me for input regarding the tags, > > > > > > > but I am falling over in the tagging process with > the following exception: > > > > > > > > > > > > > > Is this the same exception that has lead to the > creation of > > > > > > > the following issue in jira? > > > > > > > > > > > > > > http://jira.codehaus.org/brows
Re: [M2] - maven-release-plugin cannot load SCM provider
On Thu, 2005-11-10 at 00:20 +, Trent Rosenbaum wrote: > I would be more than happy to help out with any documentation. > What is the process for improving documents? Write something then attach it > to > a jira issue to it can be picked up? Yes, there are several components for documentation. > Trent > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > No problem. Perhaps you could help reword the docs to make it clearer > > what tagBase does/is? > > > > - Brett > > > > On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > Brett thanks for taking the time to look into my issues with the > > > maven-release plugin. > > > I was able to deploy a release locally. I just thought that because > > > their was a jira issue with the tagBase property for the plugin I > > > should be putting the whole URL with the prexfix because the URL > > > specified int he developerConnection is being used to construct the > > > tag URL. > > > > > > Trent > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Ah, sorry for the confusion. > > > > > > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as > > > > it is an SVN specific property. > > > > > > > > - Brett > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > This is the feedback I got from running mvn release:prepare > > > > > > > > > > [INFO] [release:prepare] > > > > > [INFO] What tag name should be used? > > > > > 0.1.2 > > > > > [INFO] Tagging release with the label 0.1.2. > > > > > Provider message: > > > > > The svn tag command failed. > > > > > Command output: > > > > > svn: Error resolving case of > > > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > > > > s\my_repo\bug-control-model\tags\0.1.2' > > > > > > > > > > [INFO] > > > > > - > > > > > --- > > > > > [ERROR] BUILD ERROR > > > > > [INFO] > > > > > - > > > > > --- > > > > > [INFO] An error is occurred in the tag process. > > > > > > > > > > > > > > > The URL for the tagBase is identical to the URL supplied within the > > > > > developerConnection element but "tags" replaces "trunk". > > > > > > > > > > Trent > > > > > > > > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > The bug is for the default of ../tags when used instead of a tagbase > > > > > > as you have, so it is different. > > > > > > > > > > > > Above that exception, there should have been output from the svn > > > > > > command. Does that reveal anything? > > > > > > > > > > > > - Brett > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > I did not have this pom.xml checked into SVN and so it was > > > > > > > trying to > > > > > > > work with the previous revision of my file and this did not have > > > > > > > a SCM > > > > > > > URL defined. I have been able to get the plugin to prompt me for > > > > > > > input regarding the tags, but I am falling over in the tagging > > > > > > > process > > > > > > > with the following exception: > > > > > > > > > > > > > > Is this the same exception that has lead to the creation of the > > > > > > > following issue in jira? > > > > > > > > > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > > > > > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error > > > > > > > is occurred in > > > > > > > the tag process. > > > > > > > > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An > > > > > > > error is occurred > > > > > > > in the tag process. > > > > > > > at > > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > > > > > eReleaseMojo.java:1414) > > > > > > > at > > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > > > > > leaseMojo.java:246) > > > > > > > > > > > > > > > > > > > > > thanks for taking to time to look into this. > > > > > > > Trent > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > I thought I had used windows paths in the SCM URL before without > > > > > > > > issues, but its worth trying: > > > > > > > > > > > > > > > > scm|svn|file:///d:/subversion... > > > > > > > > > > > > > > > > hth, > > > > > > > > Brett > > > > > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > > > This is the SCM URL for the project: > > > > > > > > > > > > > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > > > > > > > > > > > > > > > > and the plugin is configured with the following tagbase > > > > > > > > > element: > > > > > > > > > > > > > > > > > > > > > > > > > > > org.apache.maven.plugins > > > > > > > > > maven-release-plugin > > > > > > > > > 2.0-beta-3 >
Re: [M2] - maven-release-plugin cannot load SCM provider
I would be more than happy to help out with any documentation. What is the process for improving documents? Write something then attach it to a jira issue to it can be picked up? Trent On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > No problem. Perhaps you could help reword the docs to make it clearer > what tagBase does/is? > > - Brett > > On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > Brett thanks for taking the time to look into my issues with the > > maven-release plugin. > > I was able to deploy a release locally. I just thought that because > > their was a jira issue with the tagBase property for the plugin I > > should be putting the whole URL with the prexfix because the URL > > specified int he developerConnection is being used to construct the > > tag URL. > > > > Trent > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > Ah, sorry for the confusion. > > > > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as > > > it is an SVN specific property. > > > > > > - Brett > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > This is the feedback I got from running mvn release:prepare > > > > > > > > [INFO] [release:prepare] > > > > [INFO] What tag name should be used? > > > > 0.1.2 > > > > [INFO] Tagging release with the label 0.1.2. > > > > Provider message: > > > > The svn tag command failed. > > > > Command output: > > > > svn: Error resolving case of > > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > > > s\my_repo\bug-control-model\tags\0.1.2' > > > > > > > > [INFO] > > > > - > > > > --- > > > > [ERROR] BUILD ERROR > > > > [INFO] > > > > - > > > > --- > > > > [INFO] An error is occurred in the tag process. > > > > > > > > > > > > The URL for the tagBase is identical to the URL supplied within the > > > > developerConnection element but "tags" replaces "trunk". > > > > > > > > Trent > > > > > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > The bug is for the default of ../tags when used instead of a tagbase > > > > > as you have, so it is different. > > > > > > > > > > Above that exception, there should have been output from the svn > > > > > command. Does that reveal anything? > > > > > > > > > > - Brett > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > I did not have this pom.xml checked into SVN and so it was trying > > > > > > to > > > > > > work with the previous revision of my file and this did not have a > > > > > > SCM > > > > > > URL defined. I have been able to get the plugin to prompt me for > > > > > > input regarding the tags, but I am falling over in the tagging > > > > > > process > > > > > > with the following exception: > > > > > > > > > > > > Is this the same exception that has lead to the creation of the > > > > > > following issue in jira? > > > > > > > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is > > > > > > occurred in > > > > > > the tag process. > > > > > > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error > > > > > > is occurred > > > > > > in the tag process. > > > > > > at > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > > > > eReleaseMojo.java:1414) > > > > > > at > > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > > > > leaseMojo.java:246) > > > > > > > > > > > > > > > > > > thanks for taking to time to look into this. > > > > > > Trent > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > I thought I had used windows paths in the SCM URL before without > > > > > > > issues, but its worth trying: > > > > > > > > > > > > > > scm|svn|file:///d:/subversion... > > > > > > > > > > > > > > hth, > > > > > > > Brett > > > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > > This is the SCM URL for the project: > > > > > > > > > > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > > > > > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > > > > > > > > > > > > > > > > org.apache.maven.plugins > > > > > > > > maven-release-plugin > > > > > > > > 2.0-beta-3 > > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > > They both use the same library - so the release plugin is for > > > > > > > > > automating release related tasks,
Re: [M2] - maven-release-plugin cannot load SCM provider
No problem. Perhaps you could help reword the docs to make it clearer what tagBase does/is? - Brett On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > Brett thanks for taking the time to look into my issues with the > maven-release plugin. > I was able to deploy a release locally. I just thought that because > their was a jira issue with the tagBase property for the plugin I > should be putting the whole URL with the prexfix because the URL > specified int he developerConnection is being used to construct the > tag URL. > > Trent > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Ah, sorry for the confusion. > > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as > > it is an SVN specific property. > > > > - Brett > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > This is the feedback I got from running mvn release:prepare > > > > > > [INFO] [release:prepare] > > > [INFO] What tag name should be used? > > > 0.1.2 > > > [INFO] Tagging release with the label 0.1.2. > > > Provider message: > > > The svn tag command failed. > > > Command output: > > > svn: Error resolving case of > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > > s\my_repo\bug-control-model\tags\0.1.2' > > > > > > [INFO] > > > - > > > --- > > > [ERROR] BUILD ERROR > > > [INFO] > > > - > > > --- > > > [INFO] An error is occurred in the tag process. > > > > > > > > > The URL for the tagBase is identical to the URL supplied within the > > > developerConnection element but "tags" replaces "trunk". > > > > > > Trent > > > > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > The bug is for the default of ../tags when used instead of a tagbase > > > > as you have, so it is different. > > > > > > > > Above that exception, there should have been output from the svn > > > > command. Does that reveal anything? > > > > > > > > - Brett > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > I did not have this pom.xml checked into SVN and so it was trying to > > > > > work with the previous revision of my file and this did not have a SCM > > > > > URL defined. I have been able to get the plugin to prompt me for > > > > > input regarding the tags, but I am falling over in the tagging process > > > > > with the following exception: > > > > > > > > > > Is this the same exception that has lead to the creation of the > > > > > following issue in jira? > > > > > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is > > > > > occurred in > > > > > the tag process. > > > > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error > > > > > is occurred > > > > > in the tag process. > > > > > at > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > > > eReleaseMojo.java:1414) > > > > > at > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > > > leaseMojo.java:246) > > > > > > > > > > > > > > > thanks for taking to time to look into this. > > > > > Trent > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > I thought I had used windows paths in the SCM URL before without > > > > > > issues, but its worth trying: > > > > > > > > > > > > scm|svn|file:///d:/subversion... > > > > > > > > > > > > hth, > > > > > > Brett > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > This is the SCM URL for the project: > > > > > > > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > > > > > > > > > > > > > org.apache.maven.plugins > > > > > > > maven-release-plugin > > > > > > > 2.0-beta-3 > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > They both use the same library - so the release plugin is for > > > > > > > > automating release related tasks, the scm plugin for development > > > > > > > > related tasks. > > > > > > > > > > > > > > > > Can you please repost the full SCM URL that gave you this error > > > > > > > > - > > > > > > > > there is still something wrong with it. > > > > > > > > > > > > > > > > - Brett > > > > > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > > > Thanks for the reply. > > > > > > > > > When I started to use the plugin I was prefixing the URLs with > > > > > > > > > "scm:svn", but then I still h
Re: [M2] - maven-release-plugin cannot load SCM provider
Brett thanks for taking the time to look into my issues with the maven-release plugin. I was able to deploy a release locally. I just thought that because their was a jira issue with the tagBase property for the plugin I should be putting the whole URL with the prexfix because the URL specified int he developerConnection is being used to construct the tag URL. Trent On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Ah, sorry for the confusion. > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as > it is an SVN specific property. > > - Brett > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > This is the feedback I got from running mvn release:prepare > > > > [INFO] [release:prepare] > > [INFO] What tag name should be used? > > 0.1.2 > > [INFO] Tagging release with the label 0.1.2. > > Provider message: > > The svn tag command failed. > > Command output: > > svn: Error resolving case of > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > > s\my_repo\bug-control-model\tags\0.1.2' > > > > [INFO] > > - > > --- > > [ERROR] BUILD ERROR > > [INFO] > > - > > --- > > [INFO] An error is occurred in the tag process. > > > > > > The URL for the tagBase is identical to the URL supplied within the > > developerConnection element but "tags" replaces "trunk". > > > > Trent > > > > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > The bug is for the default of ../tags when used instead of a tagbase > > > as you have, so it is different. > > > > > > Above that exception, there should have been output from the svn > > > command. Does that reveal anything? > > > > > > - Brett > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > I did not have this pom.xml checked into SVN and so it was trying to > > > > work with the previous revision of my file and this did not have a SCM > > > > URL defined. I have been able to get the plugin to prompt me for > > > > input regarding the tags, but I am falling over in the tagging process > > > > with the following exception: > > > > > > > > Is this the same exception that has lead to the creation of the > > > > following issue in jira? > > > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is > > > > occurred in > > > > the tag process. > > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > > > > occurred > > > > in the tag process. > > > > at > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > > eReleaseMojo.java:1414) > > > > at > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > > leaseMojo.java:246) > > > > > > > > > > > > thanks for taking to time to look into this. > > > > Trent > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > I thought I had used windows paths in the SCM URL before without > > > > > issues, but its worth trying: > > > > > > > > > > scm|svn|file:///d:/subversion... > > > > > > > > > > hth, > > > > > Brett > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > This is the SCM URL for the project: > > > > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > > > > > > > > > > org.apache.maven.plugins > > > > > > maven-release-plugin > > > > > > 2.0-beta-3 > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > They both use the same library - so the release plugin is for > > > > > > > automating release related tasks, the scm plugin for development > > > > > > > related tasks. > > > > > > > > > > > > > > Can you please repost the full SCM URL that gave you this error - > > > > > > > there is still something wrong with it. > > > > > > > > > > > > > > - Brett > > > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > > Thanks for the reply. > > > > > > > > When I started to use the plugin I was prefixing the URLs with > > > > > > > > "scm:svn", but then I still had a problem so thought about > > > > > > > > exploring > > > > > > > > and that is why I asked about setting the scm provider in a > > > > > > > > different > > > > > > > > manner. I have again used these prefixes and I still get a > > > > > > > > problem. > > > > > > > > Maven gave me the follow stacktrace below. I am using > > > > > > > > 2.0-beta-3 of the plugin. > > > > > > > > > > > > > > > > During my reading of the
Re: [M2] - maven-release-plugin cannot load SCM provider
Ah, sorry for the confusion. nulike the connections, tagBase is just the SVN URL (omit scm:svn) as it is an SVN specific property. - Brett On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > This is the feedback I got from running mvn release:prepare > > [INFO] [release:prepare] > [INFO] What tag name should be used? > 0.1.2 > [INFO] Tagging release with the label 0.1.2. > Provider message: > The svn tag command failed. > Command output: > svn: Error resolving case of > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie > s\my_repo\bug-control-model\tags\0.1.2' > > [INFO] > - > --- > [ERROR] BUILD ERROR > [INFO] > - > --- > [INFO] An error is occurred in the tag process. > > > The URL for the tagBase is identical to the URL supplied within the > developerConnection element but "tags" replaces "trunk". > > Trent > > > On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > The bug is for the default of ../tags when used instead of a tagbase > > as you have, so it is different. > > > > Above that exception, there should have been output from the svn > > command. Does that reveal anything? > > > > - Brett > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > I did not have this pom.xml checked into SVN and so it was trying to > > > work with the previous revision of my file and this did not have a SCM > > > URL defined. I have been able to get the plugin to prompt me for > > > input regarding the tags, but I am falling over in the tagging process > > > with the following exception: > > > > > > Is this the same exception that has lead to the creation of the > > > following issue in jira? > > > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is > > > occurred in > > > the tag process. > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > > > occurred > > > in the tag process. > > > at > > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > > eReleaseMojo.java:1414) > > > at > > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > > leaseMojo.java:246) > > > > > > > > > thanks for taking to time to look into this. > > > Trent > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > I thought I had used windows paths in the SCM URL before without > > > > issues, but its worth trying: > > > > > > > > scm|svn|file:///d:/subversion... > > > > > > > > hth, > > > > Brett > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > This is the SCM URL for the project: > > > > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > > > > > > > org.apache.maven.plugins > > > > > maven-release-plugin > > > > > 2.0-beta-3 > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > They both use the same library - so the release plugin is for > > > > > > automating release related tasks, the scm plugin for development > > > > > > related tasks. > > > > > > > > > > > > Can you please repost the full SCM URL that gave you this error - > > > > > > there is still something wrong with it. > > > > > > > > > > > > - Brett > > > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > > Thanks for the reply. > > > > > > > When I started to use the plugin I was prefixing the URLs with > > > > > > > "scm:svn", but then I still had a problem so thought about > > > > > > > exploring > > > > > > > and that is why I asked about setting the scm provider in a > > > > > > > different > > > > > > > manner. I have again used these prefixes and I still get a > > > > > > > problem. > > > > > > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 > > > > > > > of the plugin. > > > > > > > > > > > > > > During my reading of the site I noticed that both the scm and the > > > > > > > release plugin are similar. Is it right to think that the > > > > > > > maven-scm > > > > > > > plugin is planned to allow developers to aquire a project without > > > > > > > a > > > > > > > pom.xml and then to complete the every day version control tasks? > > > > > > > With this in mind is it best to view the maven-release plugin as a > > > > > > > component that should be used to release code for a repository > > > > > > > instead > > > > > > > of completing a checkout/checkin, copy etc manually? I just want > > > > > > > to > > > > > > > know the thoughts behind each plugin. > > > > > > > > > > > > > > ---
Re: [M2] - maven-release-plugin cannot load SCM provider
This is the feedback I got from running mvn release:prepare [INFO] [release:prepare] [INFO] What tag name should be used? 0.1.2 [INFO] Tagging release with the label 0.1.2. Provider message: The svn tag command failed. Command output: svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie s\my_repo\bug-control-model\tags\0.1.2' [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] An error is occurred in the tag process. The URL for the tagBase is identical to the URL supplied within the developerConnection element but "tags" replaces "trunk". Trent On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > The bug is for the default of ../tags when used instead of a tagbase > as you have, so it is different. > > Above that exception, there should have been output from the svn > command. Does that reveal anything? > > - Brett > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > I did not have this pom.xml checked into SVN and so it was trying to > > work with the previous revision of my file and this did not have a SCM > > URL defined. I have been able to get the plugin to prompt me for > > input regarding the tags, but I am falling over in the tagging process > > with the following exception: > > > > Is this the same exception that has lead to the creation of the > > following issue in jira? > > > > http://jira.codehaus.org/browse/MNG-883 > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is > > occurred in > > the tag process. > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > > occurred > > in the tag process. > > at > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > > eReleaseMojo.java:1414) > > at > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > > leaseMojo.java:246) > > > > > > thanks for taking to time to look into this. > > Trent > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > I thought I had used windows paths in the SCM URL before without > > > issues, but its worth trying: > > > > > > scm|svn|file:///d:/subversion... > > > > > > hth, > > > Brett > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > This is the SCM URL for the project: > > > > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > > > > org.apache.maven.plugins > > > > maven-release-plugin > > > > 2.0-beta-3 > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > They both use the same library - so the release plugin is for > > > > > automating release related tasks, the scm plugin for development > > > > > related tasks. > > > > > > > > > > Can you please repost the full SCM URL that gave you this error - > > > > > there is still something wrong with it. > > > > > > > > > > - Brett > > > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > > Thanks for the reply. > > > > > > When I started to use the plugin I was prefixing the URLs with > > > > > > "scm:svn", but then I still had a problem so thought about exploring > > > > > > and that is why I asked about setting the scm provider in a > > > > > > different > > > > > > manner. I have again used these prefixes and I still get a problem. > > > > > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 > > > > > > of the plugin. > > > > > > > > > > > > During my reading of the site I noticed that both the scm and the > > > > > > release plugin are similar. Is it right to think that the maven-scm > > > > > > plugin is planned to allow developers to aquire a project without a > > > > > > pom.xml and then to complete the every day version control tasks? > > > > > > With this in mind is it best to view the maven-release plugin as a > > > > > > component that should be used to release code for a repository > > > > > > instead > > > > > > of completing a checkout/checkin, copy etc manually? I just want to > > > > > > know the thoughts behind each plugin. > > > > > > > > > > > > - Maven output - > > > > > > > > > > > > [ERROR] BUILD ERROR > > > > > > [INFO] > > > > > > --- > > > > > > [INFO] An error is occurred in the status process. > > > > > > > > > > > > Embedded error: Can't load the scm provider. > > > > > > The scm url is invalid. > > > > > > > > > > > > - stack trace -- > > > > > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm > > > > > > provider. > > > > > > at > > > > > > org.a
Re: [M2] - maven-release-plugin cannot load SCM provider
The bug is for the default of ../tags when used instead of a tagbase as you have, so it is different. Above that exception, there should have been output from the svn command. Does that reveal anything? - Brett On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > I did not have this pom.xml checked into SVN and so it was trying to > work with the previous revision of my file and this did not have a SCM > URL defined. I have been able to get the plugin to prompt me for > input regarding the tags, but I am falling over in the tagging process > with the following exception: > > Is this the same exception that has lead to the creation of the > following issue in jira? > > http://jira.codehaus.org/browse/MNG-883 > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred > in > the tag process. > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > occurred > in the tag process. > at > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar > eReleaseMojo.java:1414) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe > leaseMojo.java:246) > > > thanks for taking to time to look into this. > Trent > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > I thought I had used windows paths in the SCM URL before without > > issues, but its worth trying: > > > > scm|svn|file:///d:/subversion... > > > > hth, > > Brett > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > This is the SCM URL for the project: > > > > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > > > > and the plugin is configured with the following tagbase element: > > > > > > > > > org.apache.maven.plugins > > > maven-release-plugin > > > 2.0-beta-3 > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > They both use the same library - so the release plugin is for > > > > automating release related tasks, the scm plugin for development > > > > related tasks. > > > > > > > > Can you please repost the full SCM URL that gave you this error - > > > > there is still something wrong with it. > > > > > > > > - Brett > > > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > > Thanks for the reply. > > > > > When I started to use the plugin I was prefixing the URLs with > > > > > "scm:svn", but then I still had a problem so thought about exploring > > > > > and that is why I asked about setting the scm provider in a different > > > > > manner. I have again used these prefixes and I still get a problem. > > > > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of > > > > > the plugin. > > > > > > > > > > During my reading of the site I noticed that both the scm and the > > > > > release plugin are similar. Is it right to think that the maven-scm > > > > > plugin is planned to allow developers to aquire a project without a > > > > > pom.xml and then to complete the every day version control tasks? > > > > > With this in mind is it best to view the maven-release plugin as a > > > > > component that should be used to release code for a repository instead > > > > > of completing a checkout/checkin, copy etc manually? I just want to > > > > > know the thoughts behind each plugin. > > > > > > > > > > - Maven output - > > > > > > > > > > [ERROR] BUILD ERROR > > > > > [INFO] > > > > > --- > > > > > [INFO] An error is occurred in the status process. > > > > > > > > > > Embedded error: Can't load the scm provider. > > > > > The scm url is invalid. > > > > > > > > > > - stack trace -- > > > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm > > > > > provider. > > > > > at > > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > > > cmHelper.java:104) > > > > > at > > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe > > > > > r.java:169) > > > > > at > > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi > > > > > fications(PrepareReleaseMojo.java:510) > > > > > ... 19 more > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: > > > > > The scm url i > > > > > s invalid. > > > > > at > > > > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos > > > > > itory(SvnScmProvider.java:84) > > > > > at > > > > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito > > > > > ry(DefaultScmManager.java:126) > > > > > at > > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > > > cmHelper.java:82) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL
Re: [M2] - maven-release-plugin cannot load SCM provider
I did not have this pom.xml checked into SVN and so it was trying to work with the previous revision of my file and this did not have a SCM URL defined. I have been able to get the plugin to prompt me for input regarding the tags, but I am falling over in the tagging process with the following exception: Is this the same exception that has lead to the creation of the following issue in jira? http://jira.codehaus.org/browse/MNG-883 org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the tag process. Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the tag process. at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar eReleaseMojo.java:1414) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe leaseMojo.java:246) thanks for taking to time to look into this. Trent On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > I thought I had used windows paths in the SCM URL before without > issues, but its worth trying: > > scm|svn|file:///d:/subversion... > > hth, > Brett > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > This is the SCM URL for the project: > > > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > > > > and the plugin is configured with the following tagbase element: > > > > > > org.apache.maven.plugins > > maven-release-plugin > > 2.0-beta-3 > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > They both use the same library - so the release plugin is for > > > automating release related tasks, the scm plugin for development > > > related tasks. > > > > > > Can you please repost the full SCM URL that gave you this error - > > > there is still something wrong with it. > > > > > > - Brett > > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > > Thanks for the reply. > > > > When I started to use the plugin I was prefixing the URLs with > > > > "scm:svn", but then I still had a problem so thought about exploring > > > > and that is why I asked about setting the scm provider in a different > > > > manner. I have again used these prefixes and I still get a problem. > > > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of > > > > the plugin. > > > > > > > > During my reading of the site I noticed that both the scm and the > > > > release plugin are similar. Is it right to think that the maven-scm > > > > plugin is planned to allow developers to aquire a project without a > > > > pom.xml and then to complete the every day version control tasks? > > > > With this in mind is it best to view the maven-release plugin as a > > > > component that should be used to release code for a repository instead > > > > of completing a checkout/checkin, copy etc manually? I just want to > > > > know the thoughts behind each plugin. > > > > > > > > - Maven output - > > > > > > > > [ERROR] BUILD ERROR > > > > [INFO] > > > > --- > > > > [INFO] An error is occurred in the status process. > > > > > > > > Embedded error: Can't load the scm provider. > > > > The scm url is invalid. > > > > > > > > - stack trace -- > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm > > > > provider. > > > > at > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > > cmHelper.java:104) > > > > at > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe > > > > r.java:169) > > > > at > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi > > > > fications(PrepareReleaseMojo.java:510) > > > > ... 19 more > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The > > > > scm url i > > > > s invalid. > > > > at > > > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos > > > > itory(SvnScmProvider.java:84) > > > > at > > > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito > > > > ry(DefaultScmManager.java:126) > > > > at > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > > cmHelper.java:82) > > > > > > > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > Your SCM URL should start: > > > > > > > > > > scm:svn:file://... > > > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given > > > > > in the second argument above. > > > > > > > > > > - Brett > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > -
Re: [M2] - maven-release-plugin cannot load SCM provider
I thought I had used windows paths in the SCM URL before without issues, but its worth trying: scm|svn|file:///d:/subversion... hth, Brett On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > This is the SCM URL for the project: > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk > > > and the plugin is configured with the following tagbase element: > > > org.apache.maven.plugins > maven-release-plugin > 2.0-beta-3 > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > They both use the same library - so the release plugin is for > > automating release related tasks, the scm plugin for development > > related tasks. > > > > Can you please repost the full SCM URL that gave you this error - > > there is still something wrong with it. > > > > - Brett > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > > Thanks for the reply. > > > When I started to use the plugin I was prefixing the URLs with > > > "scm:svn", but then I still had a problem so thought about exploring > > > and that is why I asked about setting the scm provider in a different > > > manner. I have again used these prefixes and I still get a problem. > > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of the > > > plugin. > > > > > > During my reading of the site I noticed that both the scm and the > > > release plugin are similar. Is it right to think that the maven-scm > > > plugin is planned to allow developers to aquire a project without a > > > pom.xml and then to complete the every day version control tasks? > > > With this in mind is it best to view the maven-release plugin as a > > > component that should be used to release code for a repository instead > > > of completing a checkout/checkin, copy etc manually? I just want to > > > know the thoughts behind each plugin. > > > > > > - Maven output - > > > > > > [ERROR] BUILD ERROR > > > [INFO] > > > --- > > > [INFO] An error is occurred in the status process. > > > > > > Embedded error: Can't load the scm provider. > > > The scm url is invalid. > > > > > > - stack trace -- > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider. > > > at > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > cmHelper.java:104) > > > at > > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe > > > r.java:169) > > > at > > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi > > > fications(PrepareReleaseMojo.java:510) > > > ... 19 more > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The > > > scm url i > > > s invalid. > > > at > > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos > > > itory(SvnScmProvider.java:84) > > > at > > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito > > > ry(DefaultScmManager.java:126) > > > at > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > > cmHelper.java:82) > > > > > > > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Your SCM URL should start: > > > > > > > > scm:svn:file://... > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given > > > > in the second argument above. > > > > > > > > - Brett > > > > > > - > > > 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] - maven-release-plugin cannot load SCM provider
This is the SCM URL for the project: scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk and the plugin is configured with the following tagbase element: org.apache.maven.plugins maven-release-plugin 2.0-beta-3 scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > They both use the same library - so the release plugin is for > automating release related tasks, the scm plugin for development > related tasks. > > Can you please repost the full SCM URL that gave you this error - > there is still something wrong with it. > > - Brett > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > > Thanks for the reply. > > When I started to use the plugin I was prefixing the URLs with > > "scm:svn", but then I still had a problem so thought about exploring > > and that is why I asked about setting the scm provider in a different > > manner. I have again used these prefixes and I still get a problem. > > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of the > > plugin. > > > > During my reading of the site I noticed that both the scm and the > > release plugin are similar. Is it right to think that the maven-scm > > plugin is planned to allow developers to aquire a project without a > > pom.xml and then to complete the every day version control tasks? > > With this in mind is it best to view the maven-release plugin as a > > component that should be used to release code for a repository instead > > of completing a checkout/checkin, copy etc manually? I just want to > > know the thoughts behind each plugin. > > > > - Maven output - > > > > [ERROR] BUILD ERROR > > [INFO] > > --- > > [INFO] An error is occurred in the status process. > > > > Embedded error: Can't load the scm provider. > > The scm url is invalid. > > > > - stack trace -- > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider. > > at > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > cmHelper.java:104) > > at > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe > > r.java:169) > > at > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi > > fications(PrepareReleaseMojo.java:510) > > ... 19 more > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm > > url i > > s invalid. > > at > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos > > itory(SvnScmProvider.java:84) > > at > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito > > ry(DefaultScmManager.java:126) > > at > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > > cmHelper.java:82) > > > > > > > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > Your SCM URL should start: > > > > > > scm:svn:file://... > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given > > > in the second argument above. > > > > > > - Brett > > > > - > > 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] - maven-release-plugin cannot load SCM provider
They both use the same library - so the release plugin is for automating release related tasks, the scm plugin for development related tasks. Can you please repost the full SCM URL that gave you this error - there is still something wrong with it. - Brett On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > Thanks for the reply. > When I started to use the plugin I was prefixing the URLs with > "scm:svn", but then I still had a problem so thought about exploring > and that is why I asked about setting the scm provider in a different > manner. I have again used these prefixes and I still get a problem. > Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of the > plugin. > > During my reading of the site I noticed that both the scm and the > release plugin are similar. Is it right to think that the maven-scm > plugin is planned to allow developers to aquire a project without a > pom.xml and then to complete the every day version control tasks? > With this in mind is it best to view the maven-release plugin as a > component that should be used to release code for a repository instead > of completing a checkout/checkin, copy etc manually? I just want to > know the thoughts behind each plugin. > > - Maven output - > > [ERROR] BUILD ERROR > [INFO] > --- > [INFO] An error is occurred in the status process. > > Embedded error: Can't load the scm provider. > The scm url is invalid. > > - stack trace -- > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider. > at > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > cmHelper.java:104) > at > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe > r.java:169) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi > fications(PrepareReleaseMojo.java:510) > ... 19 more > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm > url i > s invalid. > at > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos > itory(SvnScmProvider.java:84) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito > ry(DefaultScmManager.java:126) > at > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S > cmHelper.java:82) > > > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Your SCM URL should start: > > > > scm:svn:file://... > > > > Maven has no knowledge of the SVN protocols, just the scm type given > > in the second argument above. > > > > - Brett > > - > 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] - maven-release-plugin cannot load SCM provider
Thanks for the reply. When I started to use the plugin I was prefixing the URLs with "scm:svn", but then I still had a problem so thought about exploring and that is why I asked about setting the scm provider in a different manner. I have again used these prefixes and I still get a problem. Maven gave me the follow stacktrace below. I am using 2.0-beta-3 of the plugin. During my reading of the site I noticed that both the scm and the release plugin are similar. Is it right to think that the maven-scm plugin is planned to allow developers to aquire a project without a pom.xml and then to complete the every day version control tasks? With this in mind is it best to view the maven-release plugin as a component that should be used to release code for a repository instead of completing a checkout/checkin, copy etc manually? I just want to know the thoughts behind each plugin. - Maven output - [ERROR] BUILD ERROR [INFO] --- [INFO] An error is occurred in the status process. Embedded error: Can't load the scm provider. The scm url is invalid. - stack trace -- Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider. at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S cmHelper.java:104) at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe r.java:169) at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi fications(PrepareReleaseMojo.java:510) ... 19 more Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i s invalid. at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos itory(SvnScmProvider.java:84) at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito ry(DefaultScmManager.java:126) at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S cmHelper.java:82) On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Your SCM URL should start: > > scm:svn:file://... > > Maven has no knowledge of the SVN protocols, just the scm type given > in the second argument above. > > - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] - maven-release-plugin cannot load SCM provider
Your SCM URL should start: scm:svn:file://... Maven has no knowledge of the SVN protocols, just the scm type given in the second argument above. - Brett On 11/7/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > I have been using Maven 2 for my current project and I am now at a > position where I want to tag and release a version. I really want to > use maven-release-plugin, but I am having problems. I am using SVN on > the local file system. I have been using subclipse with eclipse 3.1.1 > to access the source code and so I am sure the SVN setup is fine. > > I get the following error back from maven: > > [INFO] An error is occurred in the status process. > > Embedded error: Can't load the scm provider. > The scm url is invalid. > > I have looked at the mini-guide and have the following setup in my pom.xml: > > > > file:///D:/subversion-1.2.0_data/repositories/my_repo//trunk > > > > and the plugin is setup with the following values > > > org.apache.maven.plugins > maven-release-plugin > > > file:///D:/subversion-1.2.0_data/repositories/my_repo//tags > > > > > I then run the following command: > > mvn release:prepare > > Within the mini-guide the example shows the use of a SVN URL over SSH, > I went back and double checked the valid URLs for SVN, (using the > Subversion docs) and the above developerConnection String looks fine > to me. > > I have been searching the mailing list and different sites for any > info. How do I define the SCM provider to be used by the plugin? The > maven-release-plugin docs show a scmManager element for the > configuration but I am not sure how to use it. If the > developerConnection URL contained the svn:// or svn+ssh:// then I > could understand that the plugin would be able to locate and load the > provider. > > Does anyone have any thoughts on this problem? > Many thanks > > Trent > > - > 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: Réf. : RE: [m2] Maven release plugin and CVS: bug?
Fabrice,
After deleting the .cvspass and running release:prepare, can you run CVS
commands from the command line without access problems?
i.e. is the release:prepare generated .cvspass file valid?
Also, it would be good if we could somehow see the CVS command being executed
by release:prepare, but I don't know how to do this. Anyone any suggestions?
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 October 2005 12:36 AM
To: Maven Users List
Subject: Réf. : RE: [m2] Maven release plugin and CVS: bug?
Hi David,
I use CVSNT indeed, but as I provided my password in the SCM connection, it
seems that the release:prepare goal creates by itself the ".cvspass" with
the good entry.
And I also tried with a truely valid ".cvspass" (that works with other
plugins, m1 plugins for instance), it still doesn't work. That's why I run
out of ideas as of what I can do to make it work...
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
David Jackman
<[EMAIL PROTECTED]
astsearch.com> Pour
Maven Users List
19/10/2005 16:14
cc
VeuillezObjet
répondre à RE: [m2] Maven release plugin and
Maven Users List CVS: bug?
<[EMAIL PROTECTED]
che.org>
What do you see when you run cvs -version from the command line? If you're
running some version of CVSNT, then doing a cvs login from the command line
won't create the necessary ~/.cvspass file that the Maven SCM operations
will need. (Because CVSNT stores the passwords in the registry instead of
a file.) There are some web pages around that talk about this issue. If
that's what you're seeing, I wrote a utility some time back that extracts
passwords from the registry and creates a .cvspass file with them.
..David..
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 4:15 AM
To: users@maven.apache.org
Subject: RE: [m2] Maven release plugin and CVS: bug?
Michael,
thanks for your answer. Unfortunately, although I've followed every step
you gave to me, I still get the same error:
...
[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
Provider message:
The cvs command failed.
Command output:
cvs update: Empty password used - try 'cvs login' with a real password
cvs [update aborted]: authorization failed: server localhost rejected
access to C:\fabPlateformeIntegration\cvsAppliExempleTest for user fabrice
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the status process.
Embedded error: Error!
...
Maybe the problem comes from somewhere else... But that's weird because
when I connect to CVS via the command line, my user/password account is
correct and I'm not rejected.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
[EMAIL PROTECTED],
19/10/2005 07:16 users@maven.apache.org
cc
Objet
RE: [m2] Maven release plugin and
CVS: bug?
Fabrice,
Here is something else that is worth trying:
- Make sure that you are us
Réf. : RE: [m2] Maven release plugin and CVS: bug?
Hi David,
I use CVSNT indeed, but as I provided my password in the SCM connection, it
seems that the release:prepare goal creates by itself the ".cvspass" with
the good entry.
And I also tried with a truely valid ".cvspass" (that works with other
plugins, m1 plugins for instance), it still doesn't work. That's why I run
out of ideas as of what I can do to make it work...
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
David Jackman
<[EMAIL PROTECTED]
astsearch.com> Pour
Maven Users List
19/10/2005 16:14
cc
VeuillezObjet
répondre à RE: [m2] Maven release plugin and
Maven Users List CVS: bug?
<[EMAIL PROTECTED]
che.org>
What do you see when you run cvs -version from the command line? If you're
running some version of CVSNT, then doing a cvs login from the command line
won't create the necessary ~/.cvspass file that the Maven SCM operations
will need. (Because CVSNT stores the passwords in the registry instead of
a file.) There are some web pages around that talk about this issue. If
that's what you're seeing, I wrote a utility some time back that extracts
passwords from the registry and creates a .cvspass file with them.
..David..
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 4:15 AM
To: users@maven.apache.org
Subject: RE: [m2] Maven release plugin and CVS: bug?
Michael,
thanks for your answer. Unfortunately, although I've followed every step
you gave to me, I still get the same error:
...
[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
Provider message:
The cvs command failed.
Command output:
cvs update: Empty password used - try 'cvs login' with a real password
cvs [update aborted]: authorization failed: server localhost rejected
access to C:\fabPlateformeIntegration\cvsAppliExempleTest for user fabrice
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the status process.
Embedded error: Error!
...
Maybe the problem comes from somewhere else... But that's weird because
when I connect to CVS via the command line, my user/password account is
correct and I'm not rejected.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
[EMAIL PROTECTED],
19/10/2005 07:16 users@maven.apache.org
cc
Objet
RE: [m2] Maven release plugin and
CVS: bug?
Fabrice,
Here is something else that is worth trying:
- Make sure that you are using M2 RC. (I deleted my local repository after
installing the RC, to ensure my installation was completely fresh)
Say, for example your Maven SCM URL is:
scm:cvs:pserver::@::module
- Delete your .cvspass file.
This should be in your home directory ('c:\Documents and Settings' for me)
- Run the CVS login command:
cvs -d:pserver:@: login
- Run the release:prepare goal.
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 October 2005 5:55 PM
To: Michael McCrann
Subject: RE: [M2 RC] problems with release:perform
Hi Michael,
This release plugin seems to
RE: [m2] Maven release plugin and CVS: bug?
What do you see when you run cvs -version from the command line? If you're
running some version of CVSNT, then doing a cvs login from the command line
won't create the necessary ~/.cvspass file that the Maven SCM operations will
need. (Because CVSNT stores the passwords in the registry instead of a file.)
There are some web pages around that talk about this issue. If that's what
you're seeing, I wrote a utility some time back that extracts passwords from
the registry and creates a .cvspass file with them.
..David..
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 4:15 AM
To: users@maven.apache.org
Subject: RE: [m2] Maven release plugin and CVS: bug?
Michael,
thanks for your answer. Unfortunately, although I've followed every step you
gave to me, I still get the same error:
...
[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
Provider message:
The cvs command failed.
Command output:
cvs update: Empty password used - try 'cvs login' with a real password
cvs [update aborted]: authorization failed: server localhost rejected access to
C:\fabPlateformeIntegration\cvsAppliExempleTest for user fabrice
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the status process.
Embedded error: Error!
...
Maybe the problem comes from somewhere else... But that's weird because when I
connect to CVS via the command line, my user/password account is correct and
I'm not rejected.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
[EMAIL PROTECTED],
19/10/2005 07:16 users@maven.apache.org
cc
Objet
RE: [m2] Maven release plugin and
CVS: bug?
Fabrice,
Here is something else that is worth trying:
- Make sure that you are using M2 RC. (I deleted my local repository after
installing the RC, to ensure my installation was completely fresh)
Say, for example your Maven SCM URL is:
scm:cvs:pserver::@::module
- Delete your .cvspass file.
This should be in your home directory ('c:\Documents and Settings' for me)
- Run the CVS login command:
cvs -d:pserver:@: login
- Run the release:prepare goal.
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 October 2005 5:55 PM
To: Michael McCrann
Subject: RE: [M2 RC] problems with release:perform
Hi Michael,
This release plugin seems to be quite tricky... I still haven't succeeded in
making the prepare goal working! Could you please show me how your pom looks
like so that I can try to find what's wrong with mine?
Thanks a lot in advance! :o)
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
Maven Users List
18/10/2005 08:34
cc
VeuillezObjet
répondre à RE: [M2 RC] problems with
Maven Users List release:perform
<[EMAIL PROTECTED]
che.org>
Hi,
In attempt to find a solution to the my release:perform problem, I checked out
the trunk version and built maven using the m2-bootstrap-all.bat script.
I ran the rel
RE: [m2] Maven release plugin and CVS: bug?
Michael,
thanks for your answer. Unfortunately, although I've followed every step
you gave to me, I still get the same error:
...
[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
Provider message:
The cvs command failed.
Command output:
cvs update: Empty password used - try 'cvs login' with a real password
cvs [update aborted]: authorization failed: server localhost rejected
access to
C:\fabPlateformeIntegration\cvsAppliExempleTest for user fabrice
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the status process.
Embedded error: Error!
...
Maybe the problem comes from somewhere else... But that's weird because
when I connect to CVS via the command line, my user/password account is
correct and I'm not rejected.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
[EMAIL PROTECTED],
19/10/2005 07:16 users@maven.apache.org
cc
Objet
RE: [m2] Maven release plugin and
CVS: bug?
Fabrice,
Here is something else that is worth trying:
- Make sure that you are using M2 RC. (I deleted my local repository after
installing the RC, to ensure my installation was completely fresh)
Say, for example your Maven SCM URL is:
scm:cvs:pserver::@::module
- Delete your .cvspass file.
This should be in your home directory ('c:\Documents and Settings' for me)
- Run the CVS login command:
cvs -d:pserver:@: login
- Run the release:prepare goal.
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 October 2005 5:55 PM
To: Michael McCrann
Subject: RE: [M2 RC] problems with release:perform
Hi Michael,
This release plugin seems to be quite tricky... I still haven't succeeded
in making the prepare goal working! Could you please show me how your pom
looks like so that I can try to find what's wrong with mine?
Thanks a lot in advance! :o)
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
Maven Users List
18/10/2005 08:34
cc
VeuillezObjet
répondre à RE: [M2 RC] problems with
Maven Users List release:perform
<[EMAIL PROTECTED]
che.org>
Hi,
In attempt to find a solution to the my release:perform problem, I checked
out the trunk version and
built maven using the m2-bootstrap-all.bat script.
I ran the release:perform again and got the error below.
Ignoring the m2 deprecated message! could the problem be something to do
with '/' in the working directory:
c:\michaels_projects\transact\target/checkout?
Michael
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0-beta-3:perform' -->
[DEBUG] (f) basedir = c:\michaels_projects\transact
[DEBUG] (f) goals = deploy:deploy
[DEBUG] (f) interactive = true
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) workingDirectory =
c:\michaels_projects\transact\target/checkout
[DEBUG] -- end configuration --
[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
THE m2 COMMMAND IS DEPRECATED - PLEASE RUN mvn INSTEAD
The directory name is invalid.
[INFO]
--
RE: [m2] Maven release plugin and CVS: bug?
Fabrice,
Here is something else that is worth trying:
- Make sure that you are using M2 RC. (I deleted my local repository after
installing the RC, to ensure my installation was completely fresh)
Say, for example your Maven SCM URL is:
scm:cvs:pserver::@::module
- Delete your .cvspass file.
This should be in your home directory ('c:\Documents and Settings' for me)
- Run the CVS login command:
cvs -d:pserver:@: login
- Run the release:prepare goal.
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 October 2005 5:55 PM
To: Michael McCrann
Subject: RE: [M2 RC] problems with release:perform
Hi Michael,
This release plugin seems to be quite tricky... I still haven't succeeded
in making the prepare goal working! Could you please show me how your pom
looks like so that I can try to find what's wrong with mine?
Thanks a lot in advance! :o)
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Michael McCrann
Pour
Maven Users List
18/10/2005 08:34
cc
VeuillezObjet
répondre à RE: [M2 RC] problems with
Maven Users List release:perform
<[EMAIL PROTECTED]
che.org>
Hi,
In attempt to find a solution to the my release:perform problem, I checked
out the trunk version and
built maven using the m2-bootstrap-all.bat script.
I ran the release:perform again and got the error below.
Ignoring the m2 deprecated message! could the problem be something to do
with '/' in the working directory:
c:\michaels_projects\transact\target/checkout?
Michael
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0-beta-3:perform' -->
[DEBUG] (f) basedir = c:\michaels_projects\transact
[DEBUG] (f) goals = deploy:deploy
[DEBUG] (f) interactive = true
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) workingDirectory =
c:\michaels_projects\transact\target/checkout
[DEBUG] -- end configuration --
[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
THE m2 COMMMAND IS DEPRECATED - PLEASE RUN mvn INSTEAD
The directory name is invalid.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Result of m2 execution is: '1'. Release failed.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Result of m2
execution is: '1'. Release failed.
NOTICE
This e-mail and any attachments are confidential and may contain copyright
material of Macquarie Bank or third parties. If you are not the intended
recipient of this email you should not read, print, re-transmit, store or
act in reliance on this e-mail or any attachments, and should destroy all
copies of them. Macquarie Bank does not guarantee the integrity of any
emails or any attached files. The views or opinions expressed are the
author's own and may not reflect the views or opinions of Macquarie Bank.
-
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] Maven release plugin and CVS: bug?
Hi Michael, I put my pom[1] at the end of the mail. I still can't manage to make it work, even when I embed my password in the URL. I still get: Command output: cvs update: Empty password used - try 'cvs login' with a real password cvs [update aborted]: authorization failed: server localhost rejected access to C:\fabPlateformeIntegration\cvsAppliExempleTest for user fabrice However, the username and the password are correct, and I can connect when I use the cvs command line... By the way, I use Maven 2.0-RC and version 2.0-beta-3 of the release plugin. And I have my password stored in the .cvspass of my user home... I'm really running out of ideas to make this work! Thanks in advance for your help :o) Fabrice. [1] : 4.0.0 test test-release jar Test 1.0.0-SNAPSHOT scm:cvs:pserver:[EMAIL PROTECTED]:/C//fabPlateformeIntegration/cvsAppliExempleTest:Test-Release scm:cvs:pserver:[EMAIL PROTECTED]:/C//fabPlateformeIntegration/cvsAppliExempleTest:Test-Release maven-release-plugin 2.0-beta-3 fabrice XXX Best Regards / Cordialement, Fabrice BELLINGARD DINQ/DSIN/INSI/EATE/IDVS/AIDV (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] Michael McCrann Pour Maven Users List 17/10/2005 02:29 cc VeuillezObjet répondre à RE: [m2] Maven release plugin and Maven Users List CVS: bug? <[EMAIL PROTECTED] che.org> Fabrice, What is the SCM/CVS URL you are using? I have embedded my password in the URL. My URL looks like this: scm:cvs:pserver::@:: Michael -Original Message- From: Yann Le Du [mailto:[EMAIL PROTECTED] Sent: Saturday, 15 October 2005 9:10 AM To: Maven Users List Subject: RE: [m2] Maven release plugin and CVS: bug? Hi Fabrice, I am using SVN, but had the same kind of problem (at first). In your release plugin configuration, did you also provide , along ? I provided both, and it worked. Now the odd part : I recently removed and and it's still working. I can't tell why... Michael McCrann was also trying the release plugin with CVS, and seemed to have come further than you. Maybe he'll be able to help you ? http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112925914521071&w=2 Regards, Yann --- [EMAIL PROTECTED] a écrit : > > > > > Hi guys, > > I'm trying to make the maven release plugin work, but I always get the same > error when running "m2 release:prepare -Dtag=...": > > [INFO] [release:prepare] > [INFO] Verifying there are no local modifications ... > Provider message: > The cvs command failed. > Command output: > cvs update: Empty password used - try 'cvs login' with a real password > cvs [update aborted]: authorization failed: server localhost rejected > access to C:\cvsRepo for user e222731 > > This occurs although the .cvspass exists in my user home and it is valid > with the right password (the changes plugin can connect to the CVS - even > if it generates an empty report...). > > Is there something special to do to make this plugin work connect to CVS > correctly? I tried the "password" config parameter for the release plugin, > but this does not work... > > Am I missing something? Did someone manage to make it work with CVS or is > it a bug that I will fill in JIRA? > > Thanks! > > Best Regards / Cordialement, > Fabrice BELLINGARD > DINQ/DSIN/INSI/EATE/IDVS/AIDV > (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL
RE: [m2] Maven release plugin and CVS: bug?
Fabrice, What is the SCM/CVS URL you are using? I have embedded my password in the URL. My URL looks like this: scm:cvs:pserver::@:: Michael -Original Message- From: Yann Le Du [mailto:[EMAIL PROTECTED] Sent: Saturday, 15 October 2005 9:10 AM To: Maven Users List Subject: RE: [m2] Maven release plugin and CVS: bug? Hi Fabrice, I am using SVN, but had the same kind of problem (at first). In your release plugin configuration, did you also provide , along ? I provided both, and it worked. Now the odd part : I recently removed and and it's still working. I can't tell why... Michael McCrann was also trying the release plugin with CVS, and seemed to have come further than you. Maybe he'll be able to help you ? http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112925914521071&w=2 Regards, Yann --- [EMAIL PROTECTED] a écrit : > > > > > Hi guys, > > I'm trying to make the maven release plugin work, but I always get the same > error when running "m2 release:prepare -Dtag=...": > > [INFO] [release:prepare] > [INFO] Verifying there are no local modifications ... > Provider message: > The cvs command failed. > Command output: > cvs update: Empty password used - try 'cvs login' with a real password > cvs [update aborted]: authorization failed: server localhost rejected > access to C:\cvsRepo for user e222731 > > This occurs although the .cvspass exists in my user home and it is valid > with the right password (the changes plugin can connect to the CVS - even > if it generates an empty report...). > > Is there something special to do to make this plugin work connect to CVS > correctly? I tried the "password" config parameter for the release plugin, > but this does not work... > > Am I missing something? Did someone manage to make it work with CVS or is > it a bug that I will fill in JIRA? > > Thanks! > > Best Regards / Cordialement, > Fabrice BELLINGARD > DINQ/DSIN/INSI/EATE/IDVS/AIDV > (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Maven release plugin and CVS: bug?
On 10/15/05, Yann Le Du <[EMAIL PROTECTED]> wrote: > Now the odd part : I recently removed and and it's still > working. I can't tell why... This is a consequence of svn - it caches the information. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven release plugin and CVS: bug?
Hi Fabrice, I am using SVN, but had the same kind of problem (at first). In your release plugin configuration, did you also provide , along ? I provided both, and it worked. Now the odd part : I recently removed and and it's still working. I can't tell why... Michael McCrann was also trying the release plugin with CVS, and seemed to have come further than you. Maybe he'll be able to help you ? http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112925914521071&w=2 Regards, Yann --- [EMAIL PROTECTED] a écrit : > > > > > Hi guys, > > I'm trying to make the maven release plugin work, but I always get the same > error when running "m2 release:prepare -Dtag=...": > > [INFO] [release:prepare] > [INFO] Verifying there are no local modifications ... > Provider message: > The cvs command failed. > Command output: > cvs update: Empty password used - try 'cvs login' with a real password > cvs [update aborted]: authorization failed: server localhost rejected > access to C:\cvsRepo for user e222731 > > This occurs although the .cvspass exists in my user home and it is valid > with the right password (the changes plugin can connect to the CVS - even > if it generates an empty report...). > > Is there something special to do to make this plugin work connect to CVS > correctly? I tried the "password" config parameter for the release plugin, > but this does not work... > > Am I missing something? Did someone manage to make it work with CVS or is > it a bug that I will fill in JIRA? > > Thanks! > > Best Regards / Cordialement, > Fabrice BELLINGARD > DINQ/DSIN/INSI/EATE/IDVS/AIDV > (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
