June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20763) Provide 'oc' binaries per platform

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20763: ------------------------------------------ The installer that we provide now also installs the cdk which has a compatible ocp included as pointed out in JBIDE-24236. > Provide 'oc' binaries per platform > ---------------------------------- > > Key: JBIDE-20763 > URL: https://issues.jboss.org/browse/JBIDE-20763 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: oc_binary, preferences > Fix For: 4.5.0.AM1 > > > Instead of forcing the user to search, download and install the 'oc' library manually before being able to use port forwarding or log streaming, the platform-related binary could be installed automatically. > Possible implementation: > - define the oc binary URLs in stacks.yaml > - on openshift 3 plugin startup, check if oc binary is set in preferences > - if not set trigger background job to d/l oc binary matching current platform, and update preferences, else, do nothing. > [~maxandersen] does it correspond to what you had in mind? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24236: ------------------------------------- Summary: Preferences: "automagically" use the oc that's shipped with the cdk3 (was: Preferences: "automagically" link to the oc that's shipped with the cdk3) > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.AM2 > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" link to the oc that's shipped with the cdk3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24236: ------------------------------------- Summary: Preferences: "automagically" link to the oc that's shipped with the cdk3 (was: cdk3 oc command) > Preferences: "automagically" link to the oc that's shipped with the cdk3 > ------------------------------------------------------------------------ > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.AM2 > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) cdk3 oc command

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24236: ------------------------------------- Labels: oc_binary openshift_v3 (was: ) > cdk3 oc command > --------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.AM2 > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20911: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Labels: oc_binary > Fix For: 4.5.x > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin> --server=<serverurl>` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20911: ------------------------------------- Labels: oc_binary (was: ) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Labels: oc_binary > Fix For: 4.5.x > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin> --server=<serverurl>` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20763) Provide 'oc' binaries per platform

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20763: ------------------------------------- Labels: oc_binary preferences (was: ) > Provide 'oc' binaries per platform > ---------------------------------- > > Key: JBIDE-20763 > URL: https://issues.jboss.org/browse/JBIDE-20763 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: oc_binary, preferences > Fix For: 4.5.0.AM1 > > > Instead of forcing the user to search, download and install the 'oc' library manually before being able to use port forwarding or log streaming, the platform-related binary could be installed automatically. > Possible implementation: > - define the oc binary URLs in stacks.yaml > - on openshift 3 plugin startup, check if oc binary is set in preferences > - if not set trigger background job to d/l oc binary matching current platform, and update preferences, else, do nothing. > [~maxandersen] does it correspond to what you had in mind? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21156) Remove LazySSLCertificateCallback and LazyCredentialsPrompter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21156?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21156: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Remove LazySSLCertificateCallback and LazyCredentialsPrompter > ------------------------------------------------------------- > > Key: JBIDE-21156 > URL: https://issues.jboss.org/browse/JBIDE-21156 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > > In JBIDE-21153 we introduced extension points that openshift.core can reach out to in order to present UI elements. We thus theoretically dont need the lazy loading patterns for those that were used when there were no extension points yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20972: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21191) Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21191?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21191: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-21191 > URL: https://issues.jboss.org/browse/JBIDE-21191 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1, 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.5.x > > > In JBIDE-21072 we applied a workaround to fix an SWT bug where controls are not visible but appear magically if you resize the dialog: https://bugs.eclipse.org/bugs/show_bug.cgi?id=465280 > We should remove this workaround once the fix makes it to SWT in upstream -- 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