September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24966: ------------------------------- Affects Version/s: 4.5.1.AM2 > linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 > ------------------------------------------------------------------------------ > > Key: JBIDE-24966 > URL: https://issues.jboss.org/browse/JBIDE-24966 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Jeff Johnston > Priority: Blocker > Fix For: 4.5.1.AM2 > > > Turns out we have a blocker here. > org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. > Therefore this manifest needs to be changed: > {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} > Require-Bundle: org.junit,org.eclipse.swt, > org.eclipse.ui,org.eclipse.osgi,org.eclipse.core.runtime, > org.jboss.reddeer.eclipse;bundle-version="1.2.1", > org.jboss.reddeer.common;bundle-version="1.2.1", > org.jboss.reddeer.swt;bundle-version="1.2.1", > org.jboss.reddeer.core;bundle-version="1.2.1", > org.jboss.reddeer.workbench;bundle-version="1.2.1", > org.apac he.commons.lang;bundle-version="2.6.0",org.eclipse.linuxtools.docker. > core,org.hamcrest.library;bundle-version="1.3.0",org.hamcrest.core;bu > ndle-version="1.3.0"{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24966: ------------------------------- Component/s: build docker target-platform > linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 > ------------------------------------------------------------------------------ > > Key: JBIDE-24966 > URL: https://issues.jboss.org/browse/JBIDE-24966 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, docker, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Jeff Johnston > Priority: Blocker > Fix For: 4.5.1.AM2 > > > Turns out we have a blocker here. > org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. > Therefore this manifest needs to be changed: > {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} > Require-Bundle: org.junit,org.eclipse.swt, > org.eclipse.ui,org.eclipse.osgi,org.eclipse.core.runtime, > org.jboss.reddeer.eclipse;bundle-version="1.2.1", > org.jboss.reddeer.common;bundle-version="1.2.1", > org.jboss.reddeer.swt;bundle-version="1.2.1", > org.jboss.reddeer.core;bundle-version="1.2.1", > org.jboss.reddeer.workbench;bundle-version="1.2.1", > org.apac he.commons.lang;bundle-version="2.6.0",org.eclipse.linuxtools.docker. > core,org.hamcrest.library;bundle-version="1.3.0",org.hamcrest.core;bu > ndle-version="1.3.0"{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24966: ------------------------------- Parent: (was: JBIDE-24937) Issue Type: Bug (was: Sub-task) > linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 > ------------------------------------------------------------------------------ > > Key: JBIDE-24966 > URL: https://issues.jboss.org/browse/JBIDE-24966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Jeff Johnston > Priority: Blocker > Fix For: 4.5.1.AM2 > > > Turns out we have a blocker here. > org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. > Therefore this manifest needs to be changed: > {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} > Require-Bundle: org.junit,org.eclipse.swt, > org.eclipse.ui,org.eclipse.osgi,org.eclipse.core.runtime, > org.jboss.reddeer.eclipse;bundle-version="1.2.1", > org.jboss.reddeer.common;bundle-version="1.2.1", > org.jboss.reddeer.swt;bundle-version="1.2.1", > org.jboss.reddeer.core;bundle-version="1.2.1", > org.jboss.reddeer.workbench;bundle-version="1.2.1", > org.apac he.commons.lang;bundle-version="2.6.0",org.eclipse.linuxtools.docker. > core,org.hamcrest.library;bundle-version="1.3.0",org.hamcrest.core;bu > ndle-version="1.3.0"{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24966: ---------------------------------- Summary: linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 Key: JBIDE-24966 URL: https://issues.jboss.org/browse/JBIDE-24966 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Nick Boldt Priority: Blocker Turns out we have a blocker here. org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. Therefore this manifest needs to be changed: {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} Require-Bundle: org.junit,org.eclipse.swt, org.eclipse.ui,org.eclipse.osgi,org.eclipse.core.runtime, org.jboss.reddeer.eclipse;bundle-version="1.2.1", org.jboss.reddeer.common;bundle-version="1.2.1", org.jboss.reddeer.swt;bundle-version="1.2.1", org.jboss.reddeer.core;bundle-version="1.2.1", org.jboss.reddeer.workbench;bundle-version="1.2.1", org.apac he.commons.lang;bundle-version="2.6.0",org.eclipse.linuxtools.docker. core,org.hamcrest.library;bundle-version="1.3.0",org.hamcrest.core;bu ndle-version="1.3.0"{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24966: ------------------------------- Fix Version/s: 4.5.1.AM2 > linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 > ------------------------------------------------------------------------------ > > Key: JBIDE-24966 > URL: https://issues.jboss.org/browse/JBIDE-24966 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.AM2 > > > Turns out we have a blocker here. > org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. > Therefore this manifest needs to be changed: > {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} > Require-Bundle: org.junit,org.eclipse.swt, > org.eclipse.ui,org.eclipse.osgi,org.eclipse.core.runtime, > org.jboss.reddeer.eclipse;bundle-version="1.2.1", > org.jboss.reddeer.common;bundle-version="1.2.1", > org.jboss.reddeer.swt;bundle-version="1.2.1", > org.jboss.reddeer.core;bundle-version="1.2.1", > org.jboss.reddeer.workbench;bundle-version="1.2.1", > org.apac he.commons.lang;bundle-version="2.6.0",org.eclipse.linuxtools.docker. > core,org.hamcrest.library;bundle-version="1.3.0",org.hamcrest.core;bu > ndle-version="1.3.0"{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24934) Update org.eclipse.launchbar on Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24934?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24934: ------------------------------------ PR: https://github.com/jbosstools/jbosstools-target-platforms/pull/268 However, blocked by JBIDE-24948 and JBIDE-24937. > Update org.eclipse.launchbar on Target Platform > ----------------------------------------------- > > Key: JBIDE-24934 > URL: https://issues.jboss.org/browse/JBIDE-24934 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > Please update org.eclipse.launchbar on target platform, current version (2.1.1.201706131403) on target platform has a deadlock, which is fixed http://git.eclipse.org/c/cdt/org.eclipse.launchbar.git/commit/?id=64f1d0b... and http://git.eclipse.org/c/cdt/org.eclipse.launchbar.git/commit/?id=ff9289d... > I have tried version 2.1.1.201706151520, which looks good, but you can use newer version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24948) Update RedDeer in TP to 2.0.0.Beta

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24948?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24948: ------------------------------------ PR: https://github.com/jbosstools/jbosstools-target-platforms/pull/268 However, this happened: {code} [ERROR] Software being installed: org.eclipse.linuxtools.docker.tests.feature.feature.group 3.1.0.201708010032 [ERROR] Missing requirement: org.eclipse.linuxtools.docker.reddeer 1.0.0.201708010032 requires 'bundle org.jboss.reddeer.eclipse 1.2.1' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.linuxtools.docker.tests.feature.feature.group 3.1.0.201708010032 depends on: org.eclipse.linuxtools.docker.reddeer [1.0.0.201708010032] {code} So looks like this depends on JBIDE-24937. > Update RedDeer in TP to 2.0.0.Beta > ---------------------------------- > > Key: JBIDE-24948 > URL: https://issues.jboss.org/browse/JBIDE-24948 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > We would like to update reddeer in TP to 2.0.0.Beta. Update site at eclipse is here http://download.eclipse.org/reddeer/milestones/2.0.0.Beta/ > Im not sure which job at CCI I should use to mirror the eclipse site so I will leave it for you [~nickboldt] . -- 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)

Andre Dietisheim created JBIDE-24965: ---------------------------------------- Summary: 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.0.AM2 Reporter: Andre Dietisheim Priority: Critical 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-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 6:33 PM: ------------------------------------------------------------------ [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up & terminates when you F8. I guess that requires more investigations. We btw. respect the preference to use the internal or external browser. * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up and terminates once you have it continue after the breakpoint (F8). So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24948) Update RedDeer in TP to 2.0.0.Beta

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24948?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24948: ------------------------------------ Pulling [1] RedDeer 2.0.0.Beta to here: http://download.jboss.org/jbosstools/updates/requirements/reddeer/ [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Update RedDeer in TP to 2.0.0.Beta > ---------------------------------- > > Key: JBIDE-24948 > URL: https://issues.jboss.org/browse/JBIDE-24948 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > We would like to update reddeer in TP to 2.0.0.Beta. Update site at eclipse is here http://download.eclipse.org/reddeer/milestones/2.0.0.Beta/ > Im not sure which job at CCI I should use to mirror the eclipse site so I will leave it for you [~nickboldt] . -- 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