March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13717) Unhalted event loop exception after canceling domain creation

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13717?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-13717: ----------------------------------- Summary: Unhalted event loop exception after canceling domain creation (was: Unhalted event loop ) > Unhalted event loop exception after canceling domain creation > ------------------------------------------------------------- > > Key: JBIDE-13717 > URL: https://issues.jboss.org/browse/JBIDE-13717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > {code} > java.lang.NullPointerException > at org.eclipse.jface.window.Window.initializeBounds(Window.java:758) > at org.eclipse.jface.dialogs.Dialog.initializeBounds(Dialog.java:729) > at org.eclipse.jface.window.Window.create(Window.java:435) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) > at org.eclipse.jface.window.Window.open(Window.java:790) > at org.jboss.tools.openshift.express.internal.ui.action.CreateApplicationAction.run(CreateApplicationAction.java:42) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3705) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3326) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > 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:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13716) Error when deleting domain with 1+ applications

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13716: -------------------------------------- Summary: Error when deleting domain with 1+ applications Key: JBIDE-13716 URL: https://issues.jboss.org/browse/JBIDE-13716 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Alpha1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 {code} Failed to delete domain "sbunciak" Could not request https://openshift.redhat.com/broker/rest/domains/sbunciak: Operation failed with exit code "1".Reason given: " Problem: Cannot delete Domain because of dependent 'applications'. Summary: When defining 'applications' with a :dependent => :restrict, Mongoid will raise an error when attempting to delete the Domain when the child 'applications' still has documents in it. Resolution: Don't attempt to delete the parent Domain when it has children, or change the dependent option on the relation." {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-24) Update savara to 2.1.1.Final

by Gary Brown (JIRA)

Gary Brown created JBTIS-24: ------------------------------- Summary: Update savara to 2.1.1.Final Key: JBTIS-24 URL: https://issues.jboss.org/browse/JBTIS-24 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Fix For: 4.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12381) Provide a mean to display requests and responses from the java-client layer

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12381?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-12381. ---------------------------------- OK, Closing then. > Provide a mean to display requests and responses from the java-client layer > --------------------------------------------------------------------------- > > Key: JBIDE-12381 > URL: https://issues.jboss.org/browse/JBIDE-12381 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha1 > > Attachments: trace.png, tracing-preferences.png > > > We should provide a way to let the java-client log requests and responses (with a trigger to enable/disable), so that users problem can be more easily debugged. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2

by Martin Malina (JIRA)

Martin Malina created JBIDE-13715: ------------------------------------- Summary: soa-p 5.3 is incorrectly detected as 5.2 Key: JBIDE-13715 URL: https://issues.jboss.org/browse/JBIDE-13715 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 4.0.1.Final, 4.1.0.Alpha2 When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13535) Wrong bom version is required

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13535?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-13535: ------------------------------------- Fix Version/s: 4.0.1.Final (was: 4.0.0.Final) > Wrong bom version is required > ----------------------------- > > Key: JBIDE-13535 > URL: https://issues.jboss.org/browse/JBIDE-13535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > Java EE Web Project has bom version always set to 1.0.4.Final-redhat-1 (which is version from EAP6.1) even if runtime is set to 6.0 or 6.0.1 > for HTML5 and Richfaces project it is the same, just the version is always set to 1.0.2.Final-redhat-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13297) Prevent from associating xml files to Android xml editor

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13297?page=com.atlassian.jira.plugi... ] Stefan Bunciak commented on JBIDE-13297: ---------------------------------------- Found a relevant issue at http://code.google.com/p/android/issues/detail?id=28147 > Prevent from associating xml files to Android xml editor > -------------------------------------------------------- > > Key: JBIDE-13297 > URL: https://issues.jboss.org/browse/JBIDE-13297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Reporter: Stefan Bunciak > Assignee: Max Rydahl Andersen > > After installing the Android Development Tools into JBDS/JBT all xml files gets associated to Android Common Xml Editor, even pom.xml files which we used to open with the Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13714) Typo runtimea instead of rutime

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-13714: ---------------------------------------- Summary: Typo runtimea instead of rutime Key: JBIDE-13714 URL: https://issues.jboss.org/browse/JBIDE-13714 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.1.Final Reporter: Rastislav Wagner Assignee: Rob Stryker Priority: Minor Fix For: 4.0.1.Final There's a typo when adding EAP6.1. It says JBoss Enterprise Application Platform 6.1 Runtimea. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-13537. ------------------------------------ verified in JBDS 6.0.1 v20130304-0526-B338 > Unable to create EAP6.1 server [4.0.1 maintenance] > --------------------------------------------------- > > Key: JBIDE-13537 > URL: https://issues.jboss.org/browse/JBIDE-13537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png > > > EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13713) Set up build for Hybrid

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13713: -------------------------------------- Summary: Set up build for Hybrid Key: JBIDE-13713 URL: https://issues.jboss.org/browse/JBIDE-13713 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid, Build/Releng Reporter: Mickael Istria Assignee: Gorkem Ercan Fix For: 4.1.0.Alpha2 Add poms and repository to make hybrid stuff built with "mvn verify" and ready to be embedded into JBoss Tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

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 March 2013