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.
After removal JavaCVS all user project configurations that used JavaCVS are broken. In 3.5 (or older dev build that still contained javacvs module) mount a CVS repository using javacvs, select a directory and add it to project. A link pointing to the directory is created in the Project Tab Now switch to new dev build and open the same user directory with it. The link in project tab is now broken.
This is caused by the fact that the new CVS filesystem has different getSystemName() that the old one and as links store this name, they are not valid anymore. Simple fix would be to keep the system name unchanged.
This is a problem of the javacvs compatibility module. Reassigning to javacvs. Thanks for the evaluation, I will keep the original system name.
Fixed in trunk. Support for preferred system name added into VcsFileSystem: /cvs/vcscore/src/org/netbeans/modules/vcscore/VcsFileSystem.java,v <-- VcsFileSystem.java new revision: 1.241; previous revision: 1.240 The preferred system name is stored persistently: /cvs/vcsgeneric/src/org/netbeans/modules/vcs/advanced/projectsettings/CommandLineVcsFileSystemInstance.java,v <-- CommandLineVcsFileSystemInstance.java new revision: 1.28; previous revision: 1.27 And finally the preferred system name is set by javacvs compatibility module: /cvs/javacvs/compat/src/org/netbeans/modules/cvsclient/NbJavaCvsFileSystem.java,v <-- NbJavaCvsFileSystem.java new revision: 1.3; previous revision: 1.2
When 3.6 uses user-directory created in 3.5, it raises StringIndexOutOfBoundsException (when starting). Also statuses of nodes are [Updt; x.x]. But status should be [Up-to-date; x.x].
Created attachment 14472 [details] StringIndexOutOfBoundsException
The attached "exceptoin.txt" is not an exception, but ide.log. Please attach the exception. Also, this is likely not P1, like the original issue was. So this should probably be submitted as a separate issue, if the project tab is O.K.
This exception has nothing to do with this issue. It's some another problem.
Verified in -NetBeans 3.6