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.

Bug 213438 - unable to build netbeans ide from sources using german locale
Summary: unable to build netbeans ide from sources using german locale
Status: NEW
Alias: None
Product: nblocalization
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.2
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: issues@nblocalization
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-02 23:42 UTC by toben
Modified: 2012-06-12 09:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description toben 2012-06-02 23:42:51 UTC
Product Version = NetBeans IDE 7.2 Beta (Build 201205031832)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0_04
Runtime = Java HotSpot(TM) Client VM 23.0-b21

I followed all your advises to build netbeans itself from sources. This did not succeed because of module websvc.saas.api. Here are some classes created using JAXB xjc compiler. This results in java files with the german version of this header:

//
// This file was generated by the JavaTM Architecture for XML Binding(JAXB) Reference Implementation, v2.2.5-2 
// See <a href="http://java.sun.com/xml/jaxb">http://java.sun.com/xml/jaxb</a> 
// Any modifications to this file will be lost upon recompilation of the source schema. 
// Generated on: 2012.06.02 at 11:55:06 PM CEST 
//

This header includes in the german version some characters which are not UTF-8 compatible. The build fails. This could be problematic in different locales as well. 

I could solve this starting your ant build script with a different user language (-Duser.language=EN). 

Maybe you could give some information on this issue on your wiki page.
Comment 1 pgebauer 2012-06-12 09:26:07 UTC
Since a header includes characters which are not UTF-8T, the problem seem to be in the localization.
Comment 2 toben 2012-06-12 09:48:56 UTC
> Since a header includes characters which are not UTF-8T, the problem seem to be in the localization.
The localization of JAXB delivers this. But the real problem is, that the source files are generated using the operating system file encoding. Cp1252 in windows. All relates to http://java.net/jira/browse/JAXB-499. But this one seems to be already fixed. So maybe the solution is to upgrade your JAXB version?