Re: [cdt-dev] MBS valueHandler issue

[Derek Morris <dmsubs@xxxxxxxxxxxxx>]

Chris,

Thanks for the reply. Here is the stacktrace.

The ManagedOptionValueHandler is part of a Plugin whose Activator is an 
AbstractUIPlugin. The Eclipse UI has disappeared (no longer visible, anyway) 
when this error occurs.

---

EclipseLazyStarter.shouldActivateFor(String, BaseData, EclipseStorageHook) 
line: 119	
EclipseLazyStarter.preFindLocalClass(String, ClasspathManager) line: 39	
ClasspathManager.findLocalClass(String) line: 409	
DefaultClassLoader.findLocalClass(String) line: 188	
BundleLoader.findLocalClass(String) line: 334	
BundleLoader.findClass(String, boolean) line: 386	
BundleLoader.findClass(String) line: 347	
DefaultClassLoader.loadClass(String, boolean) line: 83	
DefaultClassLoader(ClassLoader).loadClass(String) line: not available	
BundleLoader.loadClass(String) line: 278	
BundleHost.loadClass(String, boolean) line: 227	
BundleHost(AbstractBundle).loadClass(String) line: 1245	
EquinoxRegistryStrategy(RegistryStrategyOSGI).createExecutableExtension(RegistryContributor, 
String, String) line: 147	
ExtensionRegistry.createExecutableExtension(RegistryContributor, String, String) 
line: 759	
ConfigurationElement.createExecutableExtension(String) line: 243	
ConfigurationElementHandle.createExecutableExtension(String) line: 51	
Option.getValueHandler() line: 1596	
ManagedBuildManager.performValueHandlerEvent(IConfiguration, int, boolean) 
line: 2826	
ResourceChangeHandler.sendClose(IManagedBuildInfo) line: 304	
ResourceChangeHandler.sendClose(IProject) line: 294	
ManagedBuilderCorePlugin.stop(BundleContext) line: 162	
BundleContextImpl$3.run() line: 1032	
AccessController.doPrivileged(PrivilegedExceptionAction<T>) line: not available 
[native method]	
BundleContextImpl.stop() line: 1028	
BundleHost.stopWorker(boolean) line: 396	
BundleHost(AbstractBundle).stop() line: 400	
BundleStopper.basicStopBundles() line: 86	
BundleStopper.stopBundles() line: 73	
EclipseAdaptorHook.frameworkStopping(BundleContext) line: 156	
BaseAdaptor.frameworkStopping(BundleContext) line: 288	
Framework.shutdown() line: 529	
Framework.close() line: 440	
OSGi.close() line: 41	
EclipseStarter.shutdown() line: 423	
EclipseStarter.run(String[], Runnable) line: 193	
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available 
[native method]	
NativeMethodAccessorImpl.invoke(Object, Object[]) line: not available	
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not available	
Method.invoke(Object, Object...) line: not available	
Main.invokeFramework(String[], URL[]) line: 336	
Main.basicRun(String[]) line: 280	
Main.run(String[]) line: 977	
Main.main(String[]) line: 952	

--
Derek


Chris Recoskie wrote:
> I think you're doing the right thing in either case, but there seems to be
> something funny with your plugin's startup/shutdown code because you
> shouldn't have plugins being instantiated after they are shut down.  Can
> you provide a full stack trace?  It might be a bug in MBS or you might have
> other plugins doing weird things trying to access or modify the build info
> when they shut down or somesuch.
>
> ===========================
>
> Chris Recoskie
> Team Lead, IBM CDT Team
> IBM Toronto
> http://www.eclipse.org/cdt
>
>
>
>                                                                            
>   From:   Derek Morris <dmsubs@xxxxxxxxxxxxx>                              
>                                                                            
>   To:     "CDT General developers list." <cdt-dev@xxxxxxxxxxx>             
>                                                                            
>   Date:   25/01/2007 07:48 AM                                              
>                                                                            
>   Subject [cdt-dev] MBS valueHandler issue                                 
>   :                                                                        
>                                                                            
>
>
>
>
> HI,
>
> I've written ManagedOptionValueHandler and an MBSCustomPage and all (was)
> working OK.
>
> In the Runnable() of my MBSCustomPage, I was setting a tool option by using
>
> option = tool.getOptionByID(). However, I changed it to use
> tool.getOptionToSet(). Both methods successfully sets the options.
>
> However, now, when I close Eclipse, I get the following error:
>
> Managed Build system manifest file error: Could not load value handler
> com.crt.advproject.custom.OptionHandler in option
> com.crt.advproject.link.script.771933248.
>
> Tracing it through to the class loader, the error is actually caused by the
>
> following error:
>
> The class "com.crt.advproject.custom.OptionHandler" cannot be loaded
> because the
> system is shutting down and the plug-in "com.crt.advproject" has already
> been
> stopped.
>
> So, my question is:
> Which mehtod should I be using to get the option to set:
> getOptionByID(id) or getOptionToSet(getOptionByID(id))?
>
> If the latter, how do I stop the manifest file error from occuring?
>
> Thanks,
>
> --
> Derek
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev