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.
My Windoows login name includes an umlaut. By defaultthe .netbeans directory is created in a path that includes the umlaut. This bombs the compile of all projects created with these settings. This might turn off some first time users! The error message: C:\Documents and Settings\Jürgen Herrmann\WindowSampleApplication\nbproject\build- impl.xml:34: java.lang.IllegalArgumentException: Malformed \uxxxx encoding. BUILD FAILED (total time: 0 seconds) The offending line is a reference to another file: <property file="nbproject/private/private.properties"/> The contents of that file: user.properties.file=C:\\Documents and Settings\\J\ufcrgen Herrmann\\.netbeans\\4.0beta1 \\build.properties Note the representation of the umlaut. The workaround is to place .netbeans at a location where there is no special character and point private.properties to it.
Jesse probably something for you. Obvious workaround would be to place the project into some directory without umlaut.
I will look at it. Looks like problem in EditableProperties.
Silly bug which is fixed now. The problem happens only when NB userdir contains a character > 126. So if username contains such a character all projects will be broken because by default NB userdir is placed under user's home. On the other hand usernames usually do not contain these characters so P3 is appropriate. The only workaround is to put NB userdir somewhere else. The IDE has to be started as "nb.exe --userdir <some_other_folder>". The project created below such a folder should be OK. However reference from one project to the other where the reference would contain folder name with character > 126 would be broken again. Fixed in: src/org/netbeans/spi/project/support/ant/EditableProperties.java; new revision: 1.10; previous revision: 1.9 test/unit/src/org/netbeans/spi/project/support/ant/EditablePropertiesTest.java; new revision: 1.7; previous revision: 1.6
This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance.