Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » Activating a plug-in

Wed, 25 June 2008 08:23

Eclipse User

Originally posted by: selcuksumer.hotmail.com

i was working on a plug-in project, i finished coding and Exported it.

now i have the .Jar file, and it works fine in my computer (eclipse 3.3.2).

but when i copy the .jar to another (eclipse 3.3.0) computer's
Eclipse/plugins directory, open Eclipse and try opening the plugin,
eclipse says that it is not available.

is it because of the build.project.xml file ?
should i add this file inside .jar ?

or is it because i should export again and again for every different
computer?

or is it because of the difference in versions?

Thanks..

Re: Activating a plug-in [message #329479 is a reply to message #329465]

Wed, 25 June 2008 13:05

Eclipse User

My initial guess would be that a required bundle (or version) is missing
on the other computer.

Was anything written to the log? [workspace]/.metadata/.log

Wayne

On Wed, 2008-06-25 at 12:23 +0000, selcuk sumer wrote:
> i was working on a plug-in project, i finished coding and Exported it.
>
> now i have the .Jar file, and it works fine in my computer (eclipse 3.3.2).
>
> but when i copy the .jar to another (eclipse 3.3.0) computer's
> Eclipse/plugins directory, open Eclipse and try opening the plugin,
> eclipse says that it is not available.
>
>
>
> is it because of the build.project.xml file ?
> should i add this file inside .jar ?
>
> or is it because i should export again and again for every different
> computer?
>
> or is it because of the difference in versions?
>
> Thanks..
>

Re: Activating a plug-in [message #329489 is a reply to message #329479]

Thu, 26 June 2008 01:56

Eclipse User

Originally posted by: selcuksumer.hotmail.com

At first, i couldn't get the error log, it was working fine and i wasn't
able to get it from other computers.

now i read the file ;

i quess the problem is the JRE version mismatch.

if you think there are more problems, please let me know.

java.lang.UnsupportedClassVersionError: Bad version number in .class file

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.def ineClass(DefaultClassLoader.java:161)

at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineC lass(ClasspathManager.java:501)

at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findCla ssImpl(ClasspathManager.java:471)

at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClassImpl(ClasspathManager.java:430)

at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:413)

at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:189)

at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:340)

at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:408)

at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:369)

at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:357)

at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)

at java.lang.ClassLoader.loadClass(Unknown Source)

at
org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:289)

at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:227)

at
org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1269)

at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:160)

at
org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:788)

at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)

at
org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)

at
org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugi n.java:252)

at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)

at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:248)

at
org.eclipse.ui.internal.PluginAction.createDelegate(PluginAc tion.java:122)

at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:228)

at
org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPl uginAction.java:229)

at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:546)

at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:490)

at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:402)

at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)

at
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)

at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3682)

at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3293)

at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2389)

at
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)

at
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)

at
org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)

at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)

at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)

at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)

at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:106)

at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:169)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:106)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:76)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)

at
org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)

at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

Re: Activating a plug-in [message #329499 is a reply to message #329489]

Thu, 26 June 2008 04:36

Eclipse User

Originally posted by: selcuksumer.yahoo.com

i changed my Development Kit 6 to 5.

so it works fine now.

but of course, i don't know will it work with some other versions.

Re: Activating a plug-in [message #329507 is a reply to message #329499]

Thu, 26 June 2008 09:16

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

That error is due to Java JDK differences. Java is upward compatible, so
something compiled at Java 5 will run in Java 6, but something compiled
in Java 6 will not run in Java 5.

So Java 5 will not run in Java 1.4, but unless you need to support Java
1.4 (which is very down level these days), then Java 5 is sufficient.
Unless you need something from 6, then you'll need to pre-req 6 instead.

selcuk sumer wrote:
> i changed my Development Kit 6 to 5.
> so it works fine now.
> but of course, i don't know will it work with some other versions.
>
>
>

--
Thanks,
Rich Kulp

Previous Topic:	Can't update TableViewer when Button is pressed
Next Topic:	Requesting JFace ComboViewer data binding help

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Apr 25 00:22:38 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter