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 192254 - Per-project RCS
Summary: Per-project RCS
Status: RESOLVED DUPLICATE of bug 146824
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Mac OS X
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-22 02:04 UTC by dalin
Modified: 2010-11-25 13:42 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 dalin 2010-11-22 02:04:52 UTC
I'm a web developer and I usually check out libraries and modules from
multiple different RCSes (SVN, CVS, Bazaar and Git) and then manage my project
with SVN (someday I'll switch to Git).  However Netbeans gets all confused about which VCS to use for any given file.  My experience is that if you have more than one RCS in a project NB will eventually screw up and choose the wrong RCS.

In Netbeans 6.8 and 7.0 I can just disable the CVS and Mercurial plugins, then use the CLI for working with those RCSes.  This works for my primary use-case.  However sometimes I work on projects that use one of those RCSes.  To be able to use NB in both situations I must manually dis/enable the appropriate plugin every time I switch projects.  

A better way would be to have the RCS selectable per-project.  The default could be "auto" where, just like it is now, NB makes a best-guess at what RCS to work with for any given file.  With the option of going into the project "Properties" window and choosing a specific RCS on the "Sources" tab.
Comment 1 Tomas Stupka 2010-11-25 13:42:53 UTC
this should be fix via solution suggested in #146824

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