August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4710: ---------------------------------- Fixed in upstream for M3, so we can verify this is fixed once devstudio TP is updated to simrel 2018-09 M3. > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM3 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4710: ----------------------------- Fix Version/s: 12.9.0.AM3 (was: 12.x) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM3 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25205) Integration Tests: OSExplorerResourceTest stabilization

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25205?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25205: ---------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.x) > Integration Tests: OSExplorerResourceTest stabilization > ------------------------------------------------------- > > Key: JBIDE-25205 > URL: https://issues.jboss.org/browse/JBIDE-25205 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.9.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25206) Integration Tests: TriggerBuildTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25206?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25206: ---------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.x) > Integration Tests: TriggerBuildTest > ----------------------------------- > > Key: JBIDE-25206 > URL: https://issues.jboss.org/browse/JBIDE-25206 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.9.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final

by Junqi Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ] Junqi Zhao updated JBIDE-26324: ------------------------------- Description: Port forwarding failed for JBoss Tools 4.6.0.Final error is in the followings, the failed reason is flag "-p" is deprecated An internal error occurred during: "Starting port forwarding...". OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p Usage: oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] Examples: # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod oc port-forward mypod 5000 6000 # Listens on port 8888 locally, forwarding to 5000 in the pod oc port-forward mypod 8888:5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod :5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod 0:5000 Options: --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running Use "oc options" for a list of global command-line options (applies to all commands). was: Port forwarding failed for JBoss Tools 4.6.0.Final error is in the followings, flag "-p" is deprecated An internal error occurred during: "Starting port forwarding...". OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p Usage: oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] Examples: # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod oc port-forward mypod 5000 6000 # Listens on port 8888 locally, forwarding to 5000 in the pod oc port-forward mypod 8888:5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod :5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod 0:5000 Options: --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running Use "oc options" for a list of global command-line options (applies to all commands). > Port forwarding failed for JBoss Tools 4.6.0.Final > -------------------------------------------------- > > Key: JBIDE-26324 > URL: https://issues.jboss.org/browse/JBIDE-26324 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Environment: JBoss Tools 4.6.0.Final > $ oc version > oc v3.11.0-0.24.0 > kubernetes v1.11.0+d4cacc0 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Reporter: Junqi Zhao > Attachments: port_forward.png > > > Port forwarding failed for JBoss Tools 4.6.0.Final > error is in the followings, the failed reason is flag "-p" is deprecated > An internal error occurred during: "Starting port forwarding...". > OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p > Usage: > oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] > Examples: > # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod > oc port-forward mypod 5000 6000 > > # Listens on port 8888 locally, forwarding to 5000 in the pod > oc port-forward mypod 8888:5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod :5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod 0:5000 > Options: > --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running > Use "oc options" for a list of global command-line options (applies to all commands). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final

by Junqi Zhao (JIRA)

Junqi Zhao created JBIDE-26324: ---------------------------------- Summary: Port forwarding failed for JBoss Tools 4.6.0.Final Key: JBIDE-26324 URL: https://issues.jboss.org/browse/JBIDE-26324 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.6.0.Final Environment: JBoss Tools 4.6.0.Final $ oc version oc v3.11.0-0.24.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Reporter: Junqi Zhao Attachments: port_forward.png Port forwarding failed for JBoss Tools 4.6.0.Final error is in the followings, flag "-p" is deprecated An internal error occurred during: "Starting port forwarding...". OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p Usage: oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] Examples: # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod oc port-forward mypod 5000 6000 # Listens on port 8888 locally, forwarding to 5000 in the pod oc port-forward mypod 8888:5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod :5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod 0:5000 Options: --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running Use "oc options" for a list of global command-line options (applies to all commands). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26314) Review Polarion test cases for OpenShift

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26314?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26314. --------------------------------- Resolution: Done Test cases are updated. Closing. > Review Polarion test cases for OpenShift > ---------------------------------------- > > Key: JBIDE-26314 > URL: https://issues.jboss.org/browse/JBIDE-26314 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM3 > > > Add new test cases and delete not relevant cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18654: ------------------------------------ I've cloned the JDK9 jobs for base, server, javaee and hibernate. Can do more later but for now there's the usual suspects. cc: [~jeffmaury][~rob.stryker] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... HOWEVER... seems our JBoss Nexus doesn't work with JDK 11 ea25, so I've reported this upstream in case it's a problem in Nexus itself, rather than in OUR Nexus. https://issues.sonatype.org/browse/NEXUS-17859 > run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.9.0.AM3 > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-664) Orca and flat review problems [EBZ#536974]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-664: --------------------------------------- Summary: Orca and flat review problems [EBZ#536974] Key: ERT-664 URL: https://issues.jboss.org/browse/ERT-664 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot I can not read information present in the screen using flat review mode. The problem can be reproduced in various parts such as in the editor, in the package explorer, project explorer and etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-663) Display.getClientArea() includes toolbar on Linux [EBZ#33659]

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-663?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-663: --------------------------------- Assignee: Eric Williams > Display.getClientArea() includes toolbar on Linux [EBZ#33659] > ------------------------------------------------------------- > > Key: ERT-663 > URL: https://issues.jboss.org/browse/ERT-663 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Labels: SWT, bzira > > 20030227 > The client area on Linux Motif also includes the toolbar whereas on other > playforms it doesn't. > STEPS > 1) Set you display to 1024 x 768 > 2) Execute Display.getClientArea() > 3) Value us 1024,768 > 4) Switch to XP > 5) Execute Display.getClientArea() > 6) Value us 1024,738 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018