December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-10512) Explorer: Delete server and disconnect GIT when deleting OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10512?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10512: ------------------------------------- Summary: Explorer: Delete server and disconnect GIT when deleting OpenShift application (was: Delete server and disconnect GIT when deleting OpenShift application) > Explorer: Delete server and disconnect GIT when deleting OpenShift application > ------------------------------------------------------------------------------ > > Key: JBIDE-10512 > URL: https://issues.jboss.org/browse/JBIDE-10512 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Lucia Jelinkova > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > # EXEC: create a new OpenShift Application and import it to your workspace (have the server adapter created) > # EXEC: in the OpenShift Explorer: delete the application > Variant: > # EXEC: force delete the domain (and have all apps deleted with it) > Result: > The server adapter and the project (with git repository) are still there. We should delete the server adapter and remove the remote from the git repository of the project -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13145) Server Adapter: Cannot "Tail files" if I remove connection from OpenShift Explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13145?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13145: ------------------------------------- Summary: Server Adapter: Cannot "Tail files" if I remove connection from OpenShift Explorer (was: OpenShift Server Adapter: Cannot "Tail files" if I remove connection from OpenShift Explorer) > Server Adapter: Cannot "Tail files" if I remove connection from OpenShift Explorer > ---------------------------------------------------------------------------------- > > Key: JBIDE-13145 > URL: https://issues.jboss.org/browse/JBIDE-13145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10263) Application wizard: Warn if quota is reached, no further apps may get created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10263: ------------------------------------- Summary: Application wizard: Warn if quota is reached, no further apps may get created (was: Warn about App creation when quota is reached) > Application wizard: Warn if quota is reached, no further apps may get created > ----------------------------------------------------------------------------- > > Key: JBIDE-10263 > URL: https://issues.jboss.org/browse/JBIDE-10263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: error-application-quota-reached.png > > > The 'new' button should be disabled when the account already has 5 applications and a message should inform the user that he as reached his quota. > Otherwise, Openshift responds with a 400 error when the user finished his app creation :-( -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10263) Application wizard: Warn if quota is reached, no further apps may get created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10263?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10263: ------------------------------------------ This is a very old jira, the text is referring to the initial implementation of our tooling. Nevertheless this is still valid. > Application wizard: Warn if quota is reached, no further apps may get created > ----------------------------------------------------------------------------- > > Key: JBIDE-10263 > URL: https://issues.jboss.org/browse/JBIDE-10263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: error-application-quota-reached.png > > > The 'new' button should be disabled when the account already has 5 applications and a message should inform the user that he as reached his quota. > Otherwise, Openshift responds with a 400 error when the user finished his app creation :-( -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11288) Application wizard: Investigate name exceptions of OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11288: ------------------------------------------ set fixVersion to LATER since it's very unlikely that we'll have time for this. > Application wizard: Investigate name exceptions of OpenShift Application > ------------------------------------------------------------------------ > > Key: JBIDE-11288 > URL: https://issues.jboss.org/browse/JBIDE-11288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > We should find out which names can be used as OpenShift Application name. > I've encountered a problem trying to create aplication called "*richfaces*": > Could not create application "richfaces": The supplied application name 'richfaces' is not allowed > Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" > After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11288) Application wizard: Investigate name exceptions of OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11288: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > Application wizard: Investigate name exceptions of OpenShift Application > ------------------------------------------------------------------------ > > Key: JBIDE-11288 > URL: https://issues.jboss.org/browse/JBIDE-11288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > We should find out which names can be used as OpenShift Application name. > I've encountered a problem trying to create aplication called "*richfaces*": > Could not create application "richfaces": The supplied application name 'richfaces' is not allowed > Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" > After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11288) Application wizard: Investigate name exceptions of OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11288: ------------------------------------- Summary: Application wizard: Investigate name exceptions of OpenShift Application (was: Investigate name exceptions of OpenShift Application) > Application wizard: Investigate name exceptions of OpenShift Application > ------------------------------------------------------------------------ > > Key: JBIDE-11288 > URL: https://issues.jboss.org/browse/JBIDE-11288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > We should find out which names can be used as OpenShift Application name. > I've encountered a problem trying to create aplication called "*richfaces*": > Could not create application "richfaces": The supplied application name 'richfaces' is not allowed > Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" > After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11279) Application wizard: Delete git folder (that was used to clone to) if import fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11279: ------------------------------------- Summary: Application wizard: Delete git folder (that was used to clone to) if import fails (was: Delete git folder (that was used to clone to) if import fails) > Application wizard: Delete git folder (that was used to clone to) if import fails > --------------------------------------------------------------------------------- > > Key: JBIDE-11279 > URL: https://issues.jboss.org/browse/JBIDE-11279 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: image.png > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11288) Application wizard: Investigate name exceptions of OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11288: ------------------------------------- Priority: Minor (was: Major) > Application wizard: Investigate name exceptions of OpenShift Application > ------------------------------------------------------------------------ > > Key: JBIDE-11288 > URL: https://issues.jboss.org/browse/JBIDE-11288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > We should find out which names can be used as OpenShift Application name. > I've encountered a problem trying to create aplication called "*richfaces*": > Could not create application "richfaces": The supplied application name 'richfaces' is not allowed > Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" > After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11270) Server editor: Remote branch to use should be a text-field with autocomplete

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11270?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11270: ------------------------------------------ set fixVersion to LATER since it's very unlikely that we'll have time for this. > Server editor: Remote branch to use should be a text-field with autocomplete > ---------------------------------------------------------------------------- > > Key: JBIDE-11270 > URL: https://issues.jboss.org/browse/JBIDE-11270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: egit-remote-branches.png, remote-disabled.png, server_detail.jpg > > > When you open the detail of OpenShift server adapter you can change the Git remote name by typing the new value. Could you change the text field to combo box filled with remote names that are actually configured for the OpenShift project? > !server_detail.jpg! > We decided to match what EGit provides: a text-field which allows freely typed entries (which would create new branches) but also offers auto-completion to match existing branches. > !egit-remote-branches.png! -- 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

12 years, 4 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 December 2013