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: | Broken toolbars after upgrade from 3.2 to 3.3 | ||
---|---|---|---|
Product: | projects | Reporter: | Jan Zajicek <jzajicek> |
Component: | Ant | Assignee: | Jesse Glick <jglick> |
Status: | CLOSED DUPLICATE | ||
Severity: | blocker | CC: | dsimonek, mslama |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jan Zajicek
2001-09-14 11:54:51 UTC
The probable reason is that xml config files storing toolbar configurations were not found. See methods Workspace.set/getToolbarConfigName. It is not a window system bug but an ant module bug. If you upgrade from 3.2 to 3.3 using userdir form 3.2, toolbar configuration files are recognized by AntProjectDataLoader instead of XMLDataLoader. "xml" extension is serialized for AntProjectDataLoader and used in 3.3 instead of MIME type which should be used rather then the extension. That's why XML files are recognized by AntProjectDataLoader. Proposed fix (diff follows): add a version ID into AntProjectDataLoader and implement writeExternal() method which will externalize this ID. Try to read ID in readExternal() method. If it is not possible to read ID, remove "xml" extension and MIME type will be used instead of the extension. 37a38 > private static final int VERSION = 1; 86a88 > oi.readByte(); 89a92,94 > } catch (IOException exc) { > getExtensions().removeExtension("xml"); //NOI18N > initialize(); 92c97,102 < --- > > public void writeExternal (ObjectOutput oo) throws IOException { > super.writeExternal (oo); > oo.writeByte(VERSION); > } > Already reported. *** This issue has been marked as a duplicate of 15547 *** Fixed for upgrading from 3.2, but still occurs when using Import wizard when first starting ide and perform importing from nb3.1 or FFJ2.0CE. Can ant loader still be involved? I don't know, it's possible the fix only worked correctly for imports from 3.2, though I thought it should be fine for all; I will try to figure out what is going on. This is still the same, please use #15547 for details... *** This issue has been marked as a duplicate of 15547 *** Resolved for 3.3.x or earlier, no new info since then -> closing. Resolved for 3.3.x or earlier, no new info since then -> closing. |