|
| Re: Target Platform plugin dependent on workspace plugin [message #5810 is a reply to message #5793] |
Thu, 05 June 2008 18:20   |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Christopher Hopkins wrote:
> Is it possible for a Target Platform plugin to be dependent on a workspace
> plugin? I know the other way around works but I suspect that we can't
> achieve this.
Generally speaking, the mechanism to achieve this kind of thing is
extension points. Any plugin can implement an extension for an extension
point declared by a target platform plugin, thus introducing a runtime
relationship between the target platform and the extending plugin.
Does that help you? Do you control the target platform enough to add an
extension point to one of its plugins?
Eric
|
|
|
| Re: Target Platform plugin dependent on workspace plugin [message #5826 is a reply to message #5810] |
Thu, 05 June 2008 18:49 |
| Eclipse User |
|
|
|
Originally posted by: chopkins.cra.com
I was actually chasing a red herring so this didn't end up being an issue.
The original problem that I thought was happening is that a Target Platform
plugin specified a dependency on a package that was contributed by a
workspace plugin. It turns out the workspace plugin should have been a
Target Platform plugin. However, is that typically something that can
happen...a package dependency in a Target Platform where the package is
provided by a workspace plugin. I don't think that extension points help in
this situation as I understand them (admittedly, I may not understand them)
Is that more clear?
"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:g29an2$6d2$1@build.eclipse.org...
> Christopher Hopkins wrote:
>> Is it possible for a Target Platform plugin to be dependent on a
>> workspace plugin? I know the other way around works but I suspect that we
>> can't achieve this.
>
> Generally speaking, the mechanism to achieve this kind of thing is
> extension points. Any plugin can implement an extension for an extension
> point declared by a target platform plugin, thus introducing a runtime
> relationship between the target platform and the extending plugin.
>
> Does that help you? Do you control the target platform enough to add an
> extension point to one of its plugins?
>
> Eric
|
|
|
|
| Re: Target Platform plugin dependent on workspace plugin [message #568252 is a reply to message #5810] |
Thu, 05 June 2008 18:49 |
| Eclipse User |
|
|
|
Originally posted by: chopkins.cra.com
I was actually chasing a red herring so this didn't end up being an issue.
The original problem that I thought was happening is that a Target Platform
plugin specified a dependency on a package that was contributed by a
workspace plugin. It turns out the workspace plugin should have been a
Target Platform plugin. However, is that typically something that can
happen...a package dependency in a Target Platform where the package is
provided by a workspace plugin. I don't think that extension points help in
this situation as I understand them (admittedly, I may not understand them)
Is that more clear?
"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:g29an2$6d2$1@build.eclipse.org...
> Christopher Hopkins wrote:
>> Is it possible for a Target Platform plugin to be dependent on a
>> workspace plugin? I know the other way around works but I suspect that we
>> can't achieve this.
>
> Generally speaking, the mechanism to achieve this kind of thing is
> extension points. Any plugin can implement an extension for an extension
> point declared by a target platform plugin, thus introducing a runtime
> relationship between the target platform and the extending plugin.
>
> Does that help you? Do you control the target platform enough to add an
> extension point to one of its plugins?
>
> Eric
|
|
|
Powered by
FUDForum. Page generated in 0.03871 seconds
] 
Search
Help
Register
Login
Home
