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: | Locale variants not supported by <branding> | ||
---|---|---|---|
Product: | apisupport | Reporter: | mkash |
Component: | Harness | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | johan_walter |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
mkash
2011-01-21 08:19:12 UTC
Here is another case of the same problem: http://netbeans-org.1045718.n5.nabble.com/Netbeans-builds-wrong-locale-branding-td3044192.html The current harness does not have any solid support for localization in general. The <branding> task is not designed to manage more than one variant of resources, so placing localized and unlocalized branded resources in a single dir is a mistake. You can create a separate dir for localized branded resources and add a special target calling <branding> into your suite's build.xml, just as you can manually set up a dir for localized but unbranded resources. http://wiki.netbeans.org/DevFaqMavenL10N also discusses how to do this sort of thing using Maven. OK. Thanx for the explanation. I'll give it a try. *** Bug 195184 has been marked as a duplicate of this bug. *** |