June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20441) Explorer: As a user, I want to retrieve pod logs from the connection or project level

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20441?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20441: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Explorer: As a user, I want to retrieve pod logs from the connection or project level > ------------------------------------------------------------------------------------- > > Key: JBIDE-20441 > URL: https://issues.jboss.org/browse/JBIDE-20441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: explorer, help_wanted, openshift_v3 > Fix For: 4.5.x > > Original Estimate: 8 minutes > Remaining Estimate: 8 minutes > > Allow users to right-click on a project or connection and be presented with a wizard that allows them to select their pod or build to get logs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20513: ------------------------------------- Labels: connection openshift_v3 (was: openshift_v3) > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Labels: connection, openshift_v3 > Fix For: 4.5.x > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4428) EAP does not enforce having Java on Mac

by Jan Richter (JIRA)

Jan Richter created JBDS-4428: --------------------------------- Summary: EAP does not enforce having Java on Mac Key: JBDS-4428 URL: https://issues.jboss.org/browse/JBDS-4428 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 11.0.0.AM1 Reporter: Jan Richter Assignee: Jan Richter Fix For: 11.0.0.AM2 If you don't have Java on macOS and select just EAP in devsuite installer, it lets you continue even though it can't really install Java on its own. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20513: ------------------------------------- Labels: openshift_v3 (was: ) > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Labels: openshift_v3 > Fix For: 4.5.x > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20513: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Labels: openshift_v3 > Fix For: 4.5.x > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4428) EAP does not enforce having Java on Mac

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4428?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4428: ------------------------------ Story Points: 3 Sprint: devex #133 Jun 2018 > EAP does not enforce having Java on Mac > --------------------------------------- > > Key: JBDS-4428 > URL: https://issues.jboss.org/browse/JBDS-4428 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > If you don't have Java on macOS and select just EAP in devsuite installer, it lets you continue even though it can't really install Java on its own. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20563) Connection wizard: Configure non default console url for OpenShift 3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20563?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20563: ------------------------------------- Summary: Connection wizard: Configure non default console url for OpenShift 3 connections (was: Configure non default console url for OpenShift 3 connections) > Connection wizard: Configure non default console url for OpenShift 3 connections > -------------------------------------------------------------------------------- > > Key: JBIDE-20563 > URL: https://issues.jboss.org/browse/JBIDE-20563 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > > As a follow up on JBIDE-20502, the web console url doesn't necessarily match the connection URL (as in server.url+'/console'). > We should add an advanced section in the connection wizard, so that users can override the default web console url. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20563) Connection wizard: Configure non default console url for OpenShift 3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20563?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20563: ------------------------------------- Labels: connection_wizard openshift_v3 (was: ) > Connection wizard: Configure non default console url for OpenShift 3 connections > -------------------------------------------------------------------------------- > > Key: JBIDE-20563 > URL: https://issues.jboss.org/browse/JBIDE-20563 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > > As a follow up on JBIDE-20502, the web console url doesn't necessarily match the connection URL (as in server.url+'/console'). > We should add an advanced section in the connection wizard, so that users can override the default web console url. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20573) OpenShift Explorer: decorate project showing last build/deployment failed/succeeded

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20573?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20573: ------------------------------------- Labels: explorer openshift_v3 (was: ) > OpenShift Explorer: decorate project showing last build/deployment failed/succeeded > ----------------------------------------------------------------------------------- > > Key: JBIDE-20573 > URL: https://issues.jboss.org/browse/JBIDE-20573 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.5.0.AM2 > > > As reported by [~sspeiche] (or was it [~crobson]?), it'd be nice to have a visual clue of a project state, in the OpenShift Explorer. We should display the last pod status (build failed or deployment succeeded) next to a project's node -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20570) OpenShift Explorer: needs an "Expand All" button

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20570?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20570: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > OpenShift Explorer: needs an "Expand All" button > ------------------------------------------------ > > Key: JBIDE-20570 > URL: https://issues.jboss.org/browse/JBIDE-20570 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.5.x > > > OpenShift Explorer displays collapsed resources by default. Having to expand resources manually one by one is annoying, as reported by [~sspeiche]. It'd be better to have an Expand All button next to the Collapse All one in the explorer. > Or it might make sense to be able to expand all from a particular node -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 2017