January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12320) support protocol version 1.1 in openshift-java-client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12320: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > support protocol version 1.1 in openshift-java-client > ----------------------------------------------------- > > Key: JBIDE-12320 > URL: https://issues.jboss.org/browse/JBIDE-12320 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.x > > > the REST protocol that we use to talk to the OpenShift broker was bumped to 1.1 today. The change that triggers it is a change in the cartridges that you get reported when listing them on a application. We have to support protocol 1.1 for the openshift-java-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12321) handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12321?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12321: ------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) > handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1 > -------------------------------------------------------------------------------- > > Key: JBIDE-12321 > URL: https://issues.jboss.org/browse/JBIDE-12321 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: app-type-listed-as-embedded.png > > > In 1.1 the cartridges that you get reported when listing them on a application changed (IApplication#getEmbeddedCartridges): > * 1.0: > would report the embedded cartridges only > * 1.1: > would report the embedded cartridges and the application type (cartridge) > !app-type-listed-as-embedded.png! > see here: https://github.com/openshift/crankcase/pull/224 > The error that this caused was discussed here: > https://bugzilla.redhat.com/show_bug.cgi?id=838611 > OpenShift pushed the discussed change (application-type reported as embedded cartridge) to protocol v1.1 and fixed the issue on the server-side. Our client, that currently requests protocol v1.0 has no issue since the fix. We have to make sure we support protocol 1.1 and are able to handle this correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12724) openshift java client: remove various API elements (show ports etc.) in protocol 1.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12724?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12724: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > openshift java client: remove various API elements (show ports etc.) in protocol 1.1 > ------------------------------------------------------------------------------------ > > Key: JBIDE-12724 > URL: https://issues.jboss.org/browse/JBIDE-12724 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > upcoming changes for the REST service protocol 1.1 in OpenShift > {code:title=Mail from Krishan Raman on 09/26/2012} > I am planning to break 1.0 compatibility for some REST APIs which I think are not in use. Please correct me if this you are aware of some client which uses these APIs. > /rest/estimates/* > Estimates API was created for use by UI to calculate estimated number of gears used for a given app descriptor. > /rest/domains/#{dom_id}/applications/#{app_name}/events # show-port, expose-port, conceal-port > *port APIs were created for testing Rob's code. Not aware of anyone using them now. > /rest/domains/#{dom_id}/applications/#{app_name}/gears > gears API was in use by UI before gear-groups were exposed to get a list of gears in the application. Not aware of anyone using them now. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12724) openshift java client: remove various API elements (show ports etc.) in protocol 1.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12724?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12724: ------------------------------------- Priority: Minor (was: Major) > openshift java client: remove various API elements (show ports etc.) in protocol 1.1 > ------------------------------------------------------------------------------------ > > Key: JBIDE-12724 > URL: https://issues.jboss.org/browse/JBIDE-12724 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > > upcoming changes for the REST service protocol 1.1 in OpenShift > {code:title=Mail from Krishan Raman on 09/26/2012} > I am planning to break 1.0 compatibility for some REST APIs which I think are not in use. Please correct me if this you are aware of some client which uses these APIs. > /rest/estimates/* > Estimates API was created for use by UI to calculate estimated number of gears used for a given app descriptor. > /rest/domains/#{dom_id}/applications/#{app_name}/events # show-port, expose-port, conceal-port > *port APIs were created for testing Rob's code. Not aware of anyone using them now. > /rest/domains/#{dom_id}/applications/#{app_name}/gears > gears API was in use by UI before gear-groups were exposed to get a list of gears in the application. Not aware of anyone using them now. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12731) OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12731?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12731 at 1/10/13 8:43 AM: ------------------------------------------------------------------- This was fixed, the freshly used credentials show up in the OpenShift Explorer as soon as you hit *Next* in the application wizard. I dont know in which issue, I therefore set this to *Out of date* was (Author: adietish): This was fixed. I dont know in which issue, I therefore set this to *Out of date* > OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12731 > URL: https://issues.jboss.org/browse/JBIDE-12731 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha1 > > > How to reproduce: > # ASSERT: make sure you have an openshift user account that is not listed in the OpenShift Explorer > # EXEC: open up the OpenShift Explorer > # EXEC: in central, hit *OpenShift Application* > # EXEC: in the upcoming authentication dialog, provide your user (that is not listed in the explorer) and hit *Next* > Result: > # ASSERT: the user is not listed in the OpenShift explorer even though it was used and valid. > I think we should add this new user to the OpenShift explorer since it was used and proven to be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12731) OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12731?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12731. -------------------------------------- Resolution: Out of Date > OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12731 > URL: https://issues.jboss.org/browse/JBIDE-12731 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha1 > > > How to reproduce: > # ASSERT: make sure you have an openshift user account that is not listed in the OpenShift Explorer > # EXEC: open up the OpenShift Explorer > # EXEC: in central, hit *OpenShift Application* > # EXEC: in the upcoming authentication dialog, provide your user (that is not listed in the explorer) and hit *Next* > Result: > # ASSERT: the user is not listed in the OpenShift explorer even though it was used and valid. > I think we should add this new user to the OpenShift explorer since it was used and proven to be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12731) OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12731?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12731: ------------------------------------------ This was fixed. I dont know in which issue, I therefore set this to *Out of date* > OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12731 > URL: https://issues.jboss.org/browse/JBIDE-12731 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha1 > > > How to reproduce: > # ASSERT: make sure you have an openshift user account that is not listed in the OpenShift Explorer > # EXEC: open up the OpenShift Explorer > # EXEC: in central, hit *OpenShift Application* > # EXEC: in the upcoming authentication dialog, provide your user (that is not listed in the explorer) and hit *Next* > Result: > # ASSERT: the user is not listed in the OpenShift explorer even though it was used and valid. > I think we should add this new user to the OpenShift explorer since it was used and proven to be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12731) OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12731?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12731: ------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) > OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12731 > URL: https://issues.jboss.org/browse/JBIDE-12731 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha1 > > > How to reproduce: > # ASSERT: make sure you have an openshift user account that is not listed in the OpenShift Explorer > # EXEC: open up the OpenShift Explorer > # EXEC: in central, hit *OpenShift Application* > # EXEC: in the upcoming authentication dialog, provide your user (that is not listed in the explorer) and hit *Next* > Result: > # ASSERT: the user is not listed in the OpenShift explorer even though it was used and valid. > I think we should add this new user to the OpenShift explorer since it was used and proven to be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12738) OpenShift Explorer: Empty SSH wizard titles

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12738?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12738: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > OpenShift Explorer: Empty SSH wizard titles > ------------------------------------------- > > Key: JBIDE-12738 > URL: https://issues.jboss.org/browse/JBIDE-12738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: sshtitles.png > > > The wizard title should be set in these dialogs (will help QE in SWTBot tests and will look much better imho): > !sshtitles.png|thumbnail! > Accessible via OpenShift Explorer -> #1 Manage SSH Keys -> #2 New... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12749) SSH Typo in New OpenShift application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12749?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12749. -------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) Resolution: Out of Date > SSH Typo in New OpenShift application wizard > -------------------------------------------- > > Key: JBIDE-12749 > URL: https://issues.jboss.org/browse/JBIDE-12749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: corrected-message.png, sshtypo.png > > > !sshtypo.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 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 January 2013