[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-tcf-dev] [Bug 270608] [tcf] Do not initiate TCF event dispatching and extension point loading in Activator#start(...)
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270608
Product/Component: Target Management / TCF
Eugene Tarassov <eugene.tarassov@xxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #5 from Eugene Tarassov <eugene.tarassov@xxxxxxxxxxxxx> 2009-04-03 14:44:25 -0400 ---
Yes, Equinox implementation of start() method has its limitations and problems
were observed in the past.
However, current use of the method in TCF is equivalent to making few
assignments and starting a thread on bundle activation, which is well within
boundaries of fair use of the API. Changing that is compatibility breaking
change that would require each client to do explicit initialization of TCF
plugin. Since it works fine and exactly as intended, I see no reason to change
it.
Changing resolution to "invalid".
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
