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 11590 - revision explorer actions work on wrong file
Summary: revision explorer actions work on wrong file
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscvs (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-20 02:46 UTC by Rochelle Raccah
Modified: 2001-07-20 20:11 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 Rochelle Raccah 2001-04-20 02:48:26 UTC
Because of issue 11589, I was forced to find a workaround to cvs remove a
secondary file:
Open the revision explorer, cvs remove the mapping file, do the action which
causes delete in the main explorer, cvs commit the mapping file in the revision
explorer.

However, The explorer and revision explorer didn't update nicely at all.  I had
to be very patient and keep refreshing, or just ignore icons and labels
altogether.  In addition, sometimes, when I tried to do the cvs commit step on
the secondary file, it tried to work on the primary file!  I could tell by
looking in the title bar and the contents of the message didn't say removing the 
secondary file.
Comment 1 Martin Entlicher 2001-04-20 10:13:05 UTC
Changing component to vcscvs, since it probably applies to vcscvs module.
Comment 2 Martin Entlicher 2001-04-20 19:26:44 UTC
The refreshing is still probably a little buggy, but the actions of Revision
Explorer should act on proper files now. Fixed in the main trunk, will be merged
to release32 branch tomorrow.
Comment 3 Martin Entlicher 2001-04-21 18:21:03 UTC
The Revision Explorer problem fixed in release32 build #35.
However, the refreshing still does not work nice, when one file is locally
removed and the second is up-to-date. Therefore I entered issue #11631 for that
and closing this issue as resolved/fixed.
Comment 4 dmladek 2001-04-26 16:50:28 UTC
verified on [NB32-38, RC4]
Comment 5 Jan Chalupa 2001-05-06 15:36:34 UTC
Target milestone -> 3.2