I am not convinced that Eclipse is telling you the whole story.
On Tue, 2008-04-15 at 14:44 +0100, Simon Brooke wrote: > Sorry to be a pest. I'm still getting > -Titan-Dominion: cvs [commit aborted]: Message verification failed We still don't understand *why* we are getting this message. What failed ? My gut feeling is that your users did not supply a log message in the expected format, and then Eclipse did not report the whole error. Can you confirm that users using Eclipse, and entering a log message of the format: "bug 1234: This is a log message that exceeds the minimum of 50 characters configured in the glue" are still getting this error message ? Eclipse vs Tortoise vs cvs client vs joeShmoe client are irrelevant of the Scmbug integration. The Scmbug integration does not magically behave differently. The Scmbug integration WORKS. Its stored in the repository, NOT the client. But if the client sends junk Scmbug refuses to let through, then the problem is that the client sends junk: it's NOT a Scmbug issue. It's a client issue. > I can advise my users to commit only through Tortoise client since they > all have it, but I'd prefer to fix the issue. My feeling is that the above is "the" issue.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
