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.
As in http://blogs.oracle.com/geertjan/entry/the_case_for_profiles_part1 create an app with multiple branding variants of some resource, e.g. o-n-c-windows.jar. Start in one branding on a fresh userdir; the branded resources are available as expected. Now start in another branding on the same userdir; the base(r) resources are used, not the branded resources. Putting a debug println into LocaleVariants.findLocaleVariantsOf confirms that the list of JARs from the initial branding is being used. The current code uses the mapLocale field to produce the right results when using --locale is changed between runs, but this does not extend to --branding. Introducing a new field in the serial form sounds too dangerous, but other possible fixes are: 1. Prepend NbBundle.getBranding + '_' to mapLocale; i.e. replace all usages of Locale.getDefault() in the class with some method which prepends the current branding (if not null). (Including in getLocalizingSuffixesFast, meaning the lastBranding field could be removed.) 2. Get rid of mapLocale, and instead append branding and locale to the cache key name "localeVariants". This has the minor advantage of making startup faster when switching back and forth between locales and/or brandings.
It would be great if this were fixed. Another use case is, for example, where the "Next" button in a wizard needs to have different texts on different panels. Here, if NbBundle.setBranding were to work correctly, multiple branding bundles could be available and when the user switches to a new panel in the wizard, a new branding bundle could be loaded via NbBundle.setBranding, with the result that the text in the "Next" button would be changed to the value set in the new branding bundle. (I.e., in one case "Next" would be branded to "Advance", while in another case the text should be "Send".)
(In reply to comment #1) > Another use case [...] Very different from this bug, and will not be implemented; we do not support changing branding or locale at runtime.
ergonomics#708491051468 branding & locale is now checked. Still I don't think it is possible to change branding while the application is running.
*** Bug 200730 has been marked as a duplicate of this bug. ***
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/708491051468 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #199320: Including branding and locale into the cache time stamp
mapLocale is now obsolete and ought to be deleted, right?
*** Bug 201793 has been marked as a duplicate of this bug. ***
*** Bug 204467 has been marked as a duplicate of this bug. ***
possible candidate for the 7.0.1 patch (7.0.1 is used as Studio platform)