[JBoss JIRA] (JBIDE-18409) OpenShift Adapter: Add choice to show application in external device/browser
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18409?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18409:
-------------------------------------
Comment: was deleted
(was: setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3.)
> OpenShift Adapter: Add choice to show application in external device/browser
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18409
> URL: https://issues.jboss.org/browse/JBIDE-18409
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Joao Viragine
> Labels: openshift_v2, openshift_v3, server_adapter
> Fix For: 4.4.x
>
>
> It would be nice if we had the option: Show In/Web Browser on External Device for OpenShift Server as we have for JBoss EAP Server. (Servers/(Application)/Show In/Add Web Browser on External Device)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18665:
-------------------------------------
Labels: application_wizard openshift_v2 (was: application_wizard)
> Application wizard: Should not use project-name as application name if it's invalid, should sanitze it
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18665
> URL: https://issues.jboss.org/browse/JBIDE-18665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR2
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard, openshift_v2
> Fix For: LATER
>
> Attachments: non-alphanumeric-application-name.png
>
>
> In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22371) Allow users easily manage environment variables of OpenShift application
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22371?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-22371:
------------------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.x)
> Allow users easily manage environment variables of OpenShift application
> ------------------------------------------------------------------------
>
> Key: JBIDE-22371
> URL: https://issues.jboss.org/browse/JBIDE-22371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> At the moment to add a new environment variable/edit an existing one. Environment variables are located at deployment configuration. At the moment it requires to open Properties view, select a deployment config, open context menu Edit... and find in json where the spot with env. vars is located and add more key:value pair or edit existing ones. It would be nice if we would have some dialog/wizard to easily manage variables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-15495) Server Adapter: publish locks the whole workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15495:
-------------------------------------
Labels: openshift_v2 server_adapter (was: server_adapter)
> Server Adapter: publish locks the whole workspace
> -------------------------------------------------
>
> Key: JBIDE-15495
> URL: https://issues.jboss.org/browse/JBIDE-15495
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Labels: openshift_v2, server_adapter
> Fix For: LATER
>
> Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png
>
>
> Have 2 projects in a workspace, one of them is an OpenShift application
> Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project.
> The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20716:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: connection_wizard)
> Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20716
> URL: https://issues.jboss.org/browse/JBIDE-20716
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked.
> We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months