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.
This bug has been introduced by the fix for bug #252544 It has been recently integrated into main-silver, it's available in build *201507170001* This fix allows the user to decide if an update should or not be performed after a pull. It works very well but the versioning label still showing "tip" position for the working copy after a not updated pull. Steps to reproduce: 1. Start a new Java project Project1 2. Init mercurial repo for Project1 and commit initial revision 3. Clone Project1 to Project1_clone0 4. Make a change in Project1 and commit it 5. Enable view -> show versioning labels 6. Go to Project1_clone0 and pull from Project1 7. Answer "No" in the update after pull dialog Expected result: After the pull has been completed and update not performed, versioning label should change to specify the working copy revision. But it still showing "Project1_clone0, default tip". Then, if we simply open the update dialog (team -> update) AND CANCEL the action, the label refreshes showing the current working copy revision hash.
fix: http://hg.netbeans.org/core-main/rev/5c8a8a9da66d
Integrated into 'main-silver', will be available in build *201507190001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/5c8a8a9da66d User: Ondrej Vrabec <ovrabec@netbeans.org> Log: #253539 - Versioning label not refreshed after no updating pull Pass command name always right after the hg executable in the CLI arguments so our logic correctly recognizes the type of command and refreshes working copy info after it finishes.
Verified. Thank you!