Community
Participate
Working Groups
3.3 M5 - exported a plugin via the plugin export wizard - realized it was missing the plugin.xml file and icons folder (they apparently don't automatically get added to the build.properties file when the PDE tooling generates the plugin) - fixed up the build.properties file and tried to re-export - this time it failed with 4 ClassNotFoundExceptions for org.eclipse.pde.internal.core.ant.ExportBuildListener These appeared in an error dialog. Nothing in the log.
Created attachment 60208 [details] Screen shot of the error dialog
This may be due to having run another workspace with -clean from the same install.
I restarted and the problem went away.
the exception was thrown in the host workspace. So the PDE plug-in was affected by, but is not responsible for the exception. Looks like an ant classloader problem.
This sounds suspiously like a problem we have seen every once in a while but have not been able to reproduce consistantly. The JARs exploded into the ..LatestBuild\eclipse\configuration\org.eclipse.osgi\bundles\ space have appeared to go MIA...even when still physically present. Have you had any reports similar to this Jeff?
They likely went missing because I started another workspace from the same install with -clean. Maybe the extra plugin resulted in jars going into different folders under ...\bundles than they were before. If I look under there now, though, the only jar I see is launchingsupport.jar, containing classes in package org/eclipse/jdt/internal/launching/support/ So it doesn't seem to explain the case above.
Is it possible that ant is keeping a list of file paths to the extracted jars in one instance and reusing the file paths each time it creates a classloader? Maybe something like this happens: 1) Workspace "X" is started and ant performs some operation. While performing this operation ant finds the paths to several extracted library jars and creates a classloader. This operation completes successfully. Workspace "X" remains open. 2) Another workspace "Y" is started with -clean. This clears all the extracted ant libraries used in workspace "X". 3) Workspace "X" tries to perform another ant operation. Does ant at this point try to find the libraries again? or does it use the old paths from step 1? If it uses the old paths from step one then I can see how this would happen because they got removed from the -clean operation.
Just got that today using I20080527-2000. Export worked and when I did it again later in the same session it failed.
This problem is also present using 3.4 build M20080911-1700.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
