Bug 161542 - [Commands] The CVS commitinfo only display in the CVS Console
Summary: [Commands] The CVS commitinfo only display in the CVS Console
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-10-19 06:03 EDT by Thomas Kappen CLA
Modified: 2019-09-06 16:08 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Kappen CLA 2006-10-19 06:03:39 EDT 
This is rather a feature request than a bug.

Other CVS clients like WinCVS, Tortoise or even the console client, are displaying the response from the commitinfo script in their window. Not so the Eclipse CVS-Plugin. The CVS-Plugin just displays the following message:
cvs commit: Pre-commit check failed
cvs [commit aborted]: correct above errors first!

It would be nice, if the Eclipse CVS-Plugin also displays the output of the commitinfo script.

P.S.: I assume the output from other cvs scripts, like verifymsg, will also not be displayed from the Eclipse CVS-Plugin.
Comment 1 Jerome Lanneluc CLA 2006-10-19 06:27:50 EDT 
Moving to Platform CVS
Comment 2 Michael Valenta CLA 2006-10-19 08:52:31 EDT 
The information is displayed in the CVS Console but I agree that it would be better if it were displayed in the dialog. The problem is that CVS returns this information as messages (i.e. M tag). Currently, we do not display M messages in the error dialog because there are just too many of them and there is no easy way to distinguish the useful ones from the noise. Because of this, we added a button to the error dialog to display the CVS Console. 

We do not plan on doing any further work in this area but are happy to accept patches.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:08:52 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.