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.
see 118174 on j2se - all the info and gifs are there and it happens for this kind of project also. Tomas Mysik is aware of the situation from other mails. I will file on j2ee project and mobility also. Am assuming separate issue not needed for web freeform project ?
Fix for #118174 applied for Web, EJB and AppClient projects. Checking in j2ee/clientproject/src/org/netbeans/modules/j2ee/clientproject/resources/build-impl.xsl; /cvs/j2ee/clientproject/src/org/netbeans/modules/j2ee/clientproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.23; previous revision: 1.22 done Checking in j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.77; previous revision: 1.76 done Checking in web/project/src/org/netbeans/modules/web/project/resources/build-impl.xsl; /cvs/web/project/src/org/netbeans/modules/web/project/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.159; previous revision: 1.158 done
its ok in ja locale on solaris, using utf-8 default project encoding. However, having a new project with euc-jp encoding, it still does not work as per original issue, it can't find the path to the project since project name and also nb project dir has mbyte in its name. Even using the suggested javadoc options mentioned below using EUC-JP as the value does not help. j2se related issue on this was reopened also for same reason, 118174. ken.frank@sun.com
WONTFIX, see issue #118174 for more information.
See issue #118174.
I noticed that for the other issue, the fix was going to be done for utf-8; should that be done for this one also ? or maybe utf-8 was the way this was originally and nothing needs to be done ? ken.frank@sun.com
Fixed like in J2SE project. Please verify, thank you. Checking in j2ee/clientproject/src/org/netbeans/modules/j2ee/clientproject/resources/build-impl.xsl; /cvs/j2ee/clientproject/src/org/netbeans/modules/j2ee/clientproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.24; previous revision: 1.23 done Checking in j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.79; previous revision: 1.78 done Checking in web/project/src/org/netbeans/modules/web/project/resources/build-impl.xsl; /cvs/web/project/src/org/netbeans/modules/web/project/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.162; previous revision: 1.161 done
*** Issue 118434 has been marked as a duplicate of this issue. ***
This is seen in all kinds of projects now, at least on solaris, where project encoding is not utf-8, but for example when user in ja locale and use euc-jp encoding; sometimes even user in utf-8 encoding the problem happens. I think for this one and the other issues referred to, there is not really a fix for this situation but it was closed as will not fix ? what is user supposed to do in this case ? I don't think that requiring them to create project not in another encoding is valid since that is one reason for new project encoding properties and feq. please clarify. ken.frank@sun.com
Using Solaris 10 javadoc lwas generated ok for Web, VisualWeb, EJB, Java App I tried with Mozilla, ja locale using UFT-8/x-euc-jp project encodings, build 1104