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.
Updater cant be reasonably localized/branded using standard NetBeans branding system. The change will require modifications in all NetBeans startup scripts.
Due to the complexity of the change this won't be done in 3.5
See arch description for autoupdate for more...
Summary was confusing - looked like it referred to downloaded modules.
Could someone point me to more detailed description of what this issue is about; I want to get feedback from l10n groups on it also. ken.frank@sun.com
Ken you probably don't need to care about this, it is primarily a code issue.
I found relatively easy to implement workaround. It is of course not good idea to copy all branding code to updater. jar, but as we have only one JAR file to brand we can easily hardcode the looking for the branding. Branding for IDE is stored in <netbeans>/lib/branding file, so you can easily read this file and look for the branding to libs/locale/updater_....jar. I'm also raising the priority because this is showstopper for using NetBeans as a binary.
Updater now follows the NetBeans branding rules. Branding.properties file is obsoleted and should not be longer used.
I just tried in today's dev build to update some NBMs that had needsrestart="false", so the updater runs w/o an IDE restart. The AU splash screen appeared but was just a blank blue window with no image or text.
Wrong classloader when running updater from inside the IDE. Should be fixed now.
x