September 2015 - jbosstools-issues

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

by Ben Parees (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Ben Parees commented on JBIDE-20763: ------------------------------------ by "oc's api" you mean the actual cli commands? they are definitely not as well protected as the api is. I think if you have specific commands you want to be able to make future assumptions about, we should discuss them on a case by case basis. Clayton Coleman needs to be included in that conversation. > 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 > > 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 (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19971: -------------------------------- Labels: openshift_v2 (was: ) > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v2 > Fix For: 4.3.x > > Attachments: authorized.png, creds_prompt.png, jstack.txt, krb5-auth-method-is-1st.png > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20766) Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20766?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20766: ----------------------------------- Assignee: Fred Bricon > Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch > ------------------------------------------------------------- > > Key: JBIDE-20766 > URL: https://issues.jboss.org/browse/JBIDE-20766 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Final > > > For jbosstools-openshift, ongoing work towards the JBoss Tools 4.3.1.Final release must happen on the jbosstools-4.3.1.x branch. > Once 4.3.0.Final has been released, the jbosstools-4.3.1.x branch must be merged into jbosstools-4.3.x branch, where subsequent commits will be pushed, until the 4.3.1.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20766) Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20766?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20766: -------------------------------- Fix Version/s: 4.3.1.Final > Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch > ------------------------------------------------------------- > > Key: JBIDE-20766 > URL: https://issues.jboss.org/browse/JBIDE-20766 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Final > > > For jbosstools-openshift, ongoing work towards the JBoss Tools 4.3.1.Final release must happen on the jbosstools-4.3.1.x branch. > Once 4.3.0.Final has been released, the jbosstools-4.3.1.x branch must be merged into jbosstools-4.3.x branch, where subsequent commits will be pushed, until the 4.3.1.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20766) Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20766: ----------------------------------- Summary: Merge jbosstools-4.3.1.x branch into jbosstools-4.3.x branch Key: JBIDE-20766 URL: https://issues.jboss.org/browse/JBIDE-20766 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.3.1.Final Reporter: Fred Bricon Priority: Blocker For jbosstools-openshift, ongoing work towards the JBoss Tools 4.3.1.Final release must happen on the jbosstools-4.3.1.x branch. Once 4.3.0.Final has been released, the jbosstools-4.3.1.x branch must be merged into jbosstools-4.3.x branch, where subsequent commits will be pushed, until the 4.3.1.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-20763 at 9/22/15 4:48 PM: -------------------------------------------------------------- The question of compatibility can probably be answered by [~jcantrill] or [~bparees] was (Author: fbricon): The question of compatibility can probably answered by [~jcantrill] or [~bparees] > 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 > > 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 (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20763: ------------------------------------- The question of compatibility can probably answered by [~jcantrill] or [~bparees] > 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 > > 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 (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20764: --------------------------------------------- The key aspect is having Run As...working and have it show up the right webpage. In addition Debug could ensure the righit portforwarding is done and the oc instance gets started with right flags to enable debug > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20763: --------------------------------------------- that or wrap oc in a p2 installable unit and download it when need be. btw. a side issue for this is how we ensure 'oc's 'api' that we rely on won't change or how we handle mulitple versions of it. is oc's api well-defined/guaranteed like the client api ? > 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 > > 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 (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20765: ----------------------------------- Assignee: Mickael Istria > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Fix For: 4.3.1.Final > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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 September 2015