[JBoss JIRA] (JBIDE-22420) Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22420?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22420.
---------------------------------
Verified in devstudio with build id: Alpha3-v20160531-0503-B5474.
> Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22420
> URL: https://issues.jboss.org/browse/JBIDE-22420
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> If I select a template in New OpenShift Application wizard, the Finish button is enabled and it is possible to skip all wizard pages and have created an application. If I select a builder image in the wizard, Finish is disabled (although on the next wizard page it gets enabled even I do not set any other value manually). But having selecting a template at first in the wizard and then selecting a build image, Finish button is still enabled. Click on the button cause NPE with following stack trace:
> {code}Unable to create resources to deploy image null
> java.lang.IllegalArgumentException: newValue is null
> at org.jboss.dmr.ModelNode.set(ModelNode.java:499)
> at com.openshift.internal.restclient.model.Service.setSelector(Service.java:115)
> at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.stubService(DeployImageJob.java:254)
> at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.generateResources(DeployImageJob.java:150)
> at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.doRun(DeployImageJob.java:99)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBDS-3874) Rename default install folder to match the new branding
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3874?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3874.
-----------------------------
As per the last build, we got developer-studio folder => verfied.
> Rename default install folder to match the new branding
> -------------------------------------------------------
>
> Key: JBDS-3874
> URL: https://issues.jboss.org/browse/JBDS-3874
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.Alpha2
>
>
> Since we are no longer calling devstudio anything begining with 'j' (i.e. jboss devstudio, jbds, etc.) it would be nice to rename the default installation folder from 'jbdevstudio' to something more consistent with the new branding, like 'devstudio'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBIDE-22413) Connection Editor: dont launch further jobs if editor is already closed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22413?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22413.
---------------------------------
Verified in devstudio with build id: Alpha3-v20160531-0503-B5474.
> Connection Editor: dont launch further jobs if editor is already closed
> -----------------------------------------------------------------------
>
> Key: JBIDE-22413
> URL: https://issues.jboss.org/browse/JBIDE-22413
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha3
>
>
> ASSERT: make sure that you have a server adapter
> EXEC: open it in the server editor
> ASSERT: the widgets in the openshift section are disabled, in the status bar (or progress view) you see a job "Loading projects..." running
> EXEC: close the editor
> ASSERT: nothing happens so far, but you see another job running "Setting connection, deploy..."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22165.
---------------------------------
Verified in devstudio with build id: Alpha3-v20160531-0503-B5474.
> Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22165
> URL: https://issues.jboss.org/browse/JBIDE-22165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Thomas Mäder
> Labels: deploy_docker_wizard, docker, openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBIDE-22247) Reorganize context menus of OpenShift Resources in properties view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22247?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22247.
---------------------------------
Verified in devstudio with build id: Alpha3-v20160531-0503-B5474.
> Reorganize context menus of OpenShift Resources in properties view
> ------------------------------------------------------------------
>
> Key: JBIDE-22247
> URL: https://issues.jboss.org/browse/JBIDE-22247
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, properties, ux
> Fix For: 4.4.0.Alpha3
>
> Attachments: bc_cm.png, build_cm.png, dc_cm.png, pod_cm.png, rc_cm.png, route_cm.png, service_cm.png
>
>
> Context menus of OpenShift resources in Properties view are quite messy. It could be ordered better. For reference check Eclipse guidelines on context menus of objects in views https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2
> See screenshots of context menus
> *Build config*
> !bc_cm.png!
> *Build*
> !build_cm.png!
> *Deployment Config*
> !dc_cm.png!
> *Pod*
> !pod_cm.png!
> *Service*
> !service_cm.png!
> *Route*
> !route_cm.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months