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.
I like netbeans after use the large and easy-freeze jbuilder and trouble eclipse. netbeans is cool! I like it, but I had to say sometimes it is very stupid 1) when I try to new a j2me project with complex source and resource directory, I want to set the source path to 2 directory, but the netbeans only allow me to set only one directory! 2) when I work with a project which includes .jpp files that should be preprocessed. First I want to read the un-preprocessed source .jpp files, so I set the source path to the direstory jpp, then after run the build.xml write by myself, the generated .java files are saved to src subdirectory, but I can not change the source path setting to the new directory. 3) if I write Chinese words in the application properties description, so there are Chinese words in .jad and manifest.mf. But they are wrong char because wrong encoding handling even I set the encoding of project to UTF-8. It seems that someone ant task can not hanld encoding correctly. I hope these bug are fixed in the coming 4.2.
re 1,2 - to support other than default preprocessor you need to change ant script anyway. I'd recommend to create another directory with .jpp files and view them using Favorites or Files view and save .java files into src. In addition, for 4.2 we are planning to improve internal preprocessor so that it supports #if, #else, etc. directives. It might help you to use NB out-of-box without a need for an external preprocessor. re 3 - it may be a bug we need to check it.
re 3 - yes, some of the Ant task do not care about encoding at all and use JVM default file encoding. You can force UTF-8 as your default encoding by giving the -J-Dfile.encoding=utf8 argument to the NetBeans launcher and then no Chinese nor other locale specific word will be destryoed and all the JADs will be stored in UTF-8 encoding. Or you can use any encoding that is able to handle all your characters and then JADs will be stored in your specified encoding and Manifest always in UTF-8. The Encoding property under Build / Compiling category affects the only sources (preprocessing and compilation process). BTW have you seen Forrest Gump ?
fixed even the last part (encoding of the application descriptor)
verifying all old issues