Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] URGENT! - Plug-in F12Plugin was unable to load class GlobalActivities
I'll fill a bug report tonight, it might be very important. Everyone has a boss and, for them, everything seems so easy... 
Regards,
Simone
Leen Toelen ha scritto:


Hi,

this is not the first time I see this kind of problems in the mailing
list. Could anyone submit a bug on the eclipse bugzilla. Someone
should create ate least a page on the wiki, or change the export
wizard to make this more user-friendly.

Regards,
Leen


On 11/14/05, Count Zero <countzero81@xxxxxxxxxxxx> wrote:

FINALLY!
I found out what was wrong and, let me say it, the way the export wizard
works makes me sick (though eclipse is the best dev platform ever).
Maybe you might find this obvious but it wasn't so for me: in the
manifest, the Bundle-Classpath MUST include the binaries jar!
Thanks everyone!


Leen Toelen ha scritto:


Hi,

in my main plugin class (the Activator) I always make some functions like these:

     /**
      * @param errorLevel
      *            IStatus.[OK|INFO|WARNING|ERROR]
      */
     public static void log(int errorLevel, String message, Throwable e) {
             Status s = makeStatus(errorLevel, message, e);
             getDefault().getLog().log(s);
             if (e != null) {
                     e.printStackTrace();
             } else {
                     System.out.println(message);
             }
     }

     public static void log(Throwable e) {
             log(IStatus.ERROR, e.getMessage() != null ? e.getMessage()
                             : "No message gotten.", e);
     }

     public static void log(String message) {
             log(IStatus.WARNING, message, null);
     }

The put some log("I am here") in some parts of your code. When your
main class is loaded you know that is NOT what your are looking for
:-)

Regards


On 11/14/05, Count Zero <countzero81@xxxxxxxxxxxx> wrote:



Hi! Thanks again for the great help!
I modified the build.properties like this:
source.f12plugin.jar = src/
bin.includes = plugin.xml,\
             META-INF/,\
             icons/,\
             .,\
             bin/,\
             dom4j-1.6.1.jar,\
             jaxen-1.1-beta-6.jar,\
             jaxme-api-0.3.jar

Yes, there's a f12plugin.jar inside f12plugin_1.0.0.jar and it contains
the package f12plugin (with inner packages and classes).


Here's the log:

!ENTRY org.eclipse.update.configurator 2005-11-14 14:28:42.488
!MESSAGE Unable to find feature.xml in directory:
/home/theirish/eclipse/features/f12Plugin_1.0.0
then no more. When I click on an action:

!ENTRY org.eclipse.core.runtime 4 1 2005-11-14 14:30:51.833
!MESSAGE Plug-in f12Plugin was unable to load class
f12Plugin.actions.GlobalActivities.
!STACK 0
java.lang.ClassNotFoundException: f12Plugin.actions.GlobalActivities
      at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:403)
      at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:350)
      at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:78)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
      at
org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:275)
      at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
      at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1259)
      at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:152)
      at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:142)
      at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:129)
      at
org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:48)
      at
org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:240)
      at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:236)
      at
org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:118)
      at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:217)
      at
org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:223)
      at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
      at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
      at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1021)
      at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2867)
      at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2572)
      at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
      at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
      at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
      at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
      at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
      at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
      at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
      at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
      at org.eclipse.core.launcher.Main.run(Main.java:973)
      at org.eclipse.core.launcher.Main.main(Main.java:948)
Plug-in f12Plugin was unable to load class
f12Plugin.actions.GlobalActivities.

Thanks again for the great help. I think we're moving close to the
solution and I would never been able to reach this point without you ;)

Leen Toelen ha scritto:




Hi,

in my plugins I don't use output.f12plugin.jar = bin/. Only source. In
the resulting plugin jar, do you see f12plugin.jar in the root folder?
It might be good to send us part of the the logfile as well, there is
more information to be found over there.

Regards,
Leen

On 11/14/05, Count Zero <countzero81@xxxxxxxxxxxx> wrote:





Thanks a lot for the prompt reply.
There's not runtime section in plugin.xml . I modified the build
properties and, in fact, the output was just fine.
I modified the build.properties like this:
source.f12plugin.jar = src/
output.f12plugin.jar = bin/
bin.includes = plugin.xml,\
            META-INF/,\
            icons/,\
            .,\
            dom4j-1.6.1.jar,\
            jaxen-1.1-beta-6.jar,\
            jaxme-api-0.3.jar
And the tree that came out is:

/
icons/
META_INF/
dom4j-1.6.1.jar
f12.plugin.jar => META_INF/ , f12plugin/
f12pluginsrc.zip
jaxen-1.1.-beta-6.jar
jaxme-api-0.3.jar
plugin.xml

Still, when I copy this directory in eclipse/plugins/ and lauch eclipse,
all menus are there, but I keep getting:
Could not create action delegate for id: f12Plugin.actions.GlobalActivities
Reason:
Plug-in f12Plugin was unable to load class
f12Plugin.actions.GlobalActivities.
when I click on an item.
Thank you very much for you patience


Leen Toelen ha scritto:






In the plugin.xml, do you see a something in the Runtime information
table. You should add the myjar.jar over there, and in
build.properties add source.myjar.jar = src/
This way you tell eclipse to build all your code to a jar file.

Regards,
Leen Toelen

On 11/14/05, Count Zero <countzero81@xxxxxxxxxxxx> wrote:







Unluckly, they do...

Bruno Wassermann ha scritto:








You might want to check whether the jar file name in plugin.xml and
build.properties really match.

-----Original Message-----
From: pde-dev-bounces@xxxxxxxxxxx [mailto:pde-dev-bounces@xxxxxxxxxxx] On
Behalf Of Count Zero
Sent: 14 November 2005 09:40
To: pde-dev@xxxxxxxxxxx
Subject: [pde-dev] URGENT! - Plug-in F12Plugin was unable to load class
GlobalActivities

Good day everyone,
I'm sorry for my firt post to be Urgent... but it actually is.
I've been developing di plugin for over a month and never tried
deploying it. No I have to...
I had my problems in including external jar libraries, but finally I
succeeded.
Now, when I deploy my plugin in a jar file, say, F12Plugin_1.0.0.jar, I
can see my menus but when I click on them, I get the message:
Plug-in F12Plugin was unable to load class <class name>

I had a look at the stacktrance and it says:
java.lang.ClassNotFoundException: f12Plugin.actions.GlobalActivities

The jar tree is like:
bin
\f12Plugin
 \actions
META_INF
build.properties
plugin.xml

My manifest is like:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: F12 Plug-in
Bundle-SymbolicName: F12Plugin; singleton:=true
Bundle-Version: 1.0.0
Bundle-Activator: f12Plugin.F12PluginPlugin
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.jface.text,
org.eclipse.core.resources,
[...]
Export-Package: f12Plugin,
f12Plugin.Internals,
f12Plugin.actions,
f12Plugin.components,
f12Plugin.dialogs,
f12Plugin.editors,
f12Plugin.perspectives,
f12Plugin.staticsAndGlobals,
f12Plugin.views,
f12Plugin.webComm


My build properties is:
source.. = src/
output.. = bin/
bin.includes = plugin.xml,\
         META-INF/,\
         icons/,\
         bin/,\
         .,\
         build.properties,\
         dom4j-1.6.1.jar

Any suggestion very appreciated...
Thanks!
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev

_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev










_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev








_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev








_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev






_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev






_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev




_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev




_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev


_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev

Back to the top