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 57803

Summary:	[41cat] VCS settings in project's folder
Product:	obsolete	Reporter:	ulfzibis <ulfzibis>
Component:	vcscore	Assignee:	issues@obsolete <issues>
Status:	RESOLVED INCOMPLETE
Severity:	blocker	CC:	issues
Priority:	P2
Version:	4.x
Hardware:	PC
OS:	Windows XP
Issue Type:	ENHANCEMENT	Exception Reporter:

Description ulfzibis 2005-04-12 22:34:12 UTC

[ JDK VERSION : 1.5.0_02 ]

Now VCS settings are stored in netbeans_default_userdir.

In my opinion VCS settings more belong to the project, then to the netbeans general settings.

Then we don't have problems when switching between netbeans versions and importing settings when installing a new netbeans version.

Comment 1 Jesse Glick 2005-04-13 00:29:57 UTC

May already be in planning, I don't know details.

Not so simple as it sounds:

1. You may have many projects inside one VCS working dir. Which one stores the
VCS info? If one project is at the "top" and all others are inside it, OK, but
they may all be siblings inside the VCS dir.

2. It is possible to have a project partially inside a VCS and partially not -
most commonly when using a VCS-controlled source root with a non-controlled
project metadata dir.

3. VCS configuration may include per-user information, such as username, diff
options, even server location or proxy config, that you would not want to share.

Probable long-term solution is for the IDE's VCS support to autodetect working
directories (without requiring the Versioning Manager) for VCSs with adequate
metadata (e.g. CVS or SVN), with some optional added info kept in an appropriate
place in the working dir (e.g. $root/CVS/netbeans or $root/.svn/netbeans).

Comment 2 Martin Entlicher 2005-04-13 10:42:43 UTC

The autodetection was planned originally for 4.0, but was abandoned for
performance reasons. It might be added back when we get rid of a special VCS
filesystem.

I do not think this will ever solved by having VCS info in projects metadata,
VCS and projects are totally independent entities.

Comment 3 ulfzibis 2005-04-13 16:52:27 UTC

1. When I have a library or database which is referenced by different projects,
then I have a link to it stored in each project's settings. In case of database
or network path also username/password can be stored in these settings. Why not
have the same, when different projects refer to the same VCS working dir.

2. When at least 1 of many files in a project's filesystem is under VCS control,
you name this a "VCS-filesystem" and set a special icon. Why not only the
concerning branch ?

I am not familiar with all VCSs.. in case of CVS there is a folder "CVS" in the
subdir where this file is located.
When I include such a project into my netbeans IDE I see this normaly hidden
"CVS" folder in the filetree, when I don't have included the according
VCS-settings. This looks not very nice. Then I have to investigate a file like
'org-netbeans-modules-vcs-advanced-CommandLineVcsFileSystem_2.xml' and copy it
by hand, to be able to use the CVS-command support.
Why not have a copy of this file (perhaps without username/password) in the
projects folder, and ask for install/activate it when including the project,
and/or have a context menu item for this.