[news.eclipse.platform] Re: [Activities] failure when in separate plug-i

[Paul Keyser <rolarenfan@xxxxxxxxxxxxx>]

Tried that already; made no difference.

0) I do have in the MANIFEST.MF of the new supplying plug-in this line:
Eclipse-LazyStart: true

So, I set a breakpoint in the start() method of the activator of the new supplying plug-in, and then 
debugged the product with "-console -noExit" as program args:

1) using the command "ss", I find that the new supplying plug-in is RESOLVED but not ACTIVE, even 
after I open the ActivityCategoryPreferencePage (Window -> Prefs -> ...)

2) In that pref-page, once I check the activity, which (per prior messsages) enables the code in the 
*main* plug-in, *then* (and only then) is the breakpoint hit, when some of my code iterates through 
all suppliers of my third-party extension-point. (After that, of course, the new supplying plug-in 
is ACTIVE -- but its action-set still does *not* appear!)

3) checked to see if *Eclipse*, when iterating all suppliers of action-sets, hits mine, when the 
ActivityCategoryPreferencePage runs: set a second breakpoint in MutableActivityManager, second line 
of updateIdentifier(Identifier), i.e., line 636, with condition 
<code>id.startsWith("com.mun.ist")</code> -- my new supplying plug-in's action-set's id comes through.

4) Tried adding a fresh new action-set, using the "Hello World" action-set wizard: that appears, 
even when I morph it to appear in the file-menu (as my action-set is intended to), and once I click 
that button/menu-item, the new supplying plug-in is ACTIVE, by my action-set stubbornly does not 
appear.

5) Stare at: (1) the original action-set in my main plug-in, (2) the copied (with changed id's) 
action-set in the new supplying plug-in, and (3) the hello-world action-set in the new supplying 
plug-in -- notice that the hello-world action-set has no value for "visible", whereas *both* of mine 
have that tag with the value "false" ... remove the tag "visible" from the copied action-set in the 
new supplying plug-in -- hurrah, it works!

Conclusion:
the tag "visible", allowed (maybe even required) when an action-set is defined in the same plug-in 
as the activity that is dis-/en-abling it, is forbidden if the action-set is defined (as the 
activities docco suggests) in a different plug-in from the one defining activities.

Geh.

thanks,
Paul