Hello Thomas,
> Thanks for commenting. This is good news. Interessting that this is
> dependent on the file size. Anyway, when is there going to be a new
For performance reasons, as there is no "setReadonly(false)" method in
java.io.File, SVNKit calls external program "attrib" or "chmod" for
large files and makes a copy and rename for small files (this makes the
file writable).
> Mark, I guess you are planning to release 1.10 with a current version of
> svnkit too?
I hope we will get SVNKit 1.1.1 finally released on Tuesday. After that
Mark could make another release of Subclipse with new version of SVNKit
if nothing else prevents it.
Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!
Thomas M. Hofmann wrote:
> Hi Alexander,
>
> Thanks for commenting. This is good news. Interessting that this is
> dependent on the file size. Anyway, when is there going to be a new
> release of svnkit that includes the fix?
>
> Mark, I guess you are planning to release 1.10 with a current version of
> svnkit too?
>
> -----Original Message-----
> From: Alexander Kitaev [mailto:Alexander.Kitaev@svnkit.com]
> Sent: Donnerstag, 11. Januar 2007 12:09
> To: dev@subclipse.tigris.org
> Subject: Re: [Subclipse-dev] Another bug in new locking code in 1.1.9
>
> Hello,
>
> This bug is already fixed in the latest version of SVNKit in "trunk".
> Readonly flag was not removed on files large than 100k in size.
>
> Alexander Kitaev,
> TMate Software,
> http://svnkit.com/ - Java [Sub]Versioning Library!
>
> Mark Phippard wrote:
>> On 1/10/07, *Thomas M. Hofmann* <email@thomashofmann.com
>> <mailto:email@thomashofmann.com>> wrote:
>>
>> Hi again,
>>
>> I have built a new version based on head and deployed it to some
> of my
>> co-workers. Today one of them called me because he noticed some
> strange
>> behavior. I had a look and saw that the read only flag was not
> removed
>> after a file was locked (using svnkit). I created a new file and
> the
>> problem did not occur. I thought about problems with blanks in the
>> filename / path but renaming the new file for testing to a name
> with
>> balnks still did not show the error. The files already in the
>> repository
>> all showed the errornous behavior (all I tried at least).
>>
>> So this is pretty strange and difficult to pin down. Any ideas?
>>
>>
>> Have you tried bringing up the issue on the SVNKit mailing list yet?
>> That is what I would recommend.
>>
>> --
>> Thanks
>>
>> Mark Phippard
>> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Fri Jan 12 16:14:46 2007