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.
Summary: | "Refresh Recursively" command doesn't work well if bad repository is entered. | ||
---|---|---|---|
Product: | obsolete | Reporter: | Jiri Kovalsky <jkovalsky> |
Component: | vcscvs | Assignee: | issues@obsolete <issues> |
Status: | CLOSED FIXED | ||
Severity: | minor | CC: | prgsust |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Kovalsky
2000-10-09 11:44:53 UTC
Files will have status [Local] when the repository can not be found. Fixed in main trunk (#62) and in boston branch (#1137). To tell the truth the fix was not probably generic. The behaviour now is this: Netbeans 3.1 & Community Edition 2.0: ===================================== "Refresh Recursively" immediately after mounting works as fixed (remains [Local]), but if "Refresh" is invoked on some file it changes to [Up-to-date] in spite of wrong repository set in mounting wizard. Internet Edition: ================= The behaviour remains exactly as described in this bug. It looks like the fix was not performed for this branch at all. The best way how to solve this user's mistake would be the simple question dialog that would warn user where is the problem and suggest him to change path to the correct repository (got from /CVS/Repository). Due to this bug can't be verified yet. BUG also appears in version : FFJ20 The above description is the correct behavior. - recursive refresh is not able to find out the correct folder due to bad CVSROOT configuration => the files are [Local] - refresh (of a single folder) knows which folder it is refreshing and therefore can set the status correctly (cvs status returns the right info because it can get it from CVS/Root) - Internet Edition: its currectly being changed to use vcscore, so I do no bugfixes to the IE now. Moreover bugs in IE should not be mentioned here and should not prevent bugs in open source being fixed. Due to above, I mark it as fixed again. It behaves exactly as it's described... so I verify this bugfix is OK. But this solution might confuse users so I entered new RFE bug #9036 Resolved for 3.4.x or earlier, no new info since then -> closing. |