July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22848) Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22848?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22848: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22848 > URL: https://issues.jboss.org/browse/JBIDE-22848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > There is a prompt to create a new project, if there is no project under an OpenShift 3 connection and New OpenShift Application wizard is opened. If I close popped up shell Create OpenShift Project, also New App wizard is closed and following NPE is shown. This is happening only when opening the wizard through context menu in OpenShift Explorer. Wizards opened via central/shell menu leave New App wizard opened upon cancellation/closing of Create OpenShift Project shell. > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:64) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.setConnection(NewApplicationWizard.java:292) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.init(NewApplicationWizard.java:98) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:281) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > ... 37 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-211) JSON Hover should use JSON Schema description [EBZ#494046]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-211?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-211. ------------------------------ Resolution: Done > JSON Hover should use JSON Schema description [EBZ#494046] > ---------------------------------------------------------- > > Key: ERT-211 > URL: https://issues.jboss.org/browse/ERT-211 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.1 (4.6) > > > Takes a sample with package.json: > ---------------------- > { > "name": "..." > } > ---------------------- > When "name" is hovered, it should show "The name of the package." which comes from the JSON Schema http://json.schemastore.org/package (properties/name/description) > This feature will be possible once https://bugs.eclipse.org/bugs/show_bug.cgi?id=490639 will be fixed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-22847: ------------------------------------ Summary: jbosstools-jiralint-bzira job fails to create new jiras Key: JBIDE-22847 URL: https://issues.jboss.org/browse/JBIDE-22847 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Gorkem Ercan it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22846) Incorrectly referenced artifact are not validated/reported in Source tab in batch editor.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22846?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22846: ---------------------------------- Summary: Incorrectly referenced artifact are not validated/reported in Source tab in batch editor. (was: Incorrectly referenced artifact are not validated/reported in Source tab of batch editor.) > Incorrectly referenced artifact are not validated/reported in Source tab in batch editor. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22846 > URL: https://issues.jboss.org/browse/JBIDE-22846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160725-1821-B5680 > Build date: 20160725-1821 > Reporter: Ondrej Dockal > Priority: Critical > Attachments: BatchNoValidationSourceTab.png > > > There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22846) Incorrect referenced artifact are not validated/reported in Source tab of batch editor.

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-22846: ------------------------------------- Summary: Incorrect referenced artifact are not validated/reported in Source tab of batch editor. Key: JBIDE-22846 URL: https://issues.jboss.org/browse/JBIDE-22846 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.4.1.AM2 Environment: Fedora 24, x86_64, devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160725-1821-B5680 Build date: 20160725-1821 Reporter: Ondrej Dockal Priority: Critical Attachments: BatchNoValidationSourceTab.png There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22846) Incorrectly referenced artifact are not validated/reported in Source tab of batch editor.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22846?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22846: ---------------------------------- Summary: Incorrectly referenced artifact are not validated/reported in Source tab of batch editor. (was: Incorrect referenced artifact are not validated/reported in Source tab of batch editor.) > Incorrectly referenced artifact are not validated/reported in Source tab of batch editor. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22846 > URL: https://issues.jboss.org/browse/JBIDE-22846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160725-1821-B5680 > Build date: 20160725-1821 > Reporter: Ondrej Dockal > Priority: Critical > Attachments: BatchNoValidationSourceTab.png > > > There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-362) Node.js "Relaunch" support - not acting as expected [EBZ#498440]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-362: --------------------------------------- Summary: Node.js "Relaunch" support - not acting as expected [EBZ#498440] Key: ERT-362 URL: https://issues.jboss.org/browse/ERT-362 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot When selecting a current running node process in the debug view. There are a few options including "Relaunch", and also "Terminate and Relaunch" Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22752) Remove SWT_GTK3=0 variable from tests pom

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22752?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22752: ------------------------------------- PR was updated and merged to master. Important notes: - GTK 3 is used for vpv + jst angularjs tests / vpe tests are built against gtk 2 - both centralci and main vpe jenkins are built against RHEL 7 now. Previously main vpe jenkins use RHEL 6 slaves > Remove SWT_GTK3=0 variable from tests pom > ----------------------------------------- > > Key: JBIDE-22752 > URL: https://issues.jboss.org/browse/JBIDE-22752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.1.AM2 > > > Tests do not work on RHEL7 machines because only v3 libwebkit is available but vpe tests pom.xml disables SWT_GTK3 by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-361) Update JavaScript Indexer [EBZ#498372]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-361: --------------------------------------- Summary: Update JavaScript Indexer [EBZ#498372] Key: ERT-361 URL: https://issues.jboss.org/browse/ERT-361 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Priority: Trivial The code that manages file indexing is old and contains a lot of Java specific methods and classes. It should be updated to better fit with what is necessary for JavaScript to ease further development. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22825) Forge New and Noteworthy for 4.4.1.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22825?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22825: ------------------------------------ [~gastaldi] [~akazakov] I'll handle it > Forge New and Noteworthy for 4.4.1.AM2 > -------------------------------------- > > Key: JBIDE-22825 > URL: https://issues.jboss.org/browse/JBIDE-22825 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.1.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016