January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25504: ------------------------------- Sprint: devex #144 January 2018 > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.x > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: Andre Dietisheim > 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: Andre Dietisheim > Priority: Critical > Labels: cdk, connection > Fix For: 4.5.3.AM1 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 updated JBIDE-25586: ------------------------------- Sprint: devex #144 January 2018 > 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: Andre Dietisheim > Priority: Critical > Labels: cdk, connection > Fix For: 4.5.3.AM1 > > > But, connecting to online openshift instance works. -- 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 Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25616: ------------------------------------- Summary: 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 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-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25586: ------------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.x) > 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 > Priority: Critical > Labels: cdk, connection > Fix For: 4.5.3.AM1 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25375. --------------------------------- Closing, this error message is gone, please follow up linked JIRAs. Verified in: Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25375 > URL: https://issues.jboss.org/browse/JBIDE-25375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.Final > > > {code:java} > 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 46271 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98) > 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) > eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520 > java.version=1.8.0_144 > 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 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25615) Update test cases for server in Polarion

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25615: ------------------------------------- Summary: Update test cases for server in Polarion Key: JBIDE-25615 URL: https://issues.jboss.org/browse/JBIDE-25615 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, server Affects Versions: 4.5.2.Final Reporter: Josef Kopriva Assignee: Josef Kopriva Add latest EAP and WildFly, remove servers with expired support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4652) JDK9 Certification - javascript

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4652?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-4652: ----------------------------- Fix Version/s: 11.x > JDK9 Certification - javascript > ------------------------------- > > Key: JBDS-4652 > URL: https://issues.jboss.org/browse/JBDS-4652 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: javascript > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 11.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25584) batch itests on macosx fail or timeout most of the time

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25584?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-25584: ------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.2.Final) > batch itests on macosx fail or timeout most of the time > ------------------------------------------------------- > > Key: JBIDE-25584 > URL: https://issues.jboss.org/browse/JBIDE-25584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.5.3.AM1 > > > Not sure if we care about this since the tests pass on Win10 and RHEL7, but the Batch tests on OSX pretty consistently either timeout (120 mins) or fail. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Last good build was 20 runs ago on Jan 12: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So if only one good build happens in 20+ runs over 2 days... there's a problem. > Related question is: why is this test running so often? 20 itest runs in 2 days? Seems overkill, no? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-25455: --------------------------------------------- this really has nothing to do about management - having buildship listed on it is own is counter to everything else there are in our marketplace entries. i.e. m2e that is a first class citization is not installable as first level feature from jbosstools marketplace is it ? Why is buildship now treated as special. > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Labels: releasework > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- 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