| Intro: extensions to extensionContent [message #469020] |
Thu, 15 March 2007 21:25  |
Eclipse User |
|
|
|
What determines the order in which extensionContent contributions are
loaded?
I tried to use extensionContent that contains anchors, with other
extensionContent (contributed by other plug-ins) targeting those anchors,
but I could not get it to work.
Looking at the -debug log, it appears that org.eclipse.ui.intro loads the
extensionContent contributions in indeterminate order, so some lower-level
contributions are loaded before the higher-level contributions, even those
contributed by the primary "intro" plug-in (i.e., the plug-in that declares
org.eclipse.ui.intro and org.eclipse.ui.intro.config extensions).
Is there any option other than: a) avoiding such "nested" extensionContent
contributions, or b) implementing my own late-target-path resolver?
Thanks.
|
|
|
| Re: Intro: extensions to extensionContent [message #469022 is a reply to message #469020] |
Fri, 16 March 2007 11:55  |
| Eclipse User |
|
|
|
Never mind... user error (my mistake).
My target paths in the extensions to extensionContent incorrectly referred
to the first extension's anchor target.
For example:
<!-- primary introContent file -->
<introContent>
<page id="root-page">
<anchor id="root-target"/>
</page>
</introContent>
<!-- primary extension file -->
<introContent>
<extensionContent path="root-page/root-target">
<group id="ext-group">
<anchor id="ext-target"/>
</group>
</extensionContent>
</introContent>
<!-- secondary extension file -->
<introContent>
<!-- next line is incorrect path -->
<extensionContent path="root-page/root-target/ext-group/ext-target">
...
</extensionContent>
</introContent>
The correct secondary extension path should assume the primary extension's
path has been resolved, so:
<extensionContent path="root-page/ext-group/ext-target">
This works as it should.
DR
|
|
|
| Re: Intro: extensions to extensionContent [message #560288 is a reply to message #469020] |
Fri, 16 March 2007 11:55 |
| Eclipse User |
|
|
|
Never mind... user error (my mistake).
My target paths in the extensions to extensionContent incorrectly referred
to the first extension's anchor target.
For example:
<!-- primary introContent file -->
<introContent>
<page id="root-page">
<anchor id="root-target"/>
</page>
</introContent>
<!-- primary extension file -->
<introContent>
<extensionContent path="root-page/root-target">
<group id="ext-group">
<anchor id="ext-target"/>
</group>
</extensionContent>
</introContent>
<!-- secondary extension file -->
<introContent>
<!-- next line is incorrect path -->
<extensionContent path="root-page/root-target/ext-group/ext-target">
...
</extensionContent>
</introContent>
The correct secondary extension path should assume the primary extension's
path has been resolved, so:
<extensionContent path="root-page/ext-group/ext-target">
This works as it should.
DR
|
|
|
Powered by
FUDForum. Page generated in 0.03533 seconds
Home