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.
Development build #200310010100 of NetBeans 4.0 Windows 2000 SP2 with JDK 1.4.2 build 28 Description: ============ Default "CVS|Locking|Lock" command locks always last trunk revision even if certain branch is checked out. It may lead to some confusion if user does not double check the result. Steps to reproduce: =================== 1. Mount CVS filesystem using command-line client. 2. Update some file to some branch. 3. Invoke "CVS|Locking|Lock" command on it. 4. Invoke "CVS|Log" to find out that the trunk was locked.
Then it looks like a bug of cvs. The manual says: -l[rev] Lock the revision with number rev. If a branch is given, lock the latest revision on that branch. If rev is omitted, lock the latest revision on the default branch. I suppose that the "default branch" should be the current branch to which the file is updated? I'll check the behavior...
Yes, I saw the help too. My understanding was that '-l 1.3' will lock specific revision, '-l myBranch' will lock last revision of myBranch and '-l' will lock last revision in main trunk. Maybe it's really failure of cvs.
A simple solution would be to always ask the user. But perhaps we should find the branch name from Entries and if there is one, give it to the lock command by default. The same must be performed for unlock then.
Yes, I had something like this in my mind ...
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