[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22051:
------------------------------------------
We did not have enough time to tackle this for 4.4.2.AM3. In the next sprint we'll only be able to do bugfixing. Moving this to 4.4.x
> Redesing route prompting in server adapter wizard, show in browser etc.
> -----------------------------------------------------------------------
>
> Key: JBIDE-22051
> URL: https://issues.jboss.org/browse/JBIDE-22051
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.x
>
>
> We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser.
> According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22051:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.4.2.AM3)
> Redesing route prompting in server adapter wizard, show in browser etc.
> -----------------------------------------------------------------------
>
> Key: JBIDE-22051
> URL: https://issues.jboss.org/browse/JBIDE-22051
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.x
>
>
> We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser.
> According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22051:
-------------------------------------
Sprint: (was: devex #122 October 2016)
> Redesing route prompting in server adapter wizard, show in browser etc.
> -----------------------------------------------------------------------
>
> Key: JBIDE-22051
> URL: https://issues.jboss.org/browse/JBIDE-22051
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.x
>
>
> We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser.
> According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23069:
-------------------------------------
Sprint: (was: devex #123 November 2016)
> Server adapter wizard: Importing of project should skip Select Build Config wizard page
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23069
> URL: https://issues.jboss.org/browse/JBIDE-23069
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.x
>
>
> This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23069:
------------------------------------------
in the next sprint we'll only be able to do bugfixing. Moving this to 4.4.x
> Server adapter wizard: Importing of project should skip Select Build Config wizard page
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23069
> URL: https://issues.jboss.org/browse/JBIDE-23069
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.x
>
>
> This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23069 at 11/4/16 6:20 AM:
-------------------------------------------------------------------
We did not have enough time to tackle this for 4.4.2.AM3. In the next sprint we'll only be able to do bugfixing. Moving this to 4.4.x
was (Author: adietish):
in the next sprint we'll only be able to do bugfixing. Moving this to 4.4.x
> Server adapter wizard: Importing of project should skip Select Build Config wizard page
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23069
> URL: https://issues.jboss.org/browse/JBIDE-23069
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.x
>
>
> This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23069:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.4.2.AM3)
> Server adapter wizard: Importing of project should skip Select Build Config wizard page
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23069
> URL: https://issues.jboss.org/browse/JBIDE-23069
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.x
>
>
> This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23069:
-------------------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> Server adapter wizard: Importing of project should skip Select Build Config wizard page
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23069
> URL: https://issues.jboss.org/browse/JBIDE-23069
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.x
>
>
> This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Build pod has state of exit code 0 instead of correct status completed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23463:
----------------------------------
Description: When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. (was: When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.)
> Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months