[JBoss JIRA] (ERT-752) [GTK] Git Reflog - branch symbol on the upper right corner does not react [EBZ#546914]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-752:
---------------------------------------
Summary: [GTK] Git Reflog - branch symbol on the upper right corner does not react [EBZ#546914]
Key: ERT-752
URL: https://issues.jboss.org/browse/ERT-752
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Created attachment 278467
Git Reflog - Branch symbol
If I hover over the branch symbol in the Git Reflog view I see, that it can be clicked, but if I click on it nothing happens. I would expect to be able to select a branch when clicking on it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/21/19 4:39 AM:
-------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod. As far as I can see the springboot app is not started in devmode. Very likely that we'd need to use a springboot compliant fabric8 image instead.
[~jgammonred612] any insights into how you had springboot started in devmode with this setup, please?
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod. As far as I can see the springboot app is not started in devmode. Very likely that we'd need to use a springboot complaint fabric8 image instead.
[~jgammonred612] any insights into how you had springboot started in devmode with this setup, please?
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/21/19 4:38 AM:
-------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod. As far as I can see the springboot app is not started in devmode. Very likely that we'd need to use a springboot complaint fabric8 image instead.
[~jgammonred612] any insights into how you had springboot started in devmode with this setup, please?
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod. As if the springboot app wasn't started in dev mode.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26796) org.jboss.tools.maven.core is not compiling in Eclipse, complains about missing ProjectUtilities
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26796?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26796:
-------------------------------------
Priority: Critical (was: Major)
> org.jboss.tools.maven.core is not compiling in Eclipse, complains about missing ProjectUtilities
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26796
> URL: https://issues.jboss.org/browse/JBIDE-26796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.13.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: use TP 4.13.AM1 matching Eclipse 2019-06
> # EXEC: import jbosstools-central into workspace
> Result:
> Eclipse reports a compilation error for *org.jboss.tools.maven.core*
> {quote}The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.jem.util.emf.workbench.ProjectUtilities{quote}
> !screenshot-1.png!
> !screenshot-2.png!
> Interestingly, things compile fine in maven, no errors.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/20/19 12:25 PM:
--------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
Result:
REST endpoint can be reached at *<service-host>/ws/info*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/20/19 12:25 PM:
--------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod. As if the springboot app wasn't started in dev mode.
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
# ASSERT: have source code imported to Eclipse, server adapter created
# EXEC: start server adapter in "Debug"
Result:
REST endpoint can be reached at *<service-host>/ws/info*.
Debugger fails to connect to the remote jvm even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/20/19 12:23 PM:
--------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use *https://github.com/openshift-roadshow/nationalparks.git* in *Git Repository URL:*, remove the *Context Directory:*
Result:
REST endpoint can be reached at *<service-host>/ws/info*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use *https://github.com/openshift-roadshow/nationalparks.git* in *Git Repository URL:*, remove the *Context Directory:*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/20/19 12:24 PM:
--------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use https://github.com/openshift-roadshow/nationalparks.git in *Git Repository URL:*, remove the *Context Directory:*
Result:
REST endpoint can be reached at *<service-host>/ws/info*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use *https://github.com/openshift-roadshow/nationalparks.git* in *Git Repository URL:*, remove the *Context Directory:*
Result:
REST endpoint can be reached at *<service-host>/ws/info*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/20/19 12:20 PM:
--------------------------------------------------------------------
source code that's used is likely here: https://github.com/openshift-roadshow
The backend can be deployed using an openjdk builder image while using the following git repository: https://github.com/openshift-roadshow/nationalparks.git
steps:
# EXEC: New > Application > redhat-openjdk18-openshift:1.5 & Next
# EXEC: use *https://github.com/openshift-roadshow/nationalparks.git* in *Git Repository URL:*, remove the *Context Directory:*
I currently fail to connect the java remote debugger even though port forwarding works and reports that :8787 is forwarded to :67980 on the pod.
was (Author: adietish):
source code that's used is likely here: https://github.com/openshift-roadshow
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months