May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4397) Update year to 2017 on devstudio starting logo

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4397?page=com.atlassian.jira.plugin.... ] Ondrej Dockal reassigned JBDS-4397: ----------------------------------- Assignee: Nick Boldt > Update year to 2017 on devstudio starting logo > ---------------------------------------------- > > Key: JBDS-4397 > URL: https://issues.jboss.org/browse/JBDS-4397 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.GA > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Attachments: Screenshot_20170517_140926.png > > > We should update logo copyright year from 2016 to 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4397) Update year to 2017 on devstudio starting logo

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBDS-4397: ----------------------------------- Summary: Update year to 2017 on devstudio starting logo Key: JBDS-4397 URL: https://issues.jboss.org/browse/JBDS-4397 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Affects Versions: 10.4.0.GA Reporter: Ondrej Dockal Attachments: Screenshot_20170517_140926.png We should update logo copyright year from 2016 to 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24222: --------------------------------------- I tried this now with devstudio 10.4.0.GA and cdk 3.0.0 and it still fails for me. > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1075) Update BPMN2 Modeler to 1.3.3 (Neon)

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1075?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1075. ------------------------------------ Verified with Devstudio IS 10.3.0.CR2 which contains | BPMN2 | 1.3.1.Final-v20160927-2047-B56 | | BPMN2 Modeler | 1.3.3.Final-v20170221-1647-B60 | > Update BPMN2 Modeler to 1.3.3 (Neon) > ------------------------------------ > > Key: JBTIS-1075 > URL: https://issues.jboss.org/browse/JBTIS-1075 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 10.2.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 10.3.0.GA > > > Update to the latest BPMN2 Modeler. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24453) NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24453?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24453: ---------------------------------------- Assignee: Rob Stryker > NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24453 > URL: https://issues.jboss.org/browse/JBIDE-24453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NoClassDefFoundError: Could not initialize class com.spotify.docker.client.DefaultDockerClient > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66) > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252) > at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30) > at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182) > 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:198) > 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:2191) > at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728) > at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077) > at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370) > 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:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203) > The reporter(s) left the following comment(s): > --- Anonymous wrote on 56e0: --- > cannot select server in server view. > Bundles: > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 | > | org.eclipse.linuxtools.docker.core | 2.1.0.201612072123 | 2.3.0.201703072040 | > | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 | > | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 | > | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 | > | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 | > | org.jboss.tools.openshift.cdk.server | 3.3.2.v20170216-0102 | 3.3.2.v20170216-0102 | > Operating Systems: > | Linux | 3.12.67 | 3.16.0 | > | MacOSX | 10.12.3 | 10.12.4 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581a1e4ae4b0e3eea94... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24453) NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-24453: ----------------------------------------------------- Summary: NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient) Key: JBIDE-24453 URL: https://issues.jboss.org/browse/JBIDE-24453 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.NoClassDefFoundError: Could not initialize class com.spotify.docker.client.DefaultDockerClient at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66) at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252) at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30) at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265) at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60) at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50) at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29) at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104) at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182) 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:198) 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:2191) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077) at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370) 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:182) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203) The reporter(s) left the following comment(s): --- Anonymous wrote on 56e0: --- cannot select server in server view. Bundles: | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 | | org.eclipse.linuxtools.docker.core | 2.1.0.201612072123 | 2.3.0.201703072040 | | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 | | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 | | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 | | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 | | org.jboss.tools.openshift.cdk.server | 3.3.2.v20170216-0102 | 3.3.2.v20170216-0102 | Operating Systems: | Linux | 3.12.67 | 3.16.0 | | MacOSX | 10.12.3 | 10.12.4 | | Windows | 6.1.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581a1e4ae4b0e3eea94... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23069: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Server adapter wizard: Importing of project should skip Select Build Config wizard page > --------------------------------------------------------------------------------------- > > Key: JBIDE-23069 > URL: https://issues.jboss.org/browse/JBIDE-23069 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.5.x > > > This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24222: ------------------------------------------ [~mmalina] [~rob.stryker] I tested this yesterday with latest CDK and JBT, it doesnt work :( > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017