Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » LinkageError when starting project under Eclipse 3.5 M6
LinkageError when starting project under Eclipse 3.5 M6 [message #335066] Fri, 20 March 2009 07:08 Go to next message
Kai Schlamp is currently offline Kai SchlampFriend
Messages: 344
Registered: July 2009
Senior Member
Hello.

I just migrated from Eclipse 3.5M5 to M6 (with up to date CDO, Zest
Plugins).
The problem is that my existing project (RCP project consisting of
several plug ins) runs fine under M5, but doesn't start anymore under M6.
What does this LinkageError mean? How to resolve it? Why does the app
still run in M5?
I already tried to clean and refresh the whole project, without any success.

Best regards,
Kai

!ENTRY org.eclipse.osgi 4 0 2009-03-20 08:05:06.390
!MESSAGE Application error
!STACK 1
java.lang.LinkageError: loader constraint violation: loader (instance of
org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) previously
initiated loading for a different type with name
"org/eclipse/core/databinding/observable/Realm"
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:492)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.pubcurator.core.Application.start(Application.java:20)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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: 556)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
at org.eclipse.equinox.launcher.Main.main(Main.java:1260)

!ENTRY org.eclipse.osgi 2 0 2009-03-20 08:05:06.421
!MESSAGE The following is a complete list of bundles which are not
resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-03-20 08:05:06.421
!MESSAGE Bundle org.pubcurator.val.test_1.0.0 [105] was not resolved.
!SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
!MESSAGE Constraints from the fragment conflict with the host:
Require-Bundle: org.eclipse.swtbot.eclipse.finder; bundle-version="2.0.0"
!SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
!MESSAGE Constraints from the fragment conflict with the host:
Require-Bundle: org.eclipse.swtbot.swt.finder; bundle-version="2.0.0"
!SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
!MESSAGE Constraints from the fragment conflict with the host:
Require-Bundle: org.junit4; bundle-version="0.0.0"
!SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
!MESSAGE Constraints from the fragment conflict with the host:
Require-Bundle: org.apache.log4j; bundle-version="1.2.13"

Report message to a moderator

Re: LinkageError when starting project under Eclipse 3.5 M6 [message #335072 is a reply to message #335066] Fri, 20 March 2009 11:42 Go to previous message
Kai Schlamp is currently offline Kai SchlampFriend
Messages: 344
Registered: July 2009
Senior Member
Problem solved.
My problem was somewhere I didn't exspected or have thought about until
yet (nearly all problems have that in common ;-)). I imported several
eclipse (mostly databinding) plugins from M5 into my workspace.
That old (and incompatible) versions of databinding was then used as
dependency for my plugins and resulted in this exception.

Best regards,
Kai


Kai Schlamp schrieb:
> Hello.
>
> I just migrated from Eclipse 3.5M5 to M6 (with up to date CDO, Zest
> Plugins).
> The problem is that my existing project (RCP project consisting of
> several plug ins) runs fine under M5, but doesn't start anymore under M6.
> What does this LinkageError mean? How to resolve it? Why does the app
> still run in M5?
> I already tried to clean and refresh the whole project, without any
> success.
>
> Best regards,
> Kai
>
> !ENTRY org.eclipse.osgi 4 0 2009-03-20 08:05:06.390
> !MESSAGE Application error
> !STACK 1
> java.lang.LinkageError: loader constraint violation: loader (instance of
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) previously
> initiated loading for a different type with name
> "org/eclipse/core/databinding/observable/Realm"
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:492)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at org.pubcurator.core.Application.start(Application.java:20)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> 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: 556)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
>
> !ENTRY org.eclipse.osgi 2 0 2009-03-20 08:05:06.421
> !MESSAGE The following is a complete list of bundles which are not
> resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2009-03-20 08:05:06.421
> !MESSAGE Bundle org.pubcurator.val.test_1.0.0 [105] was not resolved.
> !SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
> !MESSAGE Constraints from the fragment conflict with the host:
> Require-Bundle: org.eclipse.swtbot.eclipse.finder; bundle-version="2.0.0"
> !SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
> !MESSAGE Constraints from the fragment conflict with the host:
> Require-Bundle: org.eclipse.swtbot.swt.finder; bundle-version="2.0.0"
> !SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
> !MESSAGE Constraints from the fragment conflict with the host:
> Require-Bundle: org.junit4; bundle-version="0.0.0"
> !SUBENTRY 2 org.pubcurator.val.test 2 0 2009-03-20 08:05:06.421
> !MESSAGE Constraints from the fragment conflict with the host:
> Require-Bundle: org.apache.log4j; bundle-version="1.2.13"
>

Report message to a moderator

Previous Topic:Localizing about.html
Next Topic:How to refresh a property tab
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sun Jul 14 07:45:29 GMT 2024

Powered by FUDForum. Page generated in 0.03209 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly