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.
Summary: | Javadoc generation from module projects does not honor encoding | ||
---|---|---|---|
Product: | apisupport | Reporter: | Ken Frank <kfrank> |
Component: | Harness | Assignee: | Jesse Glick <jglick> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | Keywords: | I18N |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
image
image |
Description
Ken Frank
2007-07-04 19:36:03 UTC
I'm not really sure what this is about. Module projects always use UTF-8 encoding, and none of our samples currently use non-ASCII chars in source code that I know of. If you have encountered a specific problem, please reopen with detailed steps to reproduce. reopening with more info first of all, typo in summary referred to moblity samples instead of nb module samples. this is seen, at least on solaris, when have paint app in folder with multibyte in a java file - would this happen for paint app (besides comments ?) Can users change some part of the app as to UI and as part of that have multibyte in a label and thus have it be in the code ? (and thus the warnings would happen) its not related to having mbyte be in the path to the project. see attached gif for the warnings, but the javadoc does compile. clean and build does work ok, which is different than was in other sample projects, where the warning was seen there. 1. create paint app, on solaris, in ja locale; am using pseudo localized nb but thats not important since this is not about messages/labels 2. add some multibyte to java file - even comments. 3. go to the Paint project and choose generate javadoc 4. warnings similar to seen in attached gif will be seen. 5. default encoding was not changed of this project nor of other projects in this ide or other ide session with same userdir. 6. also, and perhaps unrelated - see 2nd gif for the top line in left side of browser that shows the javadoc - the mbyte is not correct - this is from something from translation of javadoc msgs - when choosing the view->encoding to use the same encoding as chosen now, the mbyte shows ok. --> so if its not allowed or would not normally happen that mbyte would not be used in the paint or other sample, and #6 is not a problem, then this can be reclosed. ken.frank@sun.com Created attachment 44849 [details]
image
Created attachment 44850 [details]
image
Specifying encoding for <javadoc> therefore. Checking in nbbuild/javadoctools/template.xml; /shared/data/ccvs/repository/nbbuild/javadoctools/template.xml,v <-- template.xml new revision: 1.73; previous revision: 1.72 done Checking in apisupport/harness/release/build.xml; /shared/data/ccvs/repository/apisupport/harness/release/build.xml,v <-- build.xml new revision: 1.27; previous revision: 1.26 done v |