On Apr 11, 2007, at 11:15 AM, Mark Phippard wrote:
> On 4/11/07, alsacmem <yixtang@yahoo.com> wrote:
>>
>> Thanks Jack for replying to my questions. I should also have
>> mentioned
>> that, I performed the same tests (with same repository) on a Linux
>> box using
>> svn commands in commandline env, everything (commit, post-commit,
>> email
>> notification, ...) worked like a charm. So, I am guessing the
>> problem I
>> experienced must be of Eclipse and/or Subclipse things. I am
>> working on it
>> to see if I can figure out something.
>
> Subclipse cannot be the direct problem as we do not communicate with
> your repository. We run an SVN API and the API provider does the
> rest. So if you are using SVNKit, then perhaps it is doing something
> different.
>
> That being said the way that Subversion is architected by the time it
> gets to calling a hook script there is nothing about the client that
> should be possible to matter. The server controls all of that.
Yeah, I think Mark's original reflex ("look to SVNKit") sounds most
promising. Look also to the specific version of SVN on the client end.
But I have a very distinct sense of "shooting in the dark" about all
this, so more data seems the most important thing.
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Apr 11 20:24:18 2007