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.
Here are the steps to create it: 1. mount a JavaCVS filesystem and connect to a server. do not checkout the files. finish the process 2. right click on the JavaCVS file system and select checkout. The following error occurs: *********** Exception occurred ************ Fri Feb 02 17:50:18 GMT+05:30 2001java.lang.NullPointerException: null java.lang.NullPointerException at org.netbeans.modules.cvsclient.commands.JavaCvsCommandFactory.readFromDisk (JavaCvsCommandFactory.java:222) at org.netbeans.modules.cvsclient.commands.JavaCvsCommandFactory.<init> (JavaCvsCommandFactory.java:79) at org.netbeans.modules.cvsclient.commands.JavaCvsCommandFactory.getInstance (JavaCvsCommandFactory.java:103) at org.netbeans.modules.cvsclient.IndependantClient.getCommandFactory (IndependantClient.java:149) at org.netbeans.modules.cvsclient.commands.FileSystemCommand.loadCommand (FileSystemCommand.java:348) at org.netbeans.modules.cvsclient.commands.checkout.CvsCheckout.initCommand (CvsCheckout.java:90) at org.netbeans.modules.cvsclient.commands.FileSystemCommand.run (FileSystemCommand.java:475) [catch] at java.lang.Thread.run(Thread.java:484)
Created attachment 544 [details] log file for the null pointer exception while executing JavaCVS checkout
if a .cvsrc file exisits this problem occurs. I fixed this problem by deleting that file. Maybe there was some error in the file which was not resolved. Will attach that file for further investigation.
Created attachment 548 [details] The rogue .cvsrc file. Deleting this fixed the problem.
Yeah. That's why I couldn't reproduce it according to your instructions. P4 (normal) is appropriate I suppose.
Version: 'Dev' -> 3.2
if there are no objections I'll close this bug.
One more remark.. This was a bug of mine. I was writing the messages for add and commit commands.. which is not correct. Currently (release32 - build 15/ development build 156) this bug is fixed.
on [NBdev-207]
Works fine.