Home » Eclipse Projects » Eclipse Platform » Plugin doesn't start since i've updated to 3.2
| Plugin doesn't start since i've updated to 3.2 [message #305412] |
Mon, 03 July 2006 14:03  |
Eclipse User |
|
|
|
Originally posted by: vincent.dumont.humagade.com
Hi all,
I developed a plugin on Eclipse SDK 3.1.2. Today, I updated my SDK to 3.2
and since then, my plugin doesn't start anymore... The only changed that I
made has been to replace the old Eclipse-AutoStart by Eclipse-LazyStart in
the manifest.
I would like to know if other changes have to be done.
thx
Vincent
|
|
|
| Re: Plugin doesn't start since i've updated to 3.2 [message #305416 is a reply to message #305412] |
Mon, 03 July 2006 19:27  |
| Eclipse User |
|
|
|
Hi Vincent,
Not sure if it is relevant, but I use the PDE editor, and in "overview"
tab, there is a tick said: "Activate this plug-in when one of its
classes is loaded". In effect, it sets lazystart to true:
Eclipse-LazyStart: true.
However, if I didn't tick this box, my plugin class is not start, even
though my other extension in the plugin seems to work (to an extend).
You may want to give it a try.
Cheers,
Dennis
Vincent Dumont wrote:
> Hi all,
>
> I developed a plugin on Eclipse SDK 3.1.2. Today, I updated my SDK to 3.2
> and since then, my plugin doesn't start anymore... The only changed that I
> made has been to replace the old Eclipse-AutoStart by Eclipse-LazyStart in
> the manifest.
>
> I would like to know if other changes have to be done.
>
> thx
>
> Vincent
>
>
|
|
|
| Re: Plugin doesn't start since i've updated to 3.2 [message #305434 is a reply to message #305416] |
Tue, 04 July 2006 09:29 |
| Eclipse User |
|
|
|
Originally posted by: vincent.dumont.humagade.com
Hi Dennis,
I'm not able to find that "overview" view... The only thing that I've found
and the views included in the plug-in development perspective. (Views that
can be also found in the "show view" menu under PDE and PDE Runtime folders)
thx
Vincent
"Dennis Nguyen" <dennis.nguyen.06@gmail.com> wrote in message
news:e8c95a$ijj$1@utils.eclipse.org...
> Hi Vincent,
>
> Not sure if it is relevant, but I use the PDE editor, and in "overview"
> tab, there is a tick said: "Activate this plug-in when one of its classes
> is loaded". In effect, it sets lazystart to true:
> Eclipse-LazyStart: true.
>
> However, if I didn't tick this box, my plugin class is not start, even
> though my other extension in the plugin seems to work (to an extend). You
> may want to give it a try.
>
> Cheers,
> Dennis
>
> Vincent Dumont wrote:
>> Hi all,
>>
>> I developed a plugin on Eclipse SDK 3.1.2. Today, I updated my SDK to 3.2
>> and since then, my plugin doesn't start anymore... The only changed that
>> I made has been to replace the old Eclipse-AutoStart by Eclipse-LazyStart
>> in the manifest.
>>
>> I would like to know if other changes have to be done.
>>
>> thx
>>
>> Vincent
|
|
|
| Re: Plugin doesn't start since i've updated to 3.2 [message #305435 is a reply to message #305434] |
Tue, 04 July 2006 10:08 |
| Eclipse User |
|
|
|
Originally posted by: udnguyen.optusnet.com.au
Hi Vincent,
I mean opening the manifest file or plugin.xml for editing. The editor
will have several tabs, the first one is overview, then extension,
extension points, dependency, etc.
Vincent Dumont wrote:
> Hi Dennis,
>
> I'm not able to find that "overview" view... The only thing that I've found
> and the views included in the plug-in development perspective. (Views that
> can be also found in the "show view" menu under PDE and PDE Runtime folders)
>
> thx
>
> Vincent
> "Dennis Nguyen" <dennis.nguyen.06@gmail.com> wrote in message
> news:e8c95a$ijj$1@utils.eclipse.org...
>> Hi Vincent,
>>
>> Not sure if it is relevant, but I use the PDE editor, and in "overview"
>> tab, there is a tick said: "Activate this plug-in when one of its classes
>> is loaded". In effect, it sets lazystart to true:
>> Eclipse-LazyStart: true.
>>
>> However, if I didn't tick this box, my plugin class is not start, even
>> though my other extension in the plugin seems to work (to an extend). You
>> may want to give it a try.
>>
>> Cheers,
>> Dennis
|
|
|
| Re: Plugin doesn't start since i've updated to 3.2 [message #305437 is a reply to message #305435] |
Tue, 04 July 2006 10:29 |
| Eclipse User |
|
|
|
Originally posted by: vincent.dumont.humagade.com
Ok, finally, it's not the problem because the box is already filled by an
X.
"Uy Dung Nguyen" <udnguyen@optusnet.com.au> wrote in message
news:e8dspq$l1c$1@utils.eclipse.org...
> Hi Vincent,
>
> I mean opening the manifest file or plugin.xml for editing. The editor
> will have several tabs, the first one is overview, then extension,
> extension points, dependency, etc.
>
> Vincent Dumont wrote:
>> Hi Dennis,
>>
>> I'm not able to find that "overview" view... The only thing that I've
>> found and the views included in the plug-in development perspective.
>> (Views that can be also found in the "show view" menu under PDE and PDE
>> Runtime folders)
>>
>> thx
>>
>> Vincent
>> "Dennis Nguyen" <dennis.nguyen.06@gmail.com> wrote in message
>> news:e8c95a$ijj$1@utils.eclipse.org...
>>> Hi Vincent,
>>>
>>> Not sure if it is relevant, but I use the PDE editor, and in "overview"
>>> tab, there is a tick said: "Activate this plug-in when one of its
>>> classes is loaded". In effect, it sets lazystart to true:
>>> Eclipse-LazyStart: true.
>>>
>>> However, if I didn't tick this box, my plugin class is not start, even
>>> though my other extension in the plugin seems to work (to an extend).
>>> You may want to give it a try.
>>>
>>> Cheers,
>>> Dennis
|
|
| |
| Re: Plugin doesn't start since i've updated to 3.2 [message #305535 is a reply to message #305525] |
Wed, 05 July 2006 14:10 |
| Eclipse User |
|
|
|
Originally posted by: vincent.dumont.humagade.com
I'm not able to see my plygins views, perspective, ... The only thing that
i'm sure is that the plugin is loaded because, it appears in the "plug-in
details" list from the about menu.
In 3.1.2, I can see all my views, perspectives and other things that come
from my plugin. The only thing that I changed is the AutoStart tag for
LazyStart in plugin.xml.
Here is my log:
!SESSION 2006-07-05
14:08:32.343 -----------------------------------------------
eclipse.buildId=M20060629-1905
java.version=1.5.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA
Framework
arguments: -vmargs -Xmx512M -XX:CompileThreshold=5 -XX:+UseParallelGC -clean
Command-line arguments: -os win32 -ws win32 -arch
x86 -vmargs -Xmx512M -XX:CompileThreshold=5 -XX:+UseParallelGC -clean
!ENTRY org.eclipse.osgi 4 0 2006-07-05 14:09:07.984
!MESSAGE While loading class
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine ",
thread "main" timed out waiting (5000ms) for thread "Worker-2" to finish
starting bundle "org.tigris.subversion.subclipse.ui". To avoid deadlock,
thread "main" is proceeding but
" org.tigris.subversion.subclipse.ui.console.ConsoleDocument$C onsoleLine " may
not be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .preFindLocalClass(EclipseLazyStarter.java:75)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:409)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:188)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:339)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:391)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:352)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319 )
at
org.tigris.subversion.subclipse.ui.console.ConsoleDocument.g etLines(ConsoleDocument.java:79)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. dump(SVNOutputConsole.java:202)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole. access$1(SVNOutputConsole.java:199)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$ 1.run(SVNOutputConsole.java:124)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
"Paul Webster" <pwebster@ca.ibm.com> wrote in message
news:e8gse4$m15$1@utils.eclipse.org...
> Vincent Dumont wrote:
>> Hi all,
>>
>> I developed a plugin on Eclipse SDK 3.1.2. Today, I updated my SDK to 3.2
>> and since then, my plugin doesn't start anymore... The only changed that
>> I made has been to replace the old Eclipse-AutoStart by Eclipse-LazyStart
>> in the manifest.
>
> What do you mean won't start? What kind of errors are in the error log?
> <workspace>/.metadata/.log
>
> Later,
> PW
|
|
|
Goto Forum:
Current Time: Sat Jun 14 20:48:44 EDT 2025
Powered by FUDForum. Page generated in 0.23770 seconds |
Home