October 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26846) Update WildFly to version 18 in maven.itests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26846?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26846: ------------------------------------ Estimated Difficulty: Low (was: Medium) > Update WildFly to version 18 in maven.itests > -------------------------------------------- > > Key: JBIDE-26846 > URL: https://issues.jboss.org/browse/JBIDE-26846 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.12.0.Final > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. Complete the following tasks to upgrade WildFly in maven.itests to version 18: > * Update WildFly version to version 18 in examples.wildfly.itests -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26845) Update WildFly to version 18 in examples.wildfly.itests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26845?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26845: ------------------------------------ Estimated Difficulty: Medium (was: Low) > Update WildFly to version 18 in examples.wildfly.itests > ------------------------------------------------------- > > Key: JBIDE-26845 > URL: https://issues.jboss.org/browse/JBIDE-26845 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. Complete the following tasks to upgrade WildFly in examples.wildfly.itests to version 18: > * Update WildFly version to version 18 in examples.wildfly.itests > * Check and update entries in the *wildfly-blacklist* file > * Check and update entries in the *wildfly-blacklist-test-errors-regexes.json* file -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26846) Update WildFly to version 18 in maven.itests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26846?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26846: ------------------------------------ Estimated Difficulty: Medium (was: Low) > Update WildFly to version 18 in maven.itests > -------------------------------------------- > > Key: JBIDE-26846 > URL: https://issues.jboss.org/browse/JBIDE-26846 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.12.0.Final > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. Complete the following tasks to upgrade WildFly in maven.itests to version 18: > * Update WildFly version to version 18 in examples.wildfly.itests -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim updated JBDS-4789: ----------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/517, https://github.com/jbdevstudio/jbdevstudio-product/pull/519 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/517) > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: openshift, product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 12.13.0.AM1 > > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim reassigned JBDS-4789: -------------------------------------- Assignee: Ondrej Dockal (was: André Dietisheim) > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: openshift, product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.13.0.AM1 > > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26886) Update Quarkus dependency to release 0.23.2

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26886?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26886: ------------------------------ Fix Version/s: 4.13.0.Final > Update Quarkus dependency to release 0.23.2 > ------------------------------------------- > > Key: JBIDE-26886 > URL: https://issues.jboss.org/browse/JBIDE-26886 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: quarkus > Affects Versions: 4.13.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.13.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26886) Update Quarkus dependency to release 0.23.2

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26886?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26886: --------------------------------- Assignee: Koen Aers > Update Quarkus dependency to release 0.23.2 > ------------------------------------------- > > Key: JBIDE-26886 > URL: https://issues.jboss.org/browse/JBIDE-26886 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: quarkus > Affects Versions: 4.13.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26886) Update Quarkus dependency to release 0.23.2

by Koen Aers (Jira)

Koen Aers created JBIDE-26886: --------------------------------- Summary: Update Quarkus dependency to release 0.23.2 Key: JBIDE-26886 URL: https://issues.jboss.org/browse/JBIDE-26886 Project: Tools (JBoss Tools) Issue Type: Task Components: quarkus Affects Versions: 4.13.0.AM1 Reporter: Koen Aers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-764) [HiDPI][GTK] SWT to receive/handle DPI change notification from OS [EBZ#537896]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-764?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-764. ------------------------------- Resolution: Done > [HiDPI][GTK] SWT to receive/handle DPI change notification from OS [EBZ#537896] > ------------------------------------------------------------------------------- > > Key: ERT-764 > URL: https://issues.jboss.org/browse/ERT-764 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Trivial > Labels: SWT, bzira > > +++ This bug was initially created as a clone of Bug #515502 +++ > Tutorial: Writing High-DPI Win32 Applications > https://msdn.microsoft.com/en-us/library/windows/desktop/dd464659%28v=vs.... > As per above MSDN there is a event notification 'WM_DPICHANGED' sent to applications with SetProcessDpiAwareness set to 'PROCESS_PER_MONITOR_DPI_AWARE'. > SWT needs above mechanism to be in place, to start receive the DPI change notification from OS and then re-layout accordingly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-764) [HiDPI][GTK] SWT to receive/handle DPI change notification from OS [EBZ#537896]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-764?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-764: --------------------------------- Sprint: devex #173 Oct 2019 Assignee: Eric Williams > [HiDPI][GTK] SWT to receive/handle DPI change notification from OS [EBZ#537896] > ------------------------------------------------------------------------------- > > Key: ERT-764 > URL: https://issues.jboss.org/browse/ERT-764 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Trivial > Labels: SWT, bzira > > +++ This bug was initially created as a clone of Bug #515502 +++ > Tutorial: Writing High-DPI Win32 Applications > https://msdn.microsoft.com/en-us/library/windows/desktop/dd464659%28v=vs.... > As per above MSDN there is a event notification 'WM_DPICHANGED' sent to applications with SetProcessDpiAwareness set to 'PROCESS_PER_MONITOR_DPI_AWARE'. > SWT needs above mechanism to be in place, to start receive the DPI change notification from OS and then re-layout accordingly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2019