May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to chaning connections

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19817: ---------------------------------------- Summary: Application wizard: v3 application wizard needs to be able to react to chaning connections Key: JBIDE-19817 URL: https://issues.jboss.org/browse/JBIDE-19817 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19759: ------------------------------------- Attachment: no-application-wizard.png > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 5/18/15 5:38 AM: ------------------------------------------------------------------- When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! was (Author: adietish): When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for v3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 5/18/15 5:38 AM: ------------------------------------------------------------------- When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for v3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! was (Author: adietish): When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19759: ------------------------------------------ When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-441) zip download on tools.jboss.org is earlyaccess but that is not mentioned

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-441: ----------------------------------------- Summary: zip download on tools.jboss.org is earlyaccess but that is not mentioned Key: JBTIS-441 URL: https://issues.jboss.org/browse/JBTIS-441 Project: JBoss Tools Integration Stack Issue Type: Bug Components: releng Reporter: Max Rydahl Andersen Looking at http://tools.jboss.org/downloads/devstudio_is/luna/8.0.1.GA.html#zips the downloadable zip is actually the earlyaccess versions and not the actual GA. Should there not be two zip to download here - one for the GA parts and another for earlyaccess ? And should the updatesite not be https://devstudio.jboss.com/updates/8.0 now that it is composited into this site ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19811) Refactor IConnection interface to support connection specific display formating

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19811?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19811: ------------------------------------- Fix Version/s: 4.3.x > Refactor IConnection interface to support connection specific display formating > ------------------------------------------------------------------------------- > > Key: JBIDE-19811 > URL: https://issues.jboss.org/browse/JBIDE-19811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Fix For: 4.3.x > > > Ultimately, IConnection should be oblivious to username and password since those are authentication specific. There are a few places where we should introduce a 'display' interface which each type can implement in order to remove the dependency of the common label provider on username and password -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-3434: -------------------------------------- Assignee: Jeff Cantrill (was: Andre Dietisheim) > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Charles Moulliard > Assignee: Jeff Cantrill > Fix For: 9.0.x > > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3434: ----------------------------------- Fix Version/s: 9.0.x > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Charles Moulliard > Assignee: Jeff Cantrill > Fix For: 9.0.x > > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3434: ----------------------------------- Affects Version/s: 8.x > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Charles Moulliard > Assignee: Jeff Cantrill > Fix For: 9.0.x > > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 May 2015