This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 44128 - Need to have a way to specify several "successful" exit statuses (for e.g. cvs diff)
Summary: Need to have a way to specify several "successful" exit statuses (for e.g. cv...
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 4.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-01 20:46 UTC by Jesse Glick
Modified: 2009-12-21 07:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-06-01 20:46:30 UTC
If you run a (textual) CVS diff command, and there
are any differences, the status line in the VCS
Output window shows "Command failed.". This is
quite misleading to the user. Probably the cvs
command returned 1 - meaning yes there were
differences. If the command really failed, it
would have returned 2 (I guess).
Comment 1 Martin Entlicher 2004-06-15 11:33:55 UTC
Right. The problem is, that the command executor suppose that when the
exit status != 0, the command has failed. This is true for most
commands. We have a special flag set on diff command, that the failure
should be ignored, so in this case the message should say simply that
the command finished (like the message in the status bar).
This is already described in issue #42377.

But you're right, that a better fix would be to consider both exit
status 0 and 1 as a success, not a faiure and handle exit status 2 as
a failure. For that we would need to have a list of "successfull" exit
statii for every command.
Comment 2 Martin Entlicher 2004-06-15 14:21:47 UTC
After the fix of issue #42377 this is not so important IMO.
This is somewhere between enhancement and defect, I'm also chanig the
summary to better describe the problem.
Comment 3 Quality Engineering 2009-12-21 07:17:32 UTC
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team