[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Subclipse not working when post-commit hook was used

From: alsacmem <yixtang_at_yahoo.com>
Date: 2007-04-11 20:06:06 CEST

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.

Jack Repenning-2 wrote:
> On Apr 6, 2007, at 9:06 AM, alsacmem wrote:
>> But, when
>> I tried to commit files from Eclipse+subclipse (on Windows XP),
>> each time, I
>> got the following error message, and no email was sent. Once I
>> disabled
>> post-commit hook, everything worked fine.
>> "
>> svn: Commit failed (details follow):
>> svn: Commit failed (details follow):
>> svn: MERGE request failed on '/svn/repos/test/trunk'
>> svn: Processing MERGE request response failed: The content of
>> elements must
>> consist of well-formed character data or markup. (/svn/repos/test/
>> trunk)
>> "
> Hmmm ... something odd about your experimental results, here. A
> post-commit hook, as you suspected, has no power to fail a commit.
> Furthermore, a post-commit hook has no effect on the "MERGE request
> on '/svn/repos/test/trunk'" (this doesn't mean the familiar merge in
> your working copy, but rather the WebDAV "MERGE" command that
> constitutes the central action of any commit ... roughly translatable
> as "stuff this in, please."). And, finally, if the MERGE request
> fails, there really ain't gonna be no new revision in the repo, as
> you report there was. This is too many "impossibles" for one
> experiment; you should check for some other change you made while
> enabling/disabling the post-commit hook, or some other correspondence
> between things you thought were related but actually aren't.
> Post-commit hooks have been known, for example, to do additional
> commits of their own (and that's perfectly legal, though it can be
> tricky). So, for example, if your post-commit hook script not only
> sends email but also checks in some status file containing the
> revision number of the last revision for which email was sent, then
> this *second* commit (not the one you made yourself) might be the one
> having MERGE difficulties.
> -==-
> 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

View this message in context: http://www.nabble.com/Subclipse-not-working-when-post-commit-hook-was-used-tf3537518.html#a9944390
Sent from the subclipse - users mailing list archive at Nabble.com.
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:06:23 2007

This is an archived mail posted to the Subclipse Users mailing list.