September 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26230) Implement Tycho build

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26230: -------------------------------- Story Points: 5 > Implement Tycho build > --------------------- > > Key: JBIDE-26230 > URL: https://issues.jboss.org/browse/JBIDE-26230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.9.x > > > Switch the Maven build to Tycho for: > * centralized management of dependencies > * unit tests in OSGI env -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26117: ------------------------------- Sprint: (was: devex #155 September 2018) > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.x > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26117: ------------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.Final) > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.x > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-25000: -------------------------------- Story Points: 13 (was: 16) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > 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:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-25830: -------------------------------- Story Points: 8 > After starting CDK server adapter OpenShift Connection does not work when oc is not on path > ------------------------------------------------------------------------------------------- > > Key: JBIDE-25830 > URL: https://issues.jboss.org/browse/JBIDE-25830 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.5.3.AM3 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: cdk_server_adapter, connection > Fix For: 4.9.0.Final > > Attachments: edit-connection-advanced.png > > > OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter. > steps: > # ASSERT: oc is not on path > # EXEC: Start CDK server adapter > # ASSERT: OpenShift connection is created, but does not fully work (all oc related operations wont) > Error: oc is not set for OpenShift connection to CDK and OpenShift connection does not work. > Expected: OpenShift connection should be working without user touch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4730: ---------------------------------- Thanks. I believe the name is only CodeReady Studio, not Red Hat CodeReady Studio, but they'll know best. :D > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] James Cobb commented on JBDS-4730: ---------------------------------- [~nickboldt] - I'll reach out to Brand and see if they have the official logotype for "Red Hat CodeReady Studio" > Use "CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26232) Implement CDK support

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26232?page=com.atlassian.jira.plugi... ] Mohit Suman commented on JBIDE-26232: ------------------------------------- Created on gh: https://github.com/redhat-developer/rsp-server/issues/38 > Implement CDK support > --------------------- > > Key: JBIDE-26232 > URL: https://issues.jboss.org/browse/JBIDE-26232 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.x > > > In addition to upstream CDK, we should support Red Hat CDK supports in RST as well -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26232) Implement CDK support

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26232?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26232: -------------------------------- Story Points: 5 > Implement CDK support > --------------------- > > Key: JBIDE-26232 > URL: https://issues.jboss.org/browse/JBIDE-26232 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.x > > > In addition to upstream CDK, we should support Red Hat CDK supports in RST as well -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25586: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK > ---------------------------------------------------------------- > > Key: JBIDE-25586 > URL: https://issues.jboss.org/browse/JBIDE-25586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.2.Final > Environment: FC27 > OpenJDK 9.0.1 > CDK v3.3.0-rc.1-1 > eclipse.buildId=11.2.0.GA-v20180115-0516-B1866 > java.version=9.0.1 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Critical > Labels: cdk, connection > Fix For: 4.9.0.Final > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 2018