August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18183) Enhancement to custom jmx provider UI

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-18183: ----------------------------------- Summary: Enhancement to custom jmx provider UI Key: JBIDE-18183 URL: https://issues.jboss.org/browse/JBIDE-18183 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jmx Affects Versions: 4.2.0.CR1 Reporter: Rob Stryker Currently, each JMX provider has a UI mapped to it, and the UI assumes only 1 icon for each provider. Fuse Tools has several server types that behave identically, but require different icons. This could be worked around by declaring 4 or 5 different providers, and accompanying xml indicating different icons, but this is a lot of overhead and would make the code much more complex. A simpler solution is to allow an image provider to be part of the extension point. The image provider could then pull the Image from the server type ui (declared in wtp's api). This would also instantiate fewer images by re-using those already instantiated for wtp.server. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18182: ----------------------------------- Fix Version/s: 4.2.0.CR2 > JBDS crashes when editor is opened > ---------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > Fix For: 4.2.0.CR2 > > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18182: ---------------------------------------- Great news, thanks! > JBDS crashes when editor is opened > ---------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > Fix For: 4.2.0.CR2 > > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Alexander Kurtakov commented on JBIDE-18182: -------------------------------------------- Fix is already scheduled for SR1 - http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?h=R4_4... . > JBDS crashes when editor is opened > ---------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18073) Error when triggering content assist on Ticket Monster JPA entity

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18073?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18073: --------------------------------------- ok > Error when triggering content assist on Ticket Monster JPA entity > ----------------------------------------------------------------- > > Key: JBIDE-18073 > URL: https://issues.jboss.org/browse/JBIDE-18073 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > The following error occurs when triggering content assist on a JPA annotation attribute of _any_ Entity in the project (after following instructions on http://www.jboss.org/ticket-monster/datapersistence/) > {code} > Java Model Exception: Java Model Status [/Users/xcoulon/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar is not on its project's build path] > at org.eclipse.jdt.internal.core.PackageFragmentRoot.getRawClasspathEntry(PackageFragmentRoot.java:562) > at org.eclipse.jdt.internal.core.JavaElement.getJavadocBaseLocation(JavaElement.java:714) > at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1011) > at org.eclipse.jdt.internal.core.BinaryField.getAttachedJavadoc(BinaryField.java:121) > at org.eclipse.jdt.internal.core.ResolvedBinaryField.getAttachedJavadoc(ResolvedBinaryField.java:1) > at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:500) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:689) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:607) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:599) > at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:163) > at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129) > at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:85) > at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18073) Error when triggering content assist on Ticket Monster JPA entity

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18073?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-18073 at 8/29/14 5:32 AM: ---------------------------------------------------------------- ok. Thanks for the support ;-) was (Author: xcoulon): ok > Error when triggering content assist on Ticket Monster JPA entity > ----------------------------------------------------------------- > > Key: JBIDE-18073 > URL: https://issues.jboss.org/browse/JBIDE-18073 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > The following error occurs when triggering content assist on a JPA annotation attribute of _any_ Entity in the project (after following instructions on http://www.jboss.org/ticket-monster/datapersistence/) > {code} > Java Model Exception: Java Model Status [/Users/xcoulon/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar is not on its project's build path] > at org.eclipse.jdt.internal.core.PackageFragmentRoot.getRawClasspathEntry(PackageFragmentRoot.java:562) > at org.eclipse.jdt.internal.core.JavaElement.getJavadocBaseLocation(JavaElement.java:714) > at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1011) > at org.eclipse.jdt.internal.core.BinaryField.getAttachedJavadoc(BinaryField.java:121) > at org.eclipse.jdt.internal.core.ResolvedBinaryField.getAttachedJavadoc(ResolvedBinaryField.java:1) > at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:500) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:689) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:607) > at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:599) > at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:163) > at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129) > at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:85) > at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18072) Error while generating JPA annotations

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18072?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18072: --------------------------------------- [~koen.aers] ok ;-) > Error while generating JPA annotations > -------------------------------------- > > Key: JBIDE-18072 > URL: https://issues.jboss.org/browse/JBIDE-18072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > While following the Ticket Monster example, I got the following error when trying to generate the JPA annotations for the {{Venue}} class (selecting the class in the project explorer, then {{Source>Generate JPA annotations}} : > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findType(Utils.java:73) > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findCompilationUnit(Utils.java:51) > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findCompilationUnit(Utils.java:90) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.updateSelectedItems(JPAMapToolActor.java:273) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.updateSelected(JPAMapToolActor.java:109) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.runInternal(JPAMapToolActionDelegate.java:81) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.run(JPAMapToolActionDelegate.java:56) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:253) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18182: ---------------------------------------- [~akurtakov] Are you aware of a similar issue? JBDS 8.0 is built on top of Luna and seems to fail on RHEL 6 beta. > JBDS crashes when editor is opened > ---------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18182: ---------------------------------------- [~snjeza] Could it be related to some GTK3/SWT issue? > JBDS crashes when editor is opened > ---------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17855) JPA Project uses JDK 1.8 as default JDK level

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17855?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17855. -------------------------------- Resolution: Done [~koen.aers] This was resolved by some updates in time (upstream ? I don't know). Hoever issues is not present anymore. Closing this one. > JPA Project uses JDK 1.8 as default JDK level > --------------------------------------------- > > Key: JBIDE-17855 > URL: https://issues.jboss.org/browse/JBIDE-17855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3 > Reporter: Jiri Peterka > Fix For: 4.2.0.CR1 > > > When creating JPA Project (even JPA 2.0) all is set to JDK 1.8 by default which is not desired. It should be set to JDK 1.6 by default or another minimal level. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2014