September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18281) NullPointerException when trying to run Cordova application on iOS simulator

by Tadeas Kriz (JIRA)

Tadeas Kriz created JBIDE-18281: ----------------------------------- Summary: NullPointerException when trying to run Cordova application on iOS simulator Key: JBIDE-18281 URL: https://issues.jboss.org/browse/JBIDE-18281 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Environment: Mac OSX 10.9.4 Xcode 5.1.1 JBDS 8.0.0.Beta3 cordova app: WFK's kitchensink-cordova-contacts Reporter: Tadeas Kriz I've tried one more project and that one worked, but I don't know what should I focus on when looking for differences between those two projects. Message: {code} An internal error occurred during: "Launching kitchensink-cordova-contacts (iOS Simulator)". {code} Stack trace: {code} java.lang.NullPointerException at org.jboss.tools.aerogear.hybrid.ios.core.xcode.XcodeProjectGenerator.generateNativeFiles(XcodeProjectGenerator.java:69) at org.jboss.tools.aerogear.hybrid.core.platform.AbstractProjectGeneratorDelegate.generateNow(AbstractProjectGeneratorDelegate.java:119) at org.jboss.tools.aerogear.hybrid.ios.core.xcode.XCodeBuild.buildNow(XCodeBuild.java:122) at org.jboss.tools.aerogear.hybrid.ios.core.simulator.IOSSimulatorLaunchDelegate.buildForLaunch(IOSSimulatorLaunchDelegate.java:88) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Session data: {code} eclipse.buildId=unknown java.version=1.7.0_40 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/tkriz/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/tkriz/.eclipse_keyring -showlocation {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18183?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18183. --------------------------------- Thing to verify by QE, closing. > 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 > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > 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-18264) Weird JMX entries in server view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18264?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18264. --------------------------------- Verified in JBDS 8.0.0.CR1 B225 > Weird JMX entries in server view > -------------------------------- > > Key: JBIDE-18264 > URL: https://issues.jboss.org/browse/JBIDE-18264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: weird-entries-2.png, weird-entries.png > > > When I start EAP 6, two new entries appear in the Server view: > [Disconnected] > [Disconnected] > !weird-entries.png! > That looks pretty weird. > I can right-click them and connect and they actually correspond to the two server entries in JMX Navigator - one in Local Processes, the other in Server Connections. But there is nothing else I can do with these in the server views. What's the point of having it there? I find it confusing, especially since there is no explanations whatsoever about what these are. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17626) provide extension points for customizing node name and icon in JMX explorer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17626?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17626. --------------------------------- Nothing to verify by QE, closing. > provide extension points for customizing node name and icon in JMX explorer > --------------------------------------------------------------------------- > > Key: JBIDE-17626 > URL: https://issues.jboss.org/browse/JBIDE-17626 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Currently the whole naming and icon assignment is done in jmx.local plugin inside JBT. If other projects want to provide own icons or names for nodes it is currently not possible. We should also provide some priority mechanism if more than one plugin wants to customize a node in the tree. > Tasks: > # provide an extension point for customizing the label of the process node > # provide an extension point for customizing the icon of the process node > # provide an extension point for customizing the tooltip of the process node > # have some priority logic to decide what plugin is actually customizing it if there is more than one provider > # hand over the output of jps to determine the name, icon and tooltip -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18225) Jenkins build unstable, failing unit tests - zipped incremental deployment

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18225?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18225. --------------------------------- Tests now passing. > Jenkins build unstable, failing unit tests - zipped incremental deployment > -------------------------------------------------------------------------- > > Key: JBIDE-18225 > URL: https://issues.jboss.org/browse/JBIDE-18225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR1 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.2... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17924) java add annotation is available on projects but fail when running it

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17924?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-17924: ------------------------------- Labels: respin-b (was: respin-a) > java add annotation is available on projects but fail when running it > --------------------------------------------------------------------- > > Key: JBIDE-17924 > URL: https://issues.jboss.org/browse/JBIDE-17924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: George Gastaldi > Labels: respin-b > Fix For: 4.2.0.CR1 > > > EXECUTE: Have an eclipse project in focus in explorer. > EXECUTE: Cmd+4 > > Java: Add Annotation shows up. > Select it. > result: error in log with this: > org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed. > at org.jboss.forge.addon.facets.AbstractFaceted.getFacet(AbstractFaceted.java:51) > at org.jboss.forge.addon.parser.java.beans.ProjectOperations.getProjectClasses(ProjectOperations.java:24) > at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.setupTargetClass(JavaAddAnnotationCommandImpl.java:296) > at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.initializeUI(JavaAddAnnotationCommandImpl.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81) > at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.initializeUI(JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.java) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.initialize(SingleCommandControllerImpl.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.initialize(CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.java) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103) > at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:187) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:347) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) > 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.sendKeyEvent(Widget.java:1504) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1632) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1598) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5719) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) > at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908) > at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085) > at org.eclipse.swt.widgets.Control.keyDown(Control.java:2400) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5629) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > Caused by: org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed. > ... 76 more > I would have expected either: > a) not having add annotation on projects > b) when running forge would report a more informative error on why it is failing > c) run add annotation but let me select which file it is for... > anything except this silent logged error ;) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18279) Cordovasim run option not available for project created with Thym

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18279?page=com.atlassian.jira.plugi... ] Ilya Buziuk resolved JBIDE-18279. --------------------------------- Resolution: Rejected Not a bug > Cordovasim run option not available for project created with Thym > ------------------------------------------------------------------ > > Key: JBIDE-18279 > URL: https://issues.jboss.org/browse/JBIDE-18279 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Environment: Hybrid Mobile Application Development Tools 0.1.0.201408271516 org.eclipse.thym.feature.feature.group Eclipse.org - Thym > JBoss Tools Apache Cordova Simulator 3.5.100.Beta3-v20140717-1903-B49 org.jboss.tools.vpe.cordovasim.feature.feature.group JBoss by Red Hat > Reporter: Sebastien Blanc > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > > Hi, > I have installed Eclipse Thym using http://download.eclipse.org/thym/snapshots and CordovaSim using http://download.jboss.org/jbosstools/updates/development/luna/ > After I create a hybrid project I should be able to run it on CordovaSim but the option is not available. If I add manually CordovaSim using "run as . Run configurations ..." I got an exception. More log can be found here https://gist.github.com/sebastienblanc/03def2f21e2d119099ff -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18279) Cordovasim run option not available for project created with Thym

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18279?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18279: ------------------------------------- [~sebastienblanc], that was easy ;-) > Cordovasim run option not available for project created with Thym > ------------------------------------------------------------------ > > Key: JBIDE-18279 > URL: https://issues.jboss.org/browse/JBIDE-18279 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Environment: Hybrid Mobile Application Development Tools 0.1.0.201408271516 org.eclipse.thym.feature.feature.group Eclipse.org - Thym > JBoss Tools Apache Cordova Simulator 3.5.100.Beta3-v20140717-1903-B49 org.jboss.tools.vpe.cordovasim.feature.feature.group JBoss by Red Hat > Reporter: Sebastien Blanc > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > > Hi, > I have installed Eclipse Thym using http://download.eclipse.org/thym/snapshots and CordovaSim using http://download.jboss.org/jbosstools/updates/development/luna/ > After I create a hybrid project I should be able to run it on CordovaSim but the option is not available. If I add manually CordovaSim using "run as . Run configurations ..." I got an exception. More log can be found here https://gist.github.com/sebastienblanc/03def2f21e2d119099ff -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17021) No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17021?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17021: ------------------------------------- 1 - Open JBDS aka Eclipse #1 2 - Run a new Eclipse Application from there, aka Eclipse #2 3 - In Eclipse #1, kill Eclipse #2 (red button in console view) 4 - repeat step #1 : when Eclipse #2 opens, borked editor is shown (or used to be) > No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab > ------------------------------------------------------------------ > > Key: JBIDE-17021 > URL: https://issues.jboss.org/browse/JBIDE-17021 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > > I keep from time to time to get two central editors to open up. > 1) with "No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab" > 2) a few seconds later the real Central. > My guess is that the editorinput for central is not behaving properly so it does not know how to restore itself causing it to be empty on start and then we force opening a new one even though already one there. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18173) Remove "Add Forge Runtime" feature for Forge 1.x

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18173?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18173: ------------------------------------ Hi [~mmurray], please be aware of this change - it affects our documentation. > Remove "Add Forge Runtime" feature for Forge 1.x > ------------------------------------------------ > > Key: JBIDE-18173 > URL: https://issues.jboss.org/browse/JBIDE-18173 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: George Gastaldi > Assignee: Max Rydahl Andersen > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: forge-preferences.png > > > Since Forge 1.x is no longer maintained, there is no need to still have this feature. -- 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