June 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ] André Dietisheim updated JBDS-4777: ----------------------------------- Labels: openshift (was: ) > Please document procedure (if possible) for defining Debug port, Deployment path > -------------------------------------------------------------------------------- > > Key: JBDS-4777 > URL: https://issues.jboss.org/browse/JBDS-4777 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio 12.11 > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Labels: openshift > Fix For: 12.x > > Attachments: Problem_Description.pdf > > > Please document procedure for pre-filling the following in Adapter Server Settings: > - Pod Deployment Path > - Debugging Key > - Debugging Port > Can this be done via image Labels from an imported Docker image? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ] André Dietisheim commented on JBDS-4777: ---------------------------------------- Hi Rick As you can see in the screenshot of the wizard the 3 values should be extracted from the labels that are defined in the docker image. The default is that the checkboxes for this sake are checked and thus docker image labels should be inspected, the values contained within used. It's only when those checkboxes are unchecked that you can manually provide values. The labels we extract are the following. {code} com.redhat.dev-mode DEBUG:true com.redhat.dev-mode.port JPDA_ADDRESS:8000 com.redhat.deployments-dir /opt/webserver/webapps {code} If this doesnt work as expected, we might face a bug in the particular usecase. > Please document procedure (if possible) for defining Debug port, Deployment path > -------------------------------------------------------------------------------- > > Key: JBDS-4777 > URL: https://issues.jboss.org/browse/JBDS-4777 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio 12.11 > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Attachments: Problem_Description.pdf > > > Please document procedure for pre-filling the following in Adapter Server Settings: > - Pod Deployment Path > - Debugging Key > - Debugging Port > Can this be done via image Labels from an imported Docker image? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26676) Central CI: Update mac slaves in Central CI

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26676?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-26676: --------------------------------------- Domek: Sierra to High Sierra dev-platform-mac1: High Sierra to Mojave dev-platform-mac2: High Sierra to Mojave > Central CI: Update mac slaves in Central CI > ------------------------------------------- > > Key: JBIDE-26676 > URL: https://issues.jboss.org/browse/JBIDE-26676 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.12.0.Final > 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-26676) Central CI: Update mac slaves in Central CI

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26676: ------------------------------------- Summary: Central CI: Update mac slaves in Central CI Key: JBIDE-26676 URL: https://issues.jboss.org/browse/JBIDE-26676 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Affects Versions: 4.12.0.Final Reporter: Josef Kopriva Assignee: Josef Kopriva 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-26673) Dependency on org.eclipse.rse.ui 3.3 affects installation

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26673: ------------------------------------------ [~rob.stryker] do you know? Did we ever try to use a newer rse? Would this work? > Dependency on org.eclipse.rse.ui 3.3 affects installation > --------------------------------------------------------- > > Key: JBIDE-26673 > URL: https://issues.jboss.org/browse/JBIDE-26673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: This happens on eclipse Luna and Oxygen installing from the marketplace or directly from eclipse when creating a new JBOSS server > Reporter: Manuel Parrao > Priority: Minor > > I have a product that uses different plugins and some of them failed to be installed if JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui V4.6. On the other hand if I install first the other plugins and then try to install JBOSS tools, JBOSS does not get installed due the same dependency issue. > Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26675) Server ITests: update ITests to use WF17

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26675: ------------------------------------- Summary: Server ITests: update ITests to use WF17 Key: JBIDE-26675 URL: https://issues.jboss.org/browse/JBIDE-26675 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, server Affects Versions: 4.12.0.Final Reporter: Josef Kopriva Assignee: Josef Kopriva 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-26674) Update Forge ITests to use WF17

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26674: ------------------------------------- Summary: Update Forge ITests to use WF17 Key: JBIDE-26674 URL: https://issues.jboss.org/browse/JBIDE-26674 Project: Tools (JBoss Tools) Issue Type: Task Components: forge, integration-tests Affects Versions: 4.12.0.Final Reporter: Josef Kopriva Assignee: Josef Kopriva -- 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 Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-733: --------------------------------------- Summary: [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 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] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

by Rick Wagner (Jira)

[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ] Rick Wagner commented on JBDS-4777: ----------------------------------- Please see attached screen snap. Can the highlighted fields be pre-filled from some attributes from an imported Docker image? > Please document procedure (if possible) for defining Debug port, Deployment path > -------------------------------------------------------------------------------- > > Key: JBDS-4777 > URL: https://issues.jboss.org/browse/JBDS-4777 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio 12.11 > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Attachments: Problem_Description.pdf > > > Please document procedure for pre-filling the following in Adapter Server Settings: > - Pod Deployment Path > - Debugging Key > - Debugging Port > Can this be done via image Labels? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

by Rick Wagner (Jira)

[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ] Rick Wagner updated JBDS-4777: ------------------------------ Description: Please document procedure for pre-filling the following in Adapter Server Settings: - Pod Deployment Path - Debugging Key - Debugging Port Can this be done via image Labels from an imported Docker image? was: Please document procedure for pre-filling the following in Adapter Server Settings: - Pod Deployment Path - Debugging Key - Debugging Port Can this be done via image Labels? > Please document procedure (if possible) for defining Debug port, Deployment path > -------------------------------------------------------------------------------- > > Key: JBDS-4777 > URL: https://issues.jboss.org/browse/JBDS-4777 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio 12.11 > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Attachments: Problem_Description.pdf > > > Please document procedure for pre-filling the following in Adapter Server Settings: > - Pod Deployment Path > - Debugging Key > - Debugging Port > Can this be done via image Labels from an imported Docker image? -- 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