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 180658 - Mercurial is not refreshed after external init
Summary: Mercurial is not refreshed after external init
Status: RESOLVED DUPLICATE of bug 200267
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Ondrej Vrabec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-12 07:00 UTC by Petr Jiricka
Modified: 2011-07-21 07:15 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2010-02-12 07:00:17 UTC
1. Create a project
2. Go to command line and do hg init in the project root directory
3. Go back to IDE - the IDE does not recognize that this is a hg project, does not offer any hg actions such as commit, and still offers "initialize repository" action.

The only workaround I found is to restart the IDE:
- closing and reopening the project does not help
- Source -> Scan for external changes does not help
Comment 1 Ondrej Vrabec 2010-02-12 07:18:48 UTC
That's why we have Mercurial > Initialize action which does the same as hg init, why don't you use that action exactly?

The information about a folder being versioned/unversioned is cached inside the versioning core support and is refreshed only by certain versioning actions (one of them is the Mercurial -> Initialize). Constant rescanning would heavily slow down the IDE.
Comment 2 Petr Jiricka 2010-02-12 07:32:48 UTC
> why don't you use that action exactly?

In the IDE in general we try to follow the principle that any external changes must be picked up. This is true for the editor indexing support, for the file/project explorer etc. 

I understand the requirement not to slow down the IDE, so it's ok if the refresh is not immediate/automatic. But at the very least, the "Scan for external changes" action should recognize such a change.
Comment 3 Ondrej Vrabec 2011-07-21 07:15:50 UTC

*** This bug has been marked as a duplicate of bug 200267 ***