[JBoss JIRA] (JBIDE-10557) SWTException before code completion in HQL Editor with Hibernate 4
by Jiri Peterka (Created) (JIRA)
SWTException before code completion in HQL Editor with Hibernate 4
------------------------------------------------------------------
Key: JBIDE-10557
URL: https://issues.jboss.org/browse/JBIDE-10557
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M5
Environment: JBDS 5.0.M5a, H62, L64,HSQLDB 1.8
Reporter: Jiri Peterka
Assignee: Dmitry Geraskov
Fix For: 3.3.0.Beta1
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature
at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.getImage(EclipseHQLCompletionRequestor.java:120)
at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.accept(EclipseHQLCompletionRequestor.java:59)
at org.hibernate.tool.ide.completion.ConfigurationCompletion.addPropertiesToList(ConfigurationCompletion.java:187)
at org.hibernate.tool.ide.completion.ConfigurationCompletion.getMatchingProperties(ConfigurationCompletion.java:80)
at org.hibernate.tool.ide.completion.HQLCodeAssist.codeComplete(HQLCodeAssist.java:66)
at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.hqlCodeComplete(ConsoleExtension4_0.java:93)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeProposals(HQLCompletionProcessor.java:122)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:82)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:65)
at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482)
at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:377)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-11004) Missing requirements - installing JBT Abridged into Eckipse 3.7.1
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-11004:
------------------------------------
Summary: Missing requirements - installing JBT Abridged into Eckipse 3.7.1
Key: JBIDE-11004
URL: https://issues.jboss.org/browse/JBIDE-11004
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Eclipse Migration
Affects Versions: 3.3.0.Beta1
Environment: JBT download (Feb 22)
http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/all/jbos...
Eclipse 3.7.1
java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode
RHEL 6
Reporter: Len DiMaggio
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.3.0.Beta1
3.7.1 - downloaded from:
http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/...
JBT download (Feb 22)
http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/all/jbos...
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss OpenShift Express Tools 2.3.0.v20120217-2351-H280-Beta1 (org.jboss.tools.openshift.express.feature.feature.group 2.3.0.v20120217-2351-H280-Beta1)
Missing requirement: EGit Core 2.3.0.v20120217-2351-H280-Beta1 (org.jboss.tools.openshift.egit.core 2.3.0.v20120217-2351-H280-Beta1) requires 'bundle org.eclipse.egit [1.2.0,2.0.0)' but it could not be found
Cannot satisfy dependency:
From: EGit integration UI 2.3.0.v20120217-2351-H280-Beta1 (org.jboss.tools.openshift.egit.ui 2.3.0.v20120217-2351-H280-Beta1)
To: bundle org.jboss.tools.openshift.egit.core [2.3.0,3.0.0)
Cannot satisfy dependency:
From: JBoss OpenShift Express Tools 2.3.0.v20120217-2351-H280-Beta1 (org.jboss.tools.openshift.express.feature.feature.group 2.3.0.v20120217-2351-H280-Beta1)
To: org.jboss.tools.openshift.express.ui [2.3.0.v20120217-2351-H280-Beta1]
Cannot satisfy dependency:
From: OpenShift UI 2.3.0.v20120217-2351-H280-Beta1 (org.jboss.tools.openshift.express.ui 2.3.0.v20120217-2351-H280-Beta1)
To: bundle org.jboss.tools.openshift.egit.ui 2.3.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months