Eclipse Community Forums: Eclipse Platform » my 3.3 plugin doesn't work in 3.4

Home » Eclipse Projects » Eclipse Platform » my 3.3 plugin doesn't work in 3.4

my 3.3 plugin doesn't work in 3.4 [message #335054]

Thu, 19 March 2009 12:58

Eclipse User

A plugin I wrote under Eclipse 3.3 does not work in 3.4 - it looks like the
plugin is not activated. I did update MANIFEST.MF to include the following:

Bundle-ActivationPolicy: lazy

But it doesn't work whether the old or new line is present. My plugin
overrides editor hover behavior. I specify the extension point
org.eclipse.jdt.ui.javaEditorTextHovers in plugin.xml. That looks like
this:

<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.4"?>
<plugin>

<extension point="org.eclipse.jdt.ui.javaEditorTextHovers">
<hover
id="myEditorHover"
class="sonif.myEditorHover"
label="lewisCustomHover"
description="A custom hover handler."
activate="true" >
</hover>
</extension>

</plugin>

Any ideas why my plugin is not activated?

--
Lewis Berman
Loyola University in Maryland

Re: my 3.3 plugin doesn't work in 3.4 [message #335068 is a reply to message #335054]

Fri, 20 March 2009 04:29

Eclipse User

Lewis Berman wrote:
> A plugin I wrote under Eclipse 3.3 does not work in 3.4 - it looks like the
> plugin is not activated. I did update MANIFEST.MF to include the following:
>
> Bundle-ActivationPolicy: lazy
>
> But it doesn't work whether the old or new line is present. My plugin
> overrides editor hover behavior. I specify the extension point
> org.eclipse.jdt.ui.javaEditorTextHovers in plugin.xml. That looks like
> this:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?eclipse version="3.4"?>
> <plugin>
>
> <extension point="org.eclipse.jdt.ui.javaEditorTextHovers">
> <hover
> id="myEditorHover"
> class="sonif.myEditorHover"
> label="lewisCustomHover"
> description="A custom hover handler."
> activate="true" >
> </hover>
> </extension>
>
> </plugin>
>
> Any ideas why my plugin is not activated?
>
No idea. Try with 3.5 M6 and if it is not working there file a bug
report and attach your plug-in.

Dani

Re: my 3.3 plugin doesn't work in 3.4 [message #335079 is a reply to message #335068]

Fri, 20 March 2009 09:58

Eclipse User

It is possible that my plugin is not activated because certain code has been
deprecated. I could at least test to see if it's activation works on
demand. Does Eclipse accept any activation policy other than lazy? If so,
what do I substitute for "lazy" in:

Bundle-ActivationPolicy: lazy

?

--
Lewis Berman
Loyola University in Maryland

Re: my 3.3 plugin doesn't work in 3.4 [message #335161 is a reply to message #335079]

Tue, 24 March 2009 10:06

Eclipse User

Hi Lewis,
You can easily check if your plug-in is activated by setting a printout
in the "start()" method in your plug-in "Activator.java" class. If your
message appears in the console, your plug-in is started. Your problem
could be related to deprecated code, or perhaps a deprecated extension
point...
If the activation is not lazy, the "Bundle-ActivationPolicy: lazy" line
in your Manifest.MF is deleted.
Mircea

Lewis Berman wrote:
> It is possible that my plugin is not activated because certain code has been
> deprecated. I could at least test to see if it's activation works on
> demand. Does Eclipse accept any activation policy other than lazy? If so,
> what do I substitute for "lazy" in:
>
> Bundle-ActivationPolicy: lazy
>
> ?
>
>

Previous Topic:	IWorkBenchPropertyPages and disabling/enabling based on content
Next Topic:	How to check the consistency of the Platform ?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Apr 30 19:49:41 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter