[JBoss JIRA] (JBIDE-17985) Create Domain wizard: should be able to edit domain members within Eclipse
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17985?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-17985.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Create Domain wizard: should be able to edit domain members within Eclipse
> --------------------------------------------------------------------------
>
> Key: JBIDE-17985
> URL: https://issues.jboss.org/browse/JBIDE-17985
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Andre Dietisheim
> Labels: domain_wizard, uxtest
> Fix For: LATER
>
> Attachments: OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
>
>
> Suggest that we change the create domain dialog to do the following:
> 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
> !OpenshiftDomainCreation_Step1.png!
> 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
> !OpenshiftDomainCreation_Step2.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17974) Add contextual help to OpenShift modals
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17974?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-17974.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Add contextual help to OpenShift modals
> ---------------------------------------
>
> Key: JBIDE-17974
> URL: https://issues.jboss.org/browse/JBIDE-17974
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: uxtest
> Fix For: LATER
>
>
> Many of the openshift modals do not provide contextual help that JBDS users expect throughout the application.
> Create OpenShift Application modal:
> Help button/Icon provided in bottom left of modal. Upon clicking, the help panel does not actually provide anything that helps the user understand what they need to do with the various screens throughout this wizard.
> https://www.evernote.com/shard/s230/sh/3c712331-988c-4531-9b3b-b706973a9f...
> The following OpenShift related dialogs do not provide a help icon/button at all and probably should:
> - Configure OpenShift Markers (right click project -> OpenShift -> Configure Markers...)
> - Domains (OpenShift Explorer pane -> right click OpenShift account -> Manage domains...)
> - SSH Keys (OpenShift Explorer pane -> right click OpenShift account -> Manage SSH keys...)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18007) Server adapter: Incorrect error message when deleting application via server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18007.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Server adapter: Incorrect error message when deleting application via server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Fix For: LATER
>
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also a project in workspace. But I think this is not desired solution, bcs. user would want to work with his project later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18082) Application wizard, Connection wizard: Last used connection from explorer is not preselected
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18082?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18082.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard, Connection wizard: Last used connection from explorer is not preselected
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18082
> URL: https://issues.jboss.org/browse/JBIDE-18082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, connection_wizard
> Fix For: LATER
>
>
> In JBIDE-17568 was implemented preselection of last used connection via menu File - New - OpenShift Application. But preselection of last used connection from OpenShift explorer is not working (probably has not been implemented yet).
> We should provide preselection also for last used connection via OpenShift explorer. Preselection via Menu now works like this:
> User has lets say 2 connections. If he opens New Application wizard via menu File - New - OpenShift Application, then first connection is preselected. He chooses second connection in opened New Application wizard (on the first page containing credentials), clicks Next button and then user clicks Cancel. Then user open New application wizard via menu File - New - OpenShift application again and second connection is preselected.
> Suggested solution for explorer:
> User has 2 connections and first one is used for preselection. User selects in OpenShift explorer second connection and opens New application wizard via context menu. After closing New application wizard shell (by its completion or canceling) user should get preselected second connection after opening a New Application wizard via menu File - New - OpenShift Application.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18037) Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18037.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18037
> URL: https://issues.jboss.org/browse/JBIDE-18037
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: connection_wizard, server_adapter_wizard
> Fix For: LATER
>
> Attachments: openshift_explorer.png, server_adapter_wizard.png
>
>
> When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS).
> !server_adapter_wizard.png!
> Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box.
> !openshift_explorer.png!
> There should be option to choose any connection and on the next wizard pages this connection could be preselected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18147) Port forwarding, Environment Variables: Port forwarding tears the SSH session down, harms environment variables
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18147?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18147.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Port forwarding, Environment Variables: Port forwarding tears the SSH session down, harms environment variables
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18147
> URL: https://issues.jboss.org/browse/JBIDE-18147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Fix For: LATER
>
>
> After starting and stopping port forwarding there happens something wrong with session / ssh calling. I found it in Environment variables shell after creating env. variable and clicking on Refresh button. Following error has shown in log and environment variable from table was not removed, although it should be (Refresh button update local environment variables to environment variable of an existing OpenShift application).
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eap"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:871)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:840)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:614)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:843)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:865)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18134) Port forwarding: Free ports should be used from range 49152–65535
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18134?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18134.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Port forwarding: Free ports should be used from range 49152–65535
> -----------------------------------------------------------------
>
> Key: JBIDE-18134
> URL: https://issues.jboss.org/browse/JBIDE-18134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
>
> Currently port forwarding use as free ports any port received via java client which is calling some RHC function to get a free port. There are many ports in those so-called free ports which are under range 49152–65535. This range is declared by IANA for dynamic, private... let's call them free ports.
> Problem could occur in case of getting a port number lesser than 49152 which is currently not in use, but it is registered and user could start a service using this port number. Then there could be a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use name that was provided
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18124.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Server adapter: Creating a new server adapter does not use name that was provided
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18124
> URL: https://issues.jboss.org/browse/JBIDE-18124
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: LATER
>
>
> While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months