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.
If I open a project which is located in directory C:\tmp\nikm\samples\ on my Windows system (for example C:\tmp\nikm\samples\Args1-IZ86820), 10 error messages about I/O exceptions appear in console window: getCanonicalFile() on file C:\tmp\ftp:\ftp.chg.ru\pub\sourceware\cygwin failed. java.io.IOException: The filename, directory name, or volume label syntax is incorrect ... getCanonicalFile() on file C:\tmp\ftp:\ftp.chg.ru\pub\sourceware\cygwin failed. java.io.IOException: The filename, directory name, or volume label syntax is incorrect Probably it happens because Cygwin created an interesting directory in c:/tmp C:\tmp\ftp%3a%2f%2fftp.chg.ru%2fpub%2fsourceware%2fcygwin But it is still not clear why getCanonicalFile() has a problem with this name, and why this error message is repeated 10 times. After a small investigation I found out that there is nothing in "cnd" source code, that can print these messages. Looks like they are printed by standard java filechooser, which is used in our "Open Project" process. Here is the scenario: ===================== File -> Open Project - file chooser appears and shows my home directory - navigate to C: - so far so good - double click on "tmp" node - 10 error messages about I/O exceptions appear on console: getCanonicalFile() on file C:\tmp\ftp:\ftp.chg.ru\pub\sourceware\cygwin failed. java.io.IOException: The filename, directory name, or volume label syntax is incorrect I use jdk1.6.0, and I did not see these messages before, probably because previously I used jdk1.5. I'll try the same test case with jdk 1.5, and file a bug against jdk.
I verified that if I use jdk1.5.0_08 - there are no messages on console. If I use jdk 1.6.0 - there are error messages about I/O exceptions, so it is a bug in jdk1.6.0 (I'll file it if it is not filed yet). I suggest to keep this issue open, because other users can see similar problems, and will be able to find an explanation very easy. As soon as this bug is fixed in jdk1.6 I'll mark this issue fixed.
Please don't keep duplicate bugs open in CND. Did you file the JDK bug yet? Will close this one as INVALID because there is nothing to fix in CND as I understand it.