June 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-733) [GTK] Display.getBounds() returns wrong values for most multi monitor setups [EBZ#547375]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-733?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-733. ------------------------------- Resolution: Done > [GTK] Display.getBounds() returns wrong values for most multi monitor setups [EBZ#547375] > ----------------------------------------------------------------------------------------- > > Key: ERT-733 > URL: https://issues.jboss.org/browse/ERT-733 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13, SWT, bzira > > Display.getBounds() should return a bounding box over all monitors. It should take into account each monitor's x and y values as well as their width and height. > The current implementation iterates over all available monitors, takes the width and height of the first one it can find and then simply adds the x and y values of all the other monitors on top. Therefore this algorithm only properly works when there are at most two monitors next to each other with the same screen resolution and they are iterated in order. > For example I have two monitors (2560x1440 and 1920x1080) horizontally aligned next to each other, with the smaller screen aligning at the bottom. I would have expected getBounds to return (0,0,2560+1920=4480,1440). Instead (0,0,5120,1800) is returned. If I align them at the top (0,0,5120,1440) is returned. If it had iterated them in the other possible order a different, also wrong result would have been returned. > The calculation of a proper bounding box should cover all possible use cases, including having more than two monitors, having different screen resolutions and having different setups like being aligned in multiple rows. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-733) [GTK] Display.getBounds() returns wrong values for most multi monitor setups [EBZ#547375]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-733?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-733: --------------------------------- Sprint: devex #168 June 2019 Assignee: Eric Williams > [GTK] Display.getBounds() returns wrong values for most multi monitor setups [EBZ#547375] > ----------------------------------------------------------------------------------------- > > Key: ERT-733 > URL: https://issues.jboss.org/browse/ERT-733 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13, SWT, bzira > > Display.getBounds() should return a bounding box over all monitors. It should take into account each monitor's x and y values as well as their width and height. > The current implementation iterates over all available monitors, takes the width and height of the first one it can find and then simply adds the x and y values of all the other monitors on top. Therefore this algorithm only properly works when there are at most two monitors next to each other with the same screen resolution and they are iterated in order. > For example I have two monitors (2560x1440 and 1920x1080) horizontally aligned next to each other, with the smaller screen aligning at the bottom. I would have expected getBounds to return (0,0,2560+1920=4480,1440). Instead (0,0,5120,1800) is returned. If I align them at the top (0,0,5120,1440) is returned. If it had iterated them in the other possible order a different, also wrong result would have been returned. > The calculation of a proper bounding box should cover all possible use cases, including having more than two monitors, having different screen resolutions and having different setups like being aligned in multiple rows. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26648) Add support for WF 17

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26648?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26648. --------------------------------- Basic operations works with server. Verified in: Red Hat CodeReady Studio Version: 12.12.0.GA Build id: GA-v20190615-0431-B4582 Build date: 20190615-0431 > Add support for WF 17 > --------------------- > > Key: JBIDE-26648 > URL: https://issues.jboss.org/browse/JBIDE-26648 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > WF17 will be released on May 30th (see https://wildfly.org/news/2019/03/09/Onward-to_WildFly-17/). WF17.0.0.Alpha1 is already out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26630) Fix builds for TP based on 2019-06.M2

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26630?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26630. --------------------------------- Closing, webservices are not failing anymore. > Fix builds for TP based on 2019-06.M2 > ------------------------------------- > > Key: JBIDE-26630 > URL: https://issues.jboss.org/browse/JBIDE-26630 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > When the 2019-06.M2 TP will be only, some builds may be failing because of API breaking changes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26624) webservices does not build anymore

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26624?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26624. --------------------------------- Closing - build is not failing anymore. > webservices does not build anymore > ---------------------------------- > > Key: JBIDE-26624 > URL: https://issues.jboss.org/browse/JBIDE-26624 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.12.0.AM1 > > > Build is failing because of a dependency -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26625) Fix builds for TP based on 2019-06M1

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26625?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26625. --------------------------------- PRs are merged. > Fix builds for TP based on 2019-06M1 > ------------------------------------ > > Key: JBIDE-26625 > URL: https://issues.jboss.org/browse/JBIDE-26625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26650) Fix builds for TP based on 2019-06.M3

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26650?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26650. --------------------------------- PRs are merged. > Fix builds for TP based on 2019-06.M3 > ------------------------------------- > > Key: JBIDE-26650 > URL: https://issues.jboss.org/browse/JBIDE-26650 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > When the 2019-06.M3 TP will be out, some builds may be failing because of API breaking changes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26666) Switch from WF17.Beta to WF17

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26666?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26666. --------------------------------- WF17 can be downloaded with codeready studio and starting/stopping works. Closing. Verified in: Red Hat CodeReady Studio Version: 12.12.0.GA Build id: GA-v20190615-0431-B4582 Build date: 20190615-0431 > Switch from WF17.Beta to WF17 > ----------------------------- > > Key: JBIDE-26666 > URL: https://issues.jboss.org/browse/JBIDE-26666 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26661) Fix dependencies on JDK8 for archives tests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26661?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26661. --------------------------------- Resolution: Done tests are back to green, closing. > Fix dependencies on JDK8 for archives tests > ------------------------------------------- > > Key: JBIDE-26661 > URL: https://issues.jboss.org/browse/JBIDE-26661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26667) Fix easyimport ITests dependencies

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26667?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26667. --------------------------------- Resolution: Done Closing, tests are back to green. > Fix easyimport ITests dependencies > ---------------------------------- > > Key: JBIDE-26667 > URL: https://issues.jboss.org/browse/JBIDE-26667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, integration-tests > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019