January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25610) New Application Wizard: "Browse" and "New" buttons are misaligned horizontally

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25610?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25610: ---------------------------------- Assignee: Andre Dietisheim > New Application Wizard: "Browse" and "New" buttons are misaligned horizontally > ------------------------------------------------------------------------------ > > Key: JBIDE-25610 > URL: https://issues.jboss.org/browse/JBIDE-25610 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.5.3.AM1 > > Attachments: new-application-wizard-misaligned-browse.png, new-application-wizard.png > > > # EXEC: launch new application wizard > # ASSERT: wizard dialog shows up > Result: > !new-application-wizard.png! > the "New" and "Browse" button are horizontally misaligned > Expected: > Both buttons should be horizontally aligned on the left and right edge > The "Browse" button is also vertically misalgined when compared to the "Eclipse Project" text field. > !new-application-wizard-misaligned-browse.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25610) New Application Wizard: "Browse" and "New" buttons are misaligned horizontally

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25610?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25610: ------------------------------- Sprint: devex #144 January 2018 > New Application Wizard: "Browse" and "New" buttons are misaligned horizontally > ------------------------------------------------------------------------------ > > Key: JBIDE-25610 > URL: https://issues.jboss.org/browse/JBIDE-25610 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.5.3.AM1 > > Attachments: new-application-wizard-misaligned-browse.png, new-application-wizard.png > > > # EXEC: launch new application wizard > # ASSERT: wizard dialog shows up > Result: > !new-application-wizard.png! > the "New" and "Browse" button are horizontally misaligned > Expected: > Both buttons should be horizontally aligned on the left and right edge > The "Browse" button is also vertically misalgined when compared to the "Eclipse Project" text field. > !new-application-wizard-misaligned-browse.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25614) Upgrade embedded Jolokia client to 1.4.0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25614?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25614: ------------------------------- Sprint: devex #144 January 2018 > Upgrade embedded Jolokia client to 1.4.0 > ---------------------------------------- > > Key: JBIDE-25614 > URL: https://issues.jboss.org/browse/JBIDE-25614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > a new version of Jolokia is available. > Would be nice to leverage it. > Need to check that it is backward -compatible (but seems so at first-sight based on release notes) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25614) Upgrade embedded Jolokia client to 1.4.0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25614?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25614: ------------------------------- Fix Version/s: 4.5.3.AM1 > Upgrade embedded Jolokia client to 1.4.0 > ---------------------------------------- > > Key: JBIDE-25614 > URL: https://issues.jboss.org/browse/JBIDE-25614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > a new version of Jolokia is available. > Would be nice to leverage it. > Need to check that it is backward -compatible (but seems so at first-sight based on release notes) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25614) Upgrade embedded Jolokia client to 1.4.0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25614?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25614: ------------------------------- Affects Version/s: 4.5.2.Final > Upgrade embedded Jolokia client to 1.4.0 > ---------------------------------------- > > Key: JBIDE-25614 > URL: https://issues.jboss.org/browse/JBIDE-25614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > > a new version of Jolokia is available. > Would be nice to leverage it. > Need to check that it is backward -compatible (but seems so at first-sight based on release notes) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25614) Upgrade embedded Jolokia client to 1.4.0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25614?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25614: ---------------------------------- Assignee: Rob Stryker > Upgrade embedded Jolokia client to 1.4.0 > ---------------------------------------- > > Key: JBIDE-25614 > URL: https://issues.jboss.org/browse/JBIDE-25614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Aurélien Pupier > Assignee: Rob Stryker > > a new version of Jolokia is available. > Would be nice to leverage it. > Need to check that it is backward -compatible (but seems so at first-sight based on release notes) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25616: ------------------------------- Sprint: devex #144 January 2018 > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: java > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25616: ---------------------------------- Assignee: Jeff MAURY > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: java > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25616: ------------------------------- Fix Version/s: 4.5.3.AM2 > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: java > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25611: ------------------------------- Sprint: devex #144 January 2018 > Server adapter: timeouts when starting into "Debug" on OpenShift Online > ----------------------------------------------------------------------- > > Key: JBIDE-25611 > URL: https://issues.jboss.org/browse/JBIDE-25611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM1 > > Attachments: error-waiting-for-new-pod.png > > > # ASSERT: have an account on OpenShift Online > # EXEC: create a new application via template nodejs-mongo-persistent > # EXEC: have the project imported into the workspace and the server adapter for it created > # ASSERT: you have a new server adapter for your app in state [stopped] > # EXEC: start the adapter into "Debug" > Result: > The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog: > !error-waiting-for-new-pod.png! > In the Eclipse log you'll find the following: > {code} > org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 2018