January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21613) NPE if click on failed CDK server

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21613: -------------------------------------- Summary: NPE if click on failed CDK server Key: JBIDE-21613 URL: https://issues.jboss.org/browse/JBIDE-21613 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Alexey Kazakov I ran my CDK server but it failed by timeout (it tool longer than the timeout to start the server). When the server finally started (I saw it in the console) I clicked on the server in the server view to "restart" it. You don't need to start/stop the server. Just click on/select the server in the view: {code} java.lang.NullPointerException at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53) at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111) at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188) at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203) at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2178) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1717) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1069) at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:368) at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383) at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) at org.eclipse.equinox.launcher.Main.run(Main.java:1516) at org.eclipse.equinox.launcher.Main.main(Main.java:1489) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21598) OpenShift resource tab properties are shrinked in case of small view

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21598?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21598: ----------------------------------------------- It is implementation of TabbedPropertyList in TabbedPropertySheetPage that cannot be customized, it only can be replaced with entirely custom sheet page implementation. > OpenShift resource tab properties are shrinked in case of small view > -------------------------------------------------------------------- > > Key: JBIDE-21598 > URL: https://issues.jboss.org/browse/JBIDE-21598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: shrinked_tabbed_props.png > > > In properties view when browsing OpenShift resources (e.g. project in OpenShift explorer is selected and properties view is opened) and properties view is too small (height - y axis), the tabbed properties are shrinked and it is necessary to click button on top/bottom of them to get to other tabbed properties representing OpenShift resources. See following screenshot > !shrinked_tabbed_props.png!" > This is usability issues because it is pain to click all the time instead of scrolling (suggested solution would be to have a scroll bar) and it causes problem for automatized tests when working with widgets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-15) [ES6] Support for ECMAScript 6 validation [EBZ#477031]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-15?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-15: ---------------------------- Story Points: 50 > [ES6] Support for ECMAScript 6 validation [EBZ#477031] > ------------------------------------------------------ > > Key: ERT-15 > URL: https://issues.jboss.org/browse/ERT-15 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > JSDT Validator doesn't support ES6 syntax and display a lot of error with ES6 syntax. > To fix this problem, there are 2 solutions : > * improve the JSDT Validator to support ES6 syntax (I think it's a lot of work). > * gives the capability to disable the JSDT Validator (with extension point and with preferences). With those solution, we could delegate the validator to another component like Tern JSHint (https://github.com/angelozerr/tern.java/wiki/Tern-Linter-JSHint) where JSHint is able to validate ES6 syntax. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-14) [ES6] Support for ECMAScript 6 syntax coloration [EBZ#477030]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-14?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-14: ---------------------------- Story Points: 25 > [ES6] Support for ECMAScript 6 syntax coloration [EBZ#477030] > ------------------------------------------------------------- > > Key: ERT-14 > URL: https://issues.jboss.org/browse/ERT-14 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > It should be cool if JSDT could support ECMAScript 6 syntax coloration like highlight "let", "const" etc keywords, template string, etc > To do that there are 2 solutions : > * delegate this syntax coloration to another component, like I have done with acorn parser. See https://github.com/angelozerr/tern.java/issues/310 and https://github.com/angelozerr/tern.java/tree/master/sandbox > * improve the existing org.eclipse.wst.jsdt.internal.ui.text.java.JavaCodeScanner to support ES6 syntax coloration (I think it will be a better solution). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-32) Create icons for bower/npm utilities' wizards and actions [EBZ#484218]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-32?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-32: ---------------------------- Story Points: 2 > Create icons for bower/npm utilities' wizards and actions [EBZ#484218] > ---------------------------------------------------------------------- > > Key: ERT-32 > URL: https://issues.jboss.org/browse/ERT-32 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: General, bzira > > We need to create icons for wizards and actions for bower and npm dependency management tools to be shown for: > - Init Wizard > - Install Action > - Update Action > The icons are to be based on the according ones for bower and npm utilities logos: > For Bower: > - Site: http://bower.io > - License: > https://github.com/bower/bower/blob/master/README.md#license > https://github.com/bower/bower/blob/master/LICENSE > - Logo Info: http://bower.io/docs/about/#logo > - Logo Image: http://bower.io/img/bower-logo.png > For NPM: > - Site: https://www.npmjs.com > - License: > https://docs.npmjs.com/policies/license > https://www.npmjs.com/policies/npm-license > https://github.com/npm/npm/blob/master/LICENSE > - Trademark And Logo policies: > https://docs.npmjs.com/policies/trademark#the-npm-trademark-policy > https://docs.npmjs.com/policies/trademark#the-npm-logo > - Logo Images: > https://github.com/npm/npm/blob/master/html/npm.png > https://github.com/npm/npm/blob/master/html/n-large.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-21) Update or replace JSDT parser to support ES6 [EBZ#481706]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-21?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-21: ---------------------------- Story Points: 75 > Update or replace JSDT parser to support ES6 [EBZ#481706] > --------------------------------------------------------- > > Key: ERT-21 > URL: https://issues.jboss.org/browse/ERT-21 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Support ecma-262 standard Javascript language features with the JSDT parser so that other functionality can provide relevant support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-36) Disable TypeBinding and deprecate internal ast model [EBZ#484598]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-36?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-36: ---------------------------- Story Points: 2 > Disable TypeBinding and deprecate internal ast model [EBZ#484598] > ----------------------------------------------------------------- > > Key: ERT-36 > URL: https://issues.jboss.org/browse/ERT-36 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M5, General, bzira > Fix For: Neon (4.6) M5 > > > Disable type binding to allow the replacement for a new Parser. > maintaining 2 ast models is wasteful deprecate org.eclipse.wst.jsdt.internal.compiler.ast model in favor of dom ast model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21590: ----------------------------------------------- [~jcantrill], yes the changes are essential and should be taken into account. However, for this issue, it is about project deleted by user action, OpenShiftJobs.createDeleteProjectJob() runs a job that requests delete of project on server and then fires event projects changed, with new list without the project. Explorer content provider listens to the event and has to remove project from children of connection node. It should work, but according to this issue does not. As much as I can see, changes to JBIDE-21457 do not affect that part. If you can reproduce this issue, could you try implement equals() and hashCode() for OpenShiftProjectUIModel and check if it helps. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21590: --------------------------------------- Project will always need to be manually refreshed if they are deleted servers-side; we can only properly handle cases where we delete the from the client side. Unlike the other resource where the watch is per project, there is not a callback mechanism for project changes unless you watch on the default namespace. This requires you to be a cluster admin which we can not guarantee. In regards to the other points brought up, there may well be some memory leaks with regards to things we cache; they should probably be investigated in more detail. Caching of project may no longer be necessary with some of the existing changes because the adapter classes now keep reference to their parent. This should allow us to properly refresh trees without having to figure out the parent. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-21363: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 January 2016