Emmanuel,
I took your advice and tried the prepare call again after doing a manual
commit using the SVN command line. Suprise it worked. Many thanks to
your for your help.
Thanks,
Brian Yoffe
Emmanuel Venisse <[EMAIL PROTECTED]>
01/30/2006 12:21 PM
Please respond to "Maven Users List"
To: Maven Users List <users@maven.apache.org>
cc:
Subject: Re: SVN/SCM Release Help (M20
Yes, release and scm plugins use maven-scm.
I think your maven-release plugin use an old maven-scm (before
1.0-beta-2), You can check it with -X
parameter on command line. Code in svn use a more recent version.
Emmanuel
[EMAIL PROTECTED] a écrit :
> Ok,
>
> Found this and using the SCM plugin directly - seems to work fine (I
> believe this is the same plugin the release plugin uses). I think
I've
> provided/run every test that I can think of, so I'll stop posting and
give
> people a chance to digest this and propose some other direction. I
> really want to use the plugin and would hate to work around it.
>
> mvn scm:update -DconnectionUrl=scm:svn:MY_URL/trunk
> mvn scm:checkin -DconnectionUrl=scm:svn:http://MY_URL/trunk
> -Dmessage=Test3 -Dusername=MY_UN
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
> [INFO]
>
----------------------------------------------------------------------------
> [INFO] Building Commons Library
> [INFO] task-segment: [scm:checkin]
> [INFO]
>
----------------------------------------------------------------------------
> [INFO] [scm:checkin]
> [INFO] Working directory: /home/focis/lpatdev/build/common/trunk
> [INFO] Command line: svn --username MY_UN --non-interactive commit
--file
> /tmp/maven-scm-246229712.commit
> [INFO]
>
----------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
----------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Mon Jan 30 13:07:05 EST 2006
> [INFO] Final Memory: 3M/6M
> [INFO]
>
----------------------------------------------------------------------------
>
> Thanks again,
> Brian Yoffe
>
>
>
>
>
> [EMAIL PROTECTED]
> 01/30/2006 11:48 AM
> Please respond to "Maven Users List"
>
>
> To: "Maven Users List" <users@maven.apache.org>
> cc:
> Subject: Re: SVN/SCM Release Help (M20
>
>
> Just verified (again) that command line svn commit functions correctly:
Is
>
> there a way to test to svn scm plugin in isolation?
>
> svn commit --username=MY_UN --message=Test
> Sending pom.xml
> Authentication realm: <http://subversion.ny.jpmorgan.com:80> Subversion
> Test Repository
> Password for 'MY_UN':
> Transmitting file data .
> Committed revision 23.
>
> Thanks,
> Brian Yoffe
>
>
>
>
>
> [EMAIL PROTECTED]
> 01/30/2006 11:40 AM
> Please respond to "Maven Users List"
>
>
> To: "Maven Users List" <users@maven.apache.org>
> cc:
> Subject: Re: SVN/SCM Release Help (M20
>
>
> Here's the results of svn info:
>
> Path: .
> URL: http://MY_URL/trunk
> Repository UUID: 0d904ab9-2b0b-0410-8389-833101efcc01
> Revision: 22
> Node Kind: directory
> Schedule: normal
> Last Changed Author: MY_UN
> Last Changed Rev: 20
> Last Changed Date: 2006-01-27 19:12:08 -0500 (Fri, 27 Jan 2006)
>
> mvn release:prepare \
> -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \
> -DtagBase=http://MY_URL/tags \
> -Dusername=MY_UN
>
> Thanks,
> Brian Yoffe
>
>
>
>
>
> Emmanuel Venisse <[EMAIL PROTECTED]>
> 01/30/2006 10:21 AM
> Please respond to "Maven Users List"
>
>
> To: Maven Users List <users@maven.apache.org>
> cc:
> Subject: Re: SVN/SCM Release Help (M20
>
>
> Are you sure you use the same svn url?
>
> Check it with svn info
>
> Emmanuel
>
> [EMAIL PROTECTED] a écrit :
>
>>Ok, tried:
>>
>>mvn release:prepare \
>> -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \
>> -DtagBase=http://MY_URL/tags \
>> -Dusername=MY_UN
>>
>>and I tried:
>>
>>mvn release:prepare \
>> -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \
>> -DtagBase=http://MY_URL/tags \
>> -Dusername=MY_UN -Dpassword=MY_PW
>>
>>Result is (for both):
>>
>>svn: Commit failed (details follow):
>>svn: CHECKOUT of
>
> '/svn/repos/platformautotrading_common/!svn/ver/21/tags':
>
>>authorization failed (http://reuse.ny.jpmorgan.com).
>>
>>I have verified that svn commands are working correctly (did a commit
>>using svn directly), svn is in my path, and password caching is enabled
>>and working. Anything I can turn on (debug setting or otherwise) to
>
> see
>
>>the SVN command being issued?
>>
>>Thanks,
>>Brian Yoffe
>>
>>
>>
>>Emmanuel Venisse <[EMAIL PROTECTED]>
>>01/30/2006 03:14 AM
>>Please respond to "Maven Users List"
>>
>>
>> To: Maven Users List <users@maven.apache.org>
>> cc:
>> Subject: Re: SVN/SCM Release Help
>>
>>
>>Try this :
>>
>>mvn release:prepare \
>> -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \
>> -DtagBase=http://MY_URL/tags \
>> -Dusername=MY_UN -Dpassword=MY_PW
>>
>>Emmanuel
>>
>>
>>
>>
>>
>>"Brian E. Fox" <[EMAIL PROTECTED]>
>>01/28/2006 10:32 AM
>>Please respond to "Maven Users List"
>>
>>
>> To: "Maven Users List" <users@maven.apache.org>
>> cc:
>> Subject: RE: SVN/SCM Release Help
>>
>>
>>Use -Dusername= I'm not sure about the password, I have SVN save it for
>>me.
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>Sent: Friday, January 27, 2006 7:25 PM
>>To: users@maven.apache.org
>>Subject: SVN/SCM Release Help
>>
>>I'm moving from an ANT build script to Maven, and also moving from a
>>windows build machine to linux. Previously, all of the SVN SCM release
>>
>>activities were carried out through TortoiseSVN on that windows machine
>>- I would like to use the release plugin to accomplish what was
>>previously a multi-step manual process..
>>
>>When I execute the release:prepare step using the following command I
>>get an authorization failed error:
>>
>>mvn release:prepare \
>> -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \
>> -DtagBase=http://MY_URL/tags \
>> -Dmaven.scm.username=MY_UN -Dmaven.scm.password=MY_PW
>>
>>I have verified that svn is in my path and have verified that I can
>>commit
>>when using the svn command direcly from the shell. Can anyone point me
>>
>>in the right direction or offer some suggestions for where else to look?
>>
>>I have read everything I could get my hands on as well as the archives
>>to this list.
>>
>>Thanks in advance,
>>Brian Yoffe
>>
>>
>>
>>
>>+ Error stacktraces are turned on.
>>[INFO] Scanning for projects...
>>[INFO] Searching repository for plugin with prefix: 'release'.
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[INFO] Building Commons Library
>>[INFO] task-segment: [release:prepare] (aggregator-style)
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[INFO] [release:prepare]
>>[INFO] What tag name should be used?
>>1.1.2
>>[INFO] Tagging release with the label 1.1.2.
>>Provider message:
>>The svn tag command failed.
>>Command output:
>>svn: Commit failed (details follow):
>>svn: CHECKOUT of
>>'/svn/repos/platformautotrading_common/!svn/ver/11/tags':
>>authorization failed (http://reuse.ny.jpmorgan.com)
>>
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[ERROR] BUILD ERROR
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[INFO] An error is occurred in the tag process.
>>
>>Embedded error: Error!
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[INFO] Trace
>>org.apache.maven.lifecycle.LifecycleExecutionException: An error is
>>occurred in the tag process.
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
>>LifecycleExecutor.java:556)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
>>l(DefaultLifecycleExecutor.java:485)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
>>ifecycleExecutor.java:455)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
>>Failures(DefaultLifecycleExecutor.java:303)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>DefaultLifecycleExecutor.java:216)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
>>ycleExecutor.java:139)
>> at
>>org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
>>a:39)
>> at
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
>>Impl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at
>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>Caused by: org.apache.maven.plugin.MojoExecutionException: An error is
>>occurred in the tag process.
>> at
>>org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareRe
>>leaseMojo.java:1414)
>> at
>>org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea
>>seMojo.java:246)
>> at
>>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
>>nager.java:415)
>> at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
>>LifecycleExecutor.java:531)
>> ... 16 more
>>Caused by: org.apache.maven.scm.ScmException: Error!
>> at
>>org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper
>>.java:124)
>> at
>>org.apache.maven.plugins.release.helpers.ScmHelper.tag(ScmHelper.java:22
>>6)
>> at
>>org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareRe
>>leaseMojo.java:1410)
>> ... 19 more
>>[INFO]
>>------------------------------------------------------------------------
>>----
>>[INFO] Total time: 7 seconds
>>[INFO] Finished at: Fri Jan 27 19:20:04 EST 2006 [INFO] Final Memory:
>>3M/7M [INFO]
>>------------------------------------------------------------------------
>>----
>>This communication is for informational purposes only. It is not
>>intended as an offer or solicitation for the purchase or sale of any
>>financial instrument or as an official confirmation of any transaction.
>>All market prices, data and other information are not warranted as to
>>completeness or accuracy and are subject to change without notice. Any
>>comments or statements made herein do not necessarily reflect those of
>>JPMorgan Chase & Co., its subsidiaries and affiliates
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>
>>This communication is for informational purposes only. It is not
>
> intended
>
>>as an offer or solicitation for the purchase or sale of any financial
>>instrument or as an official confirmation of any transaction. All market
>
>
>
> prices,
>
>>data and other information are not warranted as to completeness or
>
> accuracy and
>
>>are subject to change without notice. Any comments or statements made
>
> herein
>
>>do not necessarily reflect those of JPMorgan Chase & Co., its
>
> subsidiaries
>
>>and affiliates.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> This communication is for informational purposes only. It is not
intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All market
> prices,
> data and other information are not warranted as to completeness or
> accuracy and
> are subject to change without notice. Any comments or statements made
> herein
> do not necessarily reflect those of JPMorgan Chase & Co., its
subsidiaries
>
>
> and affiliates
>
>
>
>
>
> This communication is for informational purposes only. It is not
intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All market
> prices,
> data and other information are not warranted as to completeness or
> accuracy and
> are subject to change without notice. Any comments or statements made
> herein
> do not necessarily reflect those of JPMorgan Chase & Co., its
subsidiaries
>
> and affiliates.
>
>
>
> This communication is for informational purposes only. It is not
intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All market
prices,
> data and other information are not warranted as to completeness or
accuracy and
> are subject to change without notice. Any comments or statements made
herein
> do not necessarily reflect those of JPMorgan Chase & Co., its
subsidiaries
> and affiliates.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates
