Re: [cdt-dev] MBS valueHandler issue

[Chris Recoskie <recoskie@xxxxxxxxxx>]

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