February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-23) Support for Unit testing similar to JDT Junit [EBZ#482054]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-23?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-23: ---------------------------- Story Points: 75 > Support for Unit testing similar to JDT Junit [EBZ#482054] > ---------------------------------------------------------- > > Key: ERT-23 > URL: https://issues.jboss.org/browse/ERT-23 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: General, bzira > > Ability to run, debug unit tests without having to switch to a command prompt. I think initially it can support mocha or jasmine and be extendable to extend this support to new testing frameworks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-550) Update to latest Mars Graphiti 0.13

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-550: -------------------------------- Summary: Update to latest Mars Graphiti 0.13 Key: JBTIS-550 URL: https://issues.jboss.org/browse/JBTIS-550 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 9.0.0.Beta1 Reporter: Paul Leacu Assignee: Paul Leacu Mirror latest Graphiti to JBT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21613?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21613: ------------------------------------- I'll fix this. > 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 > Fix For: 4.3.1.CR1 > > > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21614: -------------------------------- Fix Version/s: 4.3.1.CR1 > OpenShift connection is not created when CDK server starts on Windows > --------------------------------------------------------------------- > > Key: JBIDE-21614 > URL: https://issues.jboss.org/browse/JBIDE-21614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.1.CR1 > > > I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer. > When I create and start CDK server on my Ubuntu it creates OpenShift connection. > When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS. > It worked before (sometime ago on a different installation). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21614: ------------------------------------- I'll investigate this. > OpenShift connection is not created when CDK server starts on Windows > --------------------------------------------------------------------- > > Key: JBIDE-21614 > URL: https://issues.jboss.org/browse/JBIDE-21614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.1.CR1 > > > I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer. > When I create and start CDK server on my Ubuntu it creates OpenShift connection. > When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS. > It worked before (sometime ago on a different installation). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21615) Cannot save changes for launch configuration in CDK Adapter Configuration Editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21615?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21615: ------------------------------------- As in all (most?) server adapters, we override parts of the launch configuration with information from the server editor. This is not the approved mechanism of changing the username or the password. Those must be done in the server editor itself and the credential framework. However, other changes to the launch configuration, such as changes to the 'main' tab, arguments, vagrant command location, etc, should be persisted, and adding new environment variables should also be persisted properly. However removing or changing critical variables (such as those set in server editor) will be overridden by the values in the server editor. I'm inclined to reject this JIRA, since other changes to the launch config are persisted as expected and I consider this to be functioning normally. > Cannot save changes for launch configuration in CDK Adapter Configuration Editor > -------------------------------------------------------------------------------- > > Key: JBIDE-21615 > URL: https://issues.jboss.org/browse/JBIDE-21615 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.0.Alpha1 > Environment: Windows 10 > Reporter: Denis Golovin > Attachments: CDK launch config changes are not saved.mp4 > > > Launch configuration changes discarded in CDK Server Configuration Editor see attached video -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21613?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21613: -------------------------------- Fix Version/s: 4.3.1.CR1 > 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 > Fix For: 4.3.1.CR1 > > > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21582) Server adapter: always publishes on Eclipse startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21582: ------------------------------------------ I would assume that the adapter should only publish if there are changes? > Server adapter: always publishes on Eclipse startup > --------------------------------------------------- > > Key: JBIDE-21582 > URL: https://issues.jboss.org/browse/JBIDE-21582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-704) JBDS-IS 8.0.5: Release Notes and link to tooling

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-704?page=com.atlassian.jira.plug... ] Andrej Podhradsky edited comment on TOOLSDOC-704 at 2/1/16 9:22 AM: -------------------------------------------------------------------- Regarding BPMN2 issues, please remove the following issue (we've found that it is not completely fixed, so we should rather omit it) - Bug 472174 - Event SubProcess may not have incoming or outgoing sequence flows was (Author: apodhrad): Regarding BPMN2 issues, please remove the following issue (we've found that it is not completely fixed, so we should rather omit it) Bug 472174 - Event SubProcess may not have incoming or outgoing sequence flows > JBDS-IS 8.0.5: Release Notes and link to tooling > ------------------------------------------------ > > Key: TOOLSDOC-704 > URL: https://issues.jboss.org/browse/TOOLSDOC-704 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new release notes and link to DV 6.3 docs page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-704) JBDS-IS 8.0.5: Release Notes and link to tooling

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-704?page=com.atlassian.jira.plug... ] Andrej Podhradsky commented on TOOLSDOC-704: -------------------------------------------- Regarding BPMN2 issues, please remove the following issue (we've found that it is not completely fixed, so we should rather omit it) Bug 472174 - Event SubProcess may not have incoming or outgoing sequence flows > JBDS-IS 8.0.5: Release Notes and link to tooling > ------------------------------------------------ > > Key: TOOLSDOC-704 > URL: https://issues.jboss.org/browse/TOOLSDOC-704 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new release notes and link to DV 6.3 docs page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 February 2016