|
Mac OS X + SVN 1.5.1 = Branch problem
Mac OS X + SVN 1.5.1 = Branch problem
Hello,
Did anyone else using Mac OS X with SVN 1.5.1 hit this problem? This problem does not exist for SVN 1.4.4.
Thanks!
Koichi
-------
mvn release:branch -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DbranchName=stuff-1.0.10.X
.....
org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to branch SCM
Provider message:
The svn branch command failed.
Command output:
svn: Commit failed (details follow):
svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml' already exists
at org.apache.maven.shared.release.phase.ScmBranchPhase.execute(ScmBranchPhase.java:98)
at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:361)
at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:332)
at org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:130)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to branch SCM
Provider message:
The svn branch command failed.
Command output:
svn: Commit failed (details follow):
svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml' already exists
|
|
 Re: Mac OS X + SVN 1.5.1 = Branch problem
Koichi Tsunoda wrote:
> Hello,
>
> Did anyone else using Mac OS X with SVN 1.5.1 hit this problem? This problem
> does not exist for SVN 1.4.4.
Can you reproduce this using the command line client? For those of us that
don't speak maven, it is a bit difficult to figure out what's really going on here.
Thanks,
-Hyrum
>>
>> -------
>>
>> mvn release:branch -DupdateBranchVersions=true
>> -DupdateWorkingCopyVersions=false -DbranchName=stuff-1.0.10.X
>>
>> .....
>>
>> org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to
>> branch SCM
>> Provider message:
>> The svn branch command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml' already
>> exists
>>
>> at
>> org.apache.maven.shared.release.phase.ScmBranchPhase.execute(ScmBranchPhase.ja
>> va:98)
>> at
>> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseMan
>> ager.java:361)
>> at
>> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseMan
>> ager.java:332)
>> at
>> org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.j
>> ava:130)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.
>> java:451)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecy
>> cleExecutor.java:558)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(Defa
>> ultLifecycleExecutor.java:512)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecyc
>> leExecutor.java:482)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailur
>> es(DefaultLifecycleExecutor.java:330)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defaul
>> tLifecycleExecutor.java:227)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleEx
>> ecutor.java:142)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j
>> ava:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> 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)
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to branch SCM
>> Provider message:
>> The svn branch command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml' already
>> exists
>>
>
>
>
>
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
>>> ------------------------------------------------------------------------
>>> [INFO] Unable to branch SCM
>>> Provider message:
>>> The svn branch command failed.
>>> Command output:
>>> svn: Commit failed (details follow):
>>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml'
>>> already
>>> exists
This does not appear to be a broken binary. Apparently you're trying
to create a branch where a branch exists. This is a common error that
you would get regardless of client. Check your repository structure.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
That would've been way too obvious :) I believe that I mentioned that it
worked with SVN 1.4.4.
Here's what happened:
1. Tried this command with 1.5.1, and this error showed up.
2. I tried it immediately after with SVN 1.4.4, and it went through.
To me, that implies that the bug is in SVN 1.5.1, since I the only thing
that I differed is the SVN binary, and didn't do anything with the
repository location/structure.
Let me see if I can break down the maven command into SVN commands...
Thanks for your responses!
Koichi
On 8/17/08 8:51 AM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
>>>> ------------------------------------------------------------------------
>>>> [INFO] Unable to branch SCM
>>>> Provider message:
>>>> The svn branch command failed.
>>>> Command output:
>>>> svn: Commit failed (details follow):
>>>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml'
>>>> already
>>>> exists
>
> This does not appear to be a broken binary. Apparently you're trying
> to create a branch where a branch exists. This is a common error that
> you would get regardless of client. Check your repository structure.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
I am going into this with an open mind but since you're not getting a
seg fault or bus error, I don't see the binary being defective. I look
forward to your findings.
Sent from my iPod Touch.
On Aug 17, 2008, at 10:45, Koichi Tsunoda < ichikoo315@...>
wrote:
> That would've been way too obvious :) I believe that I mentioned
> that it
> worked with SVN 1.4.4.
>
> Here's what happened:
>
> 1. Tried this command with 1.5.1, and this error showed up.
> 2. I tried it immediately after with SVN 1.4.4, and it went through.
>
> To me, that implies that the bug is in SVN 1.5.1, since I the only
> thing
> that I differed is the SVN binary, and didn't do anything with the
> repository location/structure.
>
> Let me see if I can break down the maven command into SVN commands...
>
> Thanks for your responses!
> Koichi
>
>
>
> On 8/17/08 8:51 AM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
>
>>>>> ---
>>>>> ---
>>>>> ------------------------------------------------------------------
>>>>> [INFO] Unable to branch SCM
>>>>> Provider message:
>>>>> The svn branch command failed.
>>>>> Command output:
>>>>> svn: Commit failed (details follow):
>>>>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml'
>>>>> already
>>>>> exists
>>
>> This does not appear to be a broken binary. Apparently you're trying
>> to create a branch where a branch exists. This is a common error
>> that
>> you would get regardless of client. Check your repository structure.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Hello Hyrum, Jeremy,
Ok, this is what's going on:
pisces:1.0.5 Koichi$ svn copy .
https://dev.company.com/svn/flash/Core/branches/flash-core-1.0.5.X --message
"Testing 1 2 3"
svn: Commit failed (details follow):
svn: File '/svn/flash/Core/branches/flash-core-1.0.5.X/Stuff/pom.xml'
already exists
pisces:1.0.5 Koichi$ svn co
https://dev.company.com/svn/flash/Core/branches/flash-core-1.0.5.X test
svn: URL
' https://dev.company.com/svn/flash/Core/branches/flash-core-1.0.5.X' doesn't
exist
pisces:1.0.5 Koichi$
As you can see from above, svn copy fails, and right after, I do a svn co to
show that the specific location does not exist.
I suppose "svn copy" on Mac OS X has issues.
Thanks for your help!
Koichi
On 8/17/08 9:54 AM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
> I am going into this with an open mind but since you're not getting a
> seg fault or bus error, I don't see the binary being defective. I look
> forward to your findings.
>
> Sent from my iPod Touch.
>
> On Aug 17, 2008, at 10:45, Koichi Tsunoda < ichikoo315@...>
> wrote:
>
>> That would've been way too obvious :) I believe that I mentioned
>> that it
>> worked with SVN 1.4.4.
>>
>> Here's what happened:
>>
>> 1. Tried this command with 1.5.1, and this error showed up.
>> 2. I tried it immediately after with SVN 1.4.4, and it went through.
>>
>> To me, that implies that the bug is in SVN 1.5.1, since I the only
>> thing
>> that I differed is the SVN binary, and didn't do anything with the
>> repository location/structure.
>>
>> Let me see if I can break down the maven command into SVN commands...
>>
>> Thanks for your responses!
>> Koichi
>>
>>
>>
>> On 8/17/08 8:51 AM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
>>
>>>>>> ---
>>>>>> ---
>>>>>> ------------------------------------------------------------------
>>>>>> [INFO] Unable to branch SCM
>>>>>> Provider message:
>>>>>> The svn branch command failed.
>>>>>> Command output:
>>>>>> svn: Commit failed (details follow):
>>>>>> svn: File '/svn/flash/Stuff/branches/stuff-1.0.10.X/Stuff/pom.xml'
>>>>>> already
>>>>>> exists
>>>
>>> This does not appear to be a broken binary. Apparently you're trying
>>> to create a branch where a branch exists. This is a common error
>>> that
>>> you would get regardless of client. Check your repository structure.
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Can you "svn ls" the content of URL/svn/flash/Core/branches to make
sure it is or isn't there? Any chance you have a branch with the same
name just with different casing? Can you try the above with the 1.4.4
client? There is too little information to help you out here.
Anything that can help us paint a picture like the exact series of
command you ran to get to this point would help. Again, with no seg
fault or bus error, I'm pretty sure that the binary isn't messed up.
Subversion doesn't just copy different on one system differently than
it does on another system. Since there were a number of copy-related
improvements from 1.4.x to 1.5.x, it is possible that new checks and
balances are in place that are causing what you're seeing.
Permissions could also be involved here. There is just too little to
go on so please give us more information starting with the requests
above and we'll get to the bottom of this.
Take care,
Jeremy
P.S. - Here is a link to a few of the 1.5.x copy-related changes:
http://subversion.tigris.org/svn_1.5_releasenotes.html#copy-move-improvements---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Any update? Can you install a 1.5.1 client on another operating
system and attempt to do the same problematic Maven step?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Hello,
Sorry, I do not have any updates. I have been swamped with work today (still
working...). Ben mentioned that he has hit the same issue too. Perhaps he
can shed some light on which OS/configuration he used to hit the same issue.
I don't have any other machine I can test it on that has this setting for
now.
I'll give an update when I can, hopefully by the EOD Tuesday.
Koichi
On 8/18/08 10:24 PM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
> Any update? Can you install a 1.5.1 client on another operating
> system and attempt to do the same problematic Maven step?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Koichi,
I was informed by Mark Phippard today that there was a change in
Subversion's copy feature from 1.4.x to 1.5.x that might be the cause
of this:
* correctly set the peg revision for copy in JavaHL (r31994)
Since Maven is a Java application, it might not have been updated to
work with this new change. Mark also said that Subclipse had to be
updated because of this change. When you get some time, please try to
reproduce on a non-Mac so we can rule out the binary. If this is an
issue with Maven, I'll file an issue with them with a patch to fix it.
Take care,
Jeremy
On Tue, Aug 19, 2008 at 2:03 AM, Koichi Tsunoda < ichikoo315@...> wrote:
> Hello,
>
> Sorry, I do not have any updates. I have been swamped with work today (still
> working...). Ben mentioned that he has hit the same issue too. Perhaps he
> can shed some light on which OS/configuration he used to hit the same issue.
>
> I don't have any other machine I can test it on that has this setting for
> now.
>
> I'll give an update when I can, hopefully by the EOD Tuesday.
>
> Koichi
>
>
> On 8/18/08 10:24 PM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
>
>> Any update? Can you install a 1.5.1 client on another operating
>> system and attempt to do the same problematic Maven step?
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Hey Jeremy,
Thanks a lot!
Ben, what is your machine configuration that caused you to hit this same
issue?
Koichi
On 8/19/08 9:48 AM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
> Koichi,
> I was informed by Mark Phippard today that there was a change in
> Subversion's copy feature from 1.4.x to 1.5.x that might be the cause
> of this:
>
> * correctly set the peg revision for copy in JavaHL (r31994)
>
> Since Maven is a Java application, it might not have been updated to
> work with this new change. Mark also said that Subclipse had to be
> updated because of this change. When you get some time, please try to
> reproduce on a non-Mac so we can rule out the binary. If this is an
> issue with Maven, I'll file an issue with them with a patch to fix it.
>
> Take care,
>
> Jeremy
>
> On Tue, Aug 19, 2008 at 2:03 AM, Koichi Tsunoda < ichikoo315@...>
> wrote:
>> Hello,
>>
>> Sorry, I do not have any updates. I have been swamped with work today (still
>> working...). Ben mentioned that he has hit the same issue too. Perhaps he
>> can shed some light on which OS/configuration he used to hit the same issue.
>>
>> I don't have any other machine I can test it on that has this setting for
>> now.
>>
>> I'll give an update when I can, hopefully by the EOD Tuesday.
>>
>> Koichi
>>
>>
>> On 8/18/08 10:24 PM, "Jeremy Whitlock" < jcscoobyrs@...> wrote:
>>
>>> Any update? Can you install a 1.5.1 client on another operating
>>> system and attempt to do the same problematic Maven step?
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
> Ben, what is your machine configuration that caused you to hit this same
> issue?
He's on OSX just like yourself.
I'd suggest checking out your Maven-based project on another operating
system with 1.5.1 and see if you get the same error.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
On Tue, Aug 19, 2008 at 12:48 PM, Jeremy Whitlock < jcscoobyrs@...> wrote:
> Koichi,
> I was informed by Mark Phippard today that there was a change in
> Subversion's copy feature from 1.4.x to 1.5.x that might be the cause
> of this:
>
> * correctly set the peg revision for copy in JavaHL (r31994)
I think someone said this worked in 1.5.0 and not 1.5.1, so I flagged
the above change from 1.5.1.
One thing I am not sure of is whether Maven even uses JavaHL. It
might just run the SVN command line. If it does not use JavaHL, then
all bets are off. Likewise, someone should make sure it does not use
SVNKit, as that would then need to go to support@...
--
Thanks
Mark Phippard
http://markphip.blogspot.com/---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Hi.
I get this error on Red Hat (Enterprise 3 - 2.4 kernel) using svn 1.5.1 (r32289).
I tried this iwth 1.5.0 (r31699) and it works fine, atlhough 1.5.0 has other issues relating to merging.
I'm trying to isolate a test case that fails without using maven.
- Ben.
Koichi Tsunoda wrote:
Ben, what is your machine configuration that caused you to hit this same
issue?
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
> I get this error on Red Hat (Enterprise 3 - 2.4 kernel) using svn 1.5.1
> (r32289).
This is great news for me, as my binary was where this was first
reported. With all of the troubles I've ran into with maintaining the
binary, I was starting to sweat bullets. ;)
> I'm trying to isolate a test case that fails without using maven.
That would be great. You could probably download SVNKit and build a
simple application that performs a copy, like Maven does. Just make
sure you get the SVNKit used by Maven and use its code as a reference.
I think I'll get involved with trying to produce a recipe for this as
well.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
On Tue, Aug 19, 2008 at 6:54 PM, Jeremy Whitlock < jcscoobyrs@...> wrote:
>> I get this error on Red Hat (Enterprise 3 - 2.4 kernel) using svn 1.5.1
>> (r32289).
>
> This is great news for me, as my binary was where this was first
> reported. With all of the troubles I've ran into with maintaining the
> binary, I was starting to sweat bullets. ;)
>
>> I'm trying to isolate a test case that fails without using maven.
>
> That would be great. You could probably download SVNKit and build a
> simple application that performs a copy, like Maven does. Just make
> sure you get the SVNKit used by Maven and use its code as a reference.
> I think I'll get involved with trying to produce a recipe for this as
> well.
I do not believe anyone has said Maven uses SVNKit. I was simply
pointing out that if it does, that is the next place to look.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Hi.
Jeremy Whitlock wrote:
That would be great. You could probably download SVNKit and build a
simple application that performs a copy, like Maven does. Just make
sure you get the SVNKit used by Maven and use its code as a reference.
I think I'll get involved with trying to produce a recipe for this as
well.
AFAIK maven just shells out to the svn binary. The point where it fails is where it has made changes to your working copy and it is attempting to copy your (changed) working copy to a new URL.
So far all my attempts to make this fail have .... failed.
If I get some time today I'll try to find out more about what maven is doing, and how it is changing the working copy before it tries the copy.
|
|
RE: Re: Mac OS X + SVN 1.5.1 = Branch problem
> -----Original Message-----
> From: Mark Phippard [mailto: markphip@...]
> Sent: Wednesday, 20 August 2008 11:32
> To: Jeremy Whitlock
> Cc: Benjamin Kelley; users@...
> Subject: Re: Mac OS X + SVN 1.5.1 = Branch problem
>
> I do not believe anyone has said Maven uses SVNKit. I was
> simply pointing out that if it does, that is the next place to look.
I've just trawled through the maven SCM plugin source, and as far as I
can tell it uses the command-line:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/mave
n/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java?view=markup
I think I've checked every SVN file by now, and there are no references
to SVNKit or JavaHL.
Cheers
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
> AFAIK maven just shells out to the svn binary. The point where it fails is
> where it has made changes to your working copy and it is attempting to copy
> your (changed) working copy to a new URL.
I was misinformed. I recalled some information about SVNKit being
used but the patches to add the support were denied due to licensing
issues. I'll keep looking.
--
Take care,
Jeremy Whitlock
http://www.thoughtspark.org---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
|
|
Re: Mac OS X + SVN 1.5.1 = Branch problem
Mark Phippard-3 wrote:
On Tue, Aug 19, 2008 at 12:48 PM, Jeremy Whitlock <jcscoobyrs@gmail.com> wrote:
> Koichi,
> I was informed by Mark Phippard today that there was a change in
> Subversion's copy feature from 1.4.x to 1.5.x that might be the cause
> of this:
>
> * correctly set the peg revision for copy in JavaHL (r31994)
I think someone said this worked in 1.5.0 and not 1.5.1, so I flagged
the above change from 1.5.1.
One thing I am not sure of is whether Maven even uses JavaHL. It
might just run the SVN command line. If it does not use JavaHL, then
all bets are off. Likewise, someone should make sure it does not use
SVNKit, as that would then need to go to support@svnkit.com
--
Thanks
Mark Phippard
http://markphip.blogspot.com/---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
The problem occurs on the command-line as discussed on the Maven mailing list in this thread: http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html and particularly this response: http://www.nabble.com/Re%3A-AW%3A-Release-fails-during-SVN-commit-p19089435.htmlSpecifically, it appears to be a problem using svn cp with the working-copy as the first argument.
-Stephen
|
signature.asc (265 bytes) 