You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Roussel <na...@diroussel.xsmail.com> on 2008/08/26 15:18:10 UTC

release:prepare and multi-module projects

I've been trying to run release:prepare on a nested project and I keep
running into the same SVN related issues.  Has anyone else got it working?

I can supply the full trace, but the basic problem I get is:

...
[INFO] Executing: svn --non-interactive copy --file
C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1626400052.commit .
http://gcm-svn/
svn/REPO1/Projects/InstallTools/tags/installer-0.5
[INFO] Working directory: D:\dev\workspace1\installer
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File
'/svn/REPO1/Projects/InstallTools/tags/installer-0.5/installer-plugin/pom.xml'
already exists


If I repeat that svn command on the comand line it does fail again.  The
file does not exist. But if I do 'svn update' and then repeat it, then it
works.  

Also if I manually, do a 'svn copy URL URL' version of tagging, that also
works.

I've been trying to reproduce the problem in raw svn, just doing svn
commands and I can't.  So I guess it must be a maven-release-plugin bug.

So has anyone else got the release plugin to work in multi-module projects
using svn?

Thanks

David
-- 
View this message in context: http://www.nabble.com/release%3Aprepare-and-multi-module-projects-tp19161884p19161884.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: release:prepare and multi-module projects

Posted by David Roussel <na...@diroussel.xsmail.com>.
Are you trying to release a nested project?  I am?

What kind of authentication are you using?  I'm using windows authetication,
via Apache 2.2 and mod_sspi.  Not sure if that makes a difference.

David




jrduncans wrote:
> 
> Sounds like the same problem many are facing with a bug in SVN 1.5.1
> 
> See these threads on the SVN & Maven mailing lists:
> 
> http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html#a19142776
> http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html
> 
> I'm still looking to get some confirmation that it's a bug before
> reporting
> it ion the SVN issue tracker...
> 
> -Stephen
> 
> 
> On Tue, Aug 26, 2008 at 9:18 AM, David Roussel
> <na...@diroussel.xsmail.com>wrote:
> 
>>
>> I've been trying to run release:prepare on a nested project and I keep
>> running into the same SVN related issues.  Has anyone else got it
>> working?
>>
>> I can supply the full trace, but the basic problem I get is:
>>
>> ...
>> [INFO] Executing: svn --non-interactive copy --file
>> C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1626400052.commit .
>> http://gcm-svn/
>> svn/REPO1/Projects/InstallTools/tags/installer-0.5<http://gcm-svn/svn/REPO1/Projects/InstallTools/tags/installer-0.5>
>> [INFO] Working directory: D:\dev\workspace1\installer
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to tag SCM
>> Provider message:
>> The svn tag command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: File
>>
>> '/svn/REPO1/Projects/InstallTools/tags/installer-0.5/installer-plugin/pom.xml'
>> already exists
>>
>>
>> If I repeat that svn command on the comand line it does fail again.  The
>> file does not exist. But if I do 'svn update' and then repeat it, then it
>> works.
>>
>> Also if I manually, do a 'svn copy URL URL' version of tagging, that also
>> works.
>>
>> I've been trying to reproduce the problem in raw svn, just doing svn
>> commands and I can't.  So I guess it must be a maven-release-plugin bug.
>>
>> So has anyone else got the release plugin to work in multi-module
>> projects
>> using svn?
>>
>> Thanks
>>
>> David
>> --
>> View this message in context:
>> http://www.nabble.com/release%3Aprepare-and-multi-module-projects-tp19161884p19161884.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 
> 
> -- 
> Stephen Duncan Jr
> www.stephenduncanjr.com
> 
> 

-- 
View this message in context: http://www.nabble.com/release%3Aprepare-and-multi-module-projects-tp19161884p19164407.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: release:prepare and multi-module projects

Posted by Stephen Duncan Jr <st...@gmail.com>.
Sounds like the same problem many are facing with a bug in SVN 1.5.1

See these threads on the SVN & Maven mailing lists:

http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html#a19142776
http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html

I'm still looking to get some confirmation that it's a bug before reporting
it ion the SVN issue tracker...

-Stephen


On Tue, Aug 26, 2008 at 9:18 AM, David Roussel
<na...@diroussel.xsmail.com>wrote:

>
> I've been trying to run release:prepare on a nested project and I keep
> running into the same SVN related issues.  Has anyone else got it working?
>
> I can supply the full trace, but the basic problem I get is:
>
> ...
> [INFO] Executing: svn --non-interactive copy --file
> C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1626400052.commit .
> http://gcm-svn/
> svn/REPO1/Projects/InstallTools/tags/installer-0.5<http://gcm-svn/svn/REPO1/Projects/InstallTools/tags/installer-0.5>
> [INFO] Working directory: D:\dev\workspace1\installer
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File
>
> '/svn/REPO1/Projects/InstallTools/tags/installer-0.5/installer-plugin/pom.xml'
> already exists
>
>
> If I repeat that svn command on the comand line it does fail again.  The
> file does not exist. But if I do 'svn update' and then repeat it, then it
> works.
>
> Also if I manually, do a 'svn copy URL URL' version of tagging, that also
> works.
>
> I've been trying to reproduce the problem in raw svn, just doing svn
> commands and I can't.  So I guess it must be a maven-release-plugin bug.
>
> So has anyone else got the release plugin to work in multi-module projects
> using svn?
>
> Thanks
>
> David
> --
> View this message in context:
> http://www.nabble.com/release%3Aprepare-and-multi-module-projects-tp19161884p19161884.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: release:prepare and multi-module projects

Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Tue, Aug 26, 2008 at 9:18 AM, David Roussel
<na...@diroussel.xsmail.com>wrote:

> If I repeat that svn command on the comand line it does fail again.  The
> So has anyone else got the release plugin to work in multi-module projects
> using svn?


I've done lots of releases of multi-module projects with the release plugin
using SVN either over https or ssh+svn, most recently with Maven 2.0.8 and
2.0.9.  Haven't hit the issue you're describing, so I'm not sure what to
suggest.

  - Geoffrey
-- 
Geoffrey Wiseman