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.
i'm running mercurial over svn repo using hgsvn. but netbeans recognizes the repo as subversion repo which means netbeans is not usable for hgsvn repo and i have to do hg commits on console. hgsvn info: http://cheeseshop.python.org/pypi/hgsvn hgsvn repository contains .hg dir, .hgsvn dir and also .svn dirs. so i guess netbeans checks the repo for svn info before it checks for hg info which in this case causes the problem. i didn't see the netbeans code but maybe simply switching the order (hg first, then svn) would fix this problem. i did not test this with older versions of netbeans but i guess the issue is there too.
You are right, it depends on the order in which present versioning systems are tested. It would probably suffice to modify the order of the versioning systems. We're planning to look into this in the next release. We've never supported multiple repos => P2 enhancement.
fix: http://hg.netbeans.org/cdev/rev/ec06cc1dc814
You should now be able to specify the order of versioning systems. So you can manually say that e.g. mercurial precedes subversion, etc. In order to do that, set priority property of each versioning system, i.e. run IDE with these commandline switches: -J-Dversioning.subversion.priority=PRIORITY -J-Dversioning.mercurial.priority=PRIORITY -J-Dversioning.cvs.priority=PRIORITY So in your case this should be enough: -J-Dversioning.mercurial.priority=1 -J-Dversioning.subversion.priority=2
Integrated into 'main-golden', will be available in build *201003081350* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/ec06cc1dc814 User: Ondrej Vrabec <ovrabec@netbeans.org> Log: Issue #174305 - hgsvn repo should be resolved as mercurial repo, not svn repo versioning systems are now sorted in user-defined order
VCS priorities have been deprecated in 7.1 and will not work any more. Instead use the Disconnect feature as described in bug #146824 (in short Team -> Subversion -> Disconnect)