Community
Participate
Working Groups
Hi, On Eclipse 3.0 with AJDT 1.1.11, I have been unable to install XMLBuddy 2.0.10. Eclipse would simply ignore it. After having disabled AJDT with Eclipse Configuration Manager (casually ...), XMLBuddy magically appeared ! I don't know if its a bug of Eclipse, XMLBuddy or AJDT, but I thought it was right to signal it here. Bob Foster (XMLBuddy) suggested: > I believe what you did signalled Eclipse > to check for configuration changes. > On some platforms (what's yours?) > Eclipse doesn't notice plugins dropped > into the plugins folder. You would have > gotten the same effect (XMLBuddy > appeared) by deleting the configuration folder. versions Eclipse 3.0 final Eclipse AspectJ Development Tools 1.1.11 XMLBuddy 2.0.10 running on win2K + JDK 1.4.2_05
See the README. You're likely running on FAT32 in which case you need to restart with -clean to detect changes.
That is correct, I am running on FAT32. I understand I should have read the README. The problem might be given more visibility (in the user interface for example, in the configuration manager).
Dorian, I think this problem is much bigger than just XMLBuddy and FAT32. I've run into problems updating several product extensions running on Windows XP and an NTFS file system. Any time I update, the next Eclipse restart will throw several exceptions about the contributed actions, editors, or views not being available. In addition, the 'About Eclipse...' dialog will show the features, but the providers are blank and the features are obviously misconfigured. However, once eclipse is manually restarted with -clean, all is well. Could -clean be made the default option for a restart after reconfiguring the platform after an update? It would surely solve a lot of problems and make the update mechanism perform accurately in all cases. I'd also suggest changing the short description of this bug to be more descriptive of the full scope of this issue.
Todd, this looks like the Platform Runtime bug 70176. Basically, plugins with a manifest.mf that got there during zip/jar is interpreted by the runtime as a bundle manifest, so the plugin.xml is not looked at. Please confirm if this is the case. Thanks!
Dorian, Thanks for the followup and quick reply. Bug #70176 sounds like the problem because all the jars were created with the jar command and as a result *do* have a MANIFEST.MF file by default. However, they are not OSGI bundles at all. Naturally, this is a rather widespread problem since most update jars won't be OSGI bundles at the present time. :-) I'm glad to see that this is indeed resolved by the 3.0.1 target as it makes all updates look *broken* from the end user perspective.
Dorian, One more bit of information. I rebuild a local update site with jars specifically created with the -M jar option so that no manifest files would be created. However, after update the problems seemed even worse as only two of the five features were event detected. As before, restarting with -clean corrected the installation. So, I'm going to go back to requesting strongly that this be the default behavior for workbench restarts after updates.
Todd, I think the orgininal bug description and problem is different than what you're seeing. Could you please describe the steps to reproduce what you describe in comment #6 ?
Here are the steps to reproduce the problem. 1) Install a clean version of Eclipse 3.0 2) Download the MyEclipse 3.8.0 manual installation available here: http://www.myeclipseide.com/products/eworkbench/eclipse-bug70783-test/myeclipse_030800.zip 3) Unzip the archive somewhere outside your Eclipse installation. 4) Install it as a product extension through Help > Manage Configuration... 5) Restart 6) Open Help > About Eclipse and notice the five MyEclipse features are installed. 7) Open the MyEclipse Perspective and the Error Log view 8) Exit the workbench 9) Update to version 3.8.1 by adding a new update site that points to: http://www.myeclipseide.com/products/eworkbench/updates-3.8.0to3.8.1 10) Allow the workbench to restart 11) Upon restart you'll get several errors about missing action sets and the need to reset the perspective. 12) The log will have several errors in it about missing functionality and most of the features are now unavailable even though 3.8.1 was only a bug-fix update. 13) Clear the log file in the Error Log view and exit Eclipse 14) Restart with the -clean option and notice that now MyEclipse 3.8.1 starts without error and all functionality is now available. Naturally, the lare number of errors in the log and multiple perspective reset dialogs do not enhance the end user experience. The broken functionality after the update only exacerbates the issue. Again, all fixed with a -clean start. Hope that helps. Please let me know if you need any more information.
Todd, I'd suggest you open a bug against Platform UI and describe your problem. The update to 3.8.1 worked fine, all the dialogs are put up by the workbench. There may be some problem in the way the update is packaged, as I could see some osgi error. For reference, here is the log file that I get: !SESSION Aug 25, 2004 20:18:15.463 -------------------------------------------- - eclipse.buildId=I200406240800 java.version=1.4.2_03 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US !ENTRY System Bundle 0 0 Aug 25, 2004 20:18:15.463 !MESSAGE FrameworkEvent.ERROR !STACK 0 org.osgi.framework.BundleException: PackageAdmin.refreshPackages failed to complete at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta (PackageAdminImpl.java:518) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.refreshPackages (PackageAdminImpl.java:352) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run (PackageAdminImpl.java:321) at java.lang.Thread.run(Unknown Source) Caused by: org.osgi.framework.BundleException: Internal Error in the OSGi framework. Please report this problem. at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.deleteRemovalPending (PackageAdminImpl.java:157) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta (PackageAdminImpl.java:454) ... 3 more Root exception: org.osgi.framework.BundleException: Internal Error in the OSGi framework. Please report this problem. at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.deleteRemovalPending (PackageAdminImpl.java:157) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta (PackageAdminImpl.java:454) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.refreshPackages (PackageAdminImpl.java:352) at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run (PackageAdminImpl.java:321) at java.lang.Thread.run(Unknown Source) !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.617 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.deploytools !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.627 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.627 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.hibernatetools !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.637 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.webtools !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.637 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.jsftools !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:18.637 !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.strutstools !ENTRY org.eclipse.ui 4 4 Aug 25, 2004 20:18:43.32 !MESSAGE Category com.genuitec.eclipse.views.myEclipseCategory not found for view com.genuitec.eclipse.ui.HTMLView. This view added to 'Other' category.
Dorian, I took your advice and opened Bug #72653. Thanks for looking into it. Maybe you can share any insights gathered on the other bug thread. Regards, Todd
the orginal bug is a dup of bug 66120, and Todd's problem has been addressed by runtime bug 72653 *** This bug has been marked as a duplicate of 66120 ***
