September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24781) New Application Wizard: Propose to create OpenShift server adapters automatically

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24781?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24781. --------------------------------- Closing - work as expected. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.AM2 Build id: AM2-v20170905-0703-B967 Build date: 20170905-0703 > New Application Wizard: Propose to create OpenShift server adapters automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-24781 > URL: https://issues.jboss.org/browse/JBIDE-24781 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > I'm trying to push an Eclipse project as an OpenShift application with Red Hat Developer Studio. When I create the application, the wizard asks me for an Eclipse project. I would expect that a server adapter would be created by default for this project, or that at least creating a server adapter would be proposed automatically (but remain cancellable). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4412) DevSuite 1.4 Installer Make progress/status clearer/easier to see

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4412?page=com.atlassian.jira.plugin.... ] Mohit Suman resolved JBDS-4412. ------------------------------- Resolution: Done > DevSuite 1.4 Installer Make progress/status clearer/easier to see > ----------------------------------------------------------------- > > Key: JBDS-4412 > URL: https://issues.jboss.org/browse/JBDS-4412 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Mohit Suman > Priority: Minor > Labels: ui > Fix For: 11.x > > > The overall installation progress for DevSuite 1.4 is difficult to see. You've got to scroll back and forth through the boxes to look for the small text that indicates what's going on. > Suggestions: > # There should be an overall progress at the top > # There should be some indication it is still working > # the status text in the boxes is the same color and size as the version number and other comment text making it difficult to pick out. It's easy to miss that there is status text and that it is being updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24676: --------------------------------------- [~budhrg], I'm fine with that. Dots are already used in some parts of the startup process anyway - for example when applying xpaas additions or something. > CDK3 server adapter's console view is using wrong coding on all platforms > ------------------------------------------------------------------------- > > Key: JBIDE-24676 > URL: https://issues.jboss.org/browse/JBIDE-24676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.5.0.AM2 > Environment: Windows, Linux, macOS > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png > > > Console view on all platforms show strange characters. See the pic. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 closed JBIDE-24222. --------------------------------- Good news, Andre! I tried this in Windows yesterday and it works. Also, [~odockal] tried Linux yesterday. So I think we're ready to close this. > 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.1.AM2 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24965: ------------------------------------- Story Points: 4 Sprint: devex #137 September 2017 > Server adapter: fails to "Restart in Debug" > ------------------------------------------- > > Key: JBIDE-24965 > URL: https://issues.jboss.org/browse/JBIDE-24965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: image-2017-09-02-01-06-58-751.png > > > steps: > # EXEC: Create a nodejs-mongo-persistent application > # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent > # EXEC: start the server adapter via "Debug" > # ASSERT: debugging works > # EXEC: restart the server adapter via "Restart in Debug" > Result: > Debugging fails, you get the following error: > !image-2017-09-02-01-06-58-751.png! > In the log you find the following entry: > {code} > org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)" > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031 > !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24981: ---------------------------------------- Assignee: Andre Dietisheim > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.5.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !started-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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: ------------------------------------------ I can confirm that his now works for MacOS, yay! > 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.1.AM2 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24981: ------------------------------------- Attachment: (was: starte-even-though-failed-starting.png) > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.5.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !starte-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24981: ------------------------------------- Attachment: started-even-though-failed-starting.png > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.5.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !starte-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24981: ------------------------------------- Description: # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available # ASSERT: the server adapter is starting up !image-2017-09-04-22-15-46-383.png! Result: The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - after a few minutes, it fails with the following error: !image-2017-09-04-22-17-26-655.png! Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up !started-even-though-failed-starting.png! was: # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available # ASSERT: the server adapter is starting up !image-2017-09-04-22-15-46-383.png! Result: The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - after a few minutes, it fails with the following error: !image-2017-09-04-22-17-26-655.png! Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up !starte-even-though-failed-starting.png! > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.5.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !started-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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