September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18180) Hibernate Tools UI elements not loading images

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18180?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-18180. -------------------------------- Verified with JBDS 8.0.0.CR1, Linux_64 > Hibernate Tools UI elements not loading images > ---------------------------------------------- > > Key: JBIDE-18180 > URL: https://issues.jboss.org/browse/JBIDE-18180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599 (from nightly repo) > Reporter: Luke Maurer > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: screenshot-1.png > > > Immediately upon switching to the Hibernate perspective, I get error dialogs and log messages saying “Unable to create resource URLImageDescriptor” with an URL. All elements in the Hibernate Configurations tab, including the toolbar buttons (reload, HQL editor, etc.) and the nodes in the configuration tree, appear as little red squares or as blank. Functionality seems unaffected (besides having to click through those dialogs …). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18031) Widget disposed error when toggling EA features on/off

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18031?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18031. ------------------------------ Couldn't reproduce in JBT 4.2.0.CR1. Closing. > Widget disposed error when toggling EA features on/off > ------------------------------------------------------ > > Key: JBIDE-18031 > URL: https://issues.jboss.org/browse/JBIDE-18031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > 1. Install JBT 4.2.0.Beta3 or CR1 (nightly) into Eclipse Luna eclipse-jee-luna-R-linux.gtk.x86_64.tar.gz > 2. Launch JBT, and Central will open by itself (default) > 3. Select Software/Update tab > 4. Close Central > (So far, so good.) > 5. Reopen it from the coolbar icon. > 7. Select "Show Early Access" checkbox (enable or disable, whichever shows that same issue) > Pop-up: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". > {code} > Stack: > {code} > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.widgets.Widget.error(Widget.java:476) > at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:562) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$1.propertyChange(JBossCentralEditor.java:533) > at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:382) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:378) > at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:197) > at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899) > at org.eclipse.core.internal.preferences.EclipsePreferences.putBoolean(EclipsePreferences.java:926) > at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:553) > at org.jboss.tools.central.editors.SoftwarePage.access$11(SoftwarePage.java:506) > at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:236) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} > Environment: > {code} > eclipse.buildId=4.4.0.I20140606-1215 > java.version=1.8.0 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation -Dorg.jboss.tools.vpe.loadxulrunner=false > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -Dorg.jboss.tools.vpe.loadxulrunner=false > {code} > Restarting Eclipse/JBDS "resets" the error so first Central page works fine, but the bug is still there for next times you'll open Central. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11766) Work with "Annotation Properties" view breaks JAX-RS explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11766?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-11766. ----------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.x) Resolution: Cannot Reproduce Bug Bug cannot be reproduced anymore. It was probably solved while working on other issues on the plugin. > Work with "Annotation Properties" view breaks JAX-RS explorer > ------------------------------------------------------------- > > Key: JBIDE-11766 > URL: https://issues.jboss.org/browse/JBIDE-11766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta3 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > After some random clicking on JAX-RS annotation in Annotation Properties view, JAX-RS breaks. -- 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 Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18072?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-18072. -------------------------------- Unable to replicate with JBDS 8.0.0.CR1 > 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-18228) Publish *-earlyaccess.properties in CI build

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18228?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-18228. ---------------------------------- Resolution: Done Ok. Next iteration is tracked in JBIDE-18235. > Publish *-earlyaccess.properties in CI build > -------------------------------------------- > > Key: JBIDE-18228 > URL: https://issues.jboss.org/browse/JBIDE-18228 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.0.CR1 > > > *-earlyaccess.properties files are generated/updated whenever we run a build of the discovery bundles (cf JBIDE-18105). The CI job that builds discovery should publish the newer files as part of the build. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18235) Improve publication of *-earlyaccess.properties files

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-18235: -------------------------------------- Summary: Improve publication of *-earlyaccess.properties files Key: JBIDE-18235 URL: https://issues.jboss.org/browse/JBIDE-18235 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build, discovery Affects Versions: 4.2.0.CR1 Reporter: Mickael Istria Assignee: Nick Boldt Priority: Minor Fix For: 4.2.0.CR2 Currently, there are explicit steps in discovery job configurations (cf JBIDE-18228) to publish the *-earlyaccess.properties file to nightly directories. Instead, we should consider making publication more standard and rely on promote.sh. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11321) Tidy up Forge's list-commands output

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11321?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-11321. ------------------------------ Verified in JBT 4.2.0.CR1 build. > Tidy up Forge's list-commands output > ------------------------------------ > > Key: JBIDE-11321 > URL: https://issues.jboss.org/browse/JBIDE-11321 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Burr Sutter > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: Screen Shot 2012-03-14 at 8.55.57 AM.png > > > The use of "list-commands" produces a less than ideal formatting - see screenshot from JBDS5 Beta1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15290) Database Connection Usability Improvements

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15290?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15290. ------------------------------ Verified in JBT 4.2.0.CR1 build. > Database Connection Usability Improvements > ------------------------------------------ > > Key: JBIDE-15290 > URL: https://issues.jboss.org/browse/JBIDE-15290 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge, upstream > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > > The current end-user workflow is fairly challenging and has amble opportunities for end-user error. You can see it starting around minute 4 in this video: > https://vimeo.com/39608294 > This workflow is also used with the Forge: Entities from Tables Wizard. > Here are the current steps, starting from the Forge Wizard: > http://www.screencast.com/t/mSyhEtlwfp > http://www.screencast.com/t/pNk17S4Xk9 > http://www.screencast.com/t/MssISpUZW6 > http://www.screencast.com/t/XxkzckHdi > http://www.screencast.com/t/j5pBIE0ESBM0 > http://www.screencast.com/t/GzLvpgNv8m > http://www.screencast.com/t/6KsGhlPx > http://www.screencast.com/t/yHHPnHva > http://www.screencast.com/t/v26qYQ3Cjr > http://www.screencast.com/t/NHvDtza1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18228) Publish *-earlyaccess.properties in CI build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18228?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18228: ------------------------------------ OK, that's acceptable ... until we have earlyaccess.properties for JBTIS/JBDSIS. Then we should really standardize this into the shell script. If you want to close this JIRA, please do -- you can open a clone set for 4.2.x and assign it to me. Or just leave it open for 4.2.0.CR2 and I'll have a look when I'm back in 3 weeks. > Publish *-earlyaccess.properties in CI build > -------------------------------------------- > > Key: JBIDE-18228 > URL: https://issues.jboss.org/browse/JBIDE-18228 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.0.CR1 > > > *-earlyaccess.properties files are generated/updated whenever we run a build of the discovery bundles (cf JBIDE-18105). The CI job that builds discovery should publish the newer files as part of the build. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16593) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16593?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16593: --------------------------------------------- [~apodhrad] please tell us which servers this is a problem for and what settings should be used ? run.conf is os specific thus cannot be relied on for our usage unfortunately. Does SOA-P 6 still require massive amount of memory ? > JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16593 > URL: https://issues.jboss.org/browse/JBIDE-16593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 4.2.x > > > JBDS6: > "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime" > -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true > -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed" > SOA 5.3.1 run.conf: > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning > =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true" > fi -- 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 September 2014