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.
If I run pilsen_fcs build with userdir from boston IE the loaders are not ordered correctly. ServletDataLoader is not before JavaDataLoader as is specified in manifest. After disabling and enabling of module they are sorted correctly. Maybe that one of the reasons is that ServletDataLoader was not present in boston. It is a new class.
Assigning and ccing. Folks do you know what can be wrong?
I don't know, will investigate. BTW -J-Dorg.netbeans.core.LoaderPoolNode=0 and attach ide.log is helpful for diagnostics.
By the way, after correcting some unrelated bugs, this does not happen with the trunk version; Java Servlets is placed above Java Source Objects.
I don't have time to test thoroughly but here is a patch which I believe fixes it in release32 branch (for core/src/org/netbeans/core/LoaderPoolNode.java): */ private static synchronized void readPool (ObjectInputStream ois) throws IOException, ClassNotFoundException { + // #13880: keep any manifest-provided install before/after information, + // rather than overwriting the map with a (possibly incomplete or obsolete) + // deexternalized mapping. + Map oldInstallBefores = installBefores; + Map oldInstallAfters = installAfters; installBefores = (Map) ois.readObject (); installAfters = (Map) ois.readObject (); + installBefores.putAll(oldInstallBefores); + installAfters.putAll(oldInstallAfters); HashSet classes = new HashSet (); LinkedList l = new LinkedList ();
Fix should be applied in the trunk. Someone who wishes to merge to release32, please try the patch below.
Verified in the trunk (rev1.48). Also verified the patch for Pilsen. Yarda can you do the code review of the fix for integration into Pilsen. Also Ales, will you apply the fix into Pilsen?
Integrated into pilsen_fcs and release32
Correcting the Version filed.
Resolved for 3.4.x or earlier, no new info since then -> closing.