[JBoss JIRA] (JBIDE-10512) Explorer: Delete server and disconnect GIT when deleting OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10512?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10512:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Explorer: Delete server and disconnect GIT when deleting OpenShift application
> ------------------------------------------------------------------------------
>
> Key: JBIDE-10512
> URL: https://issues.jboss.org/browse/JBIDE-10512
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Lucia Jelinkova
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
>
> # EXEC: create a new OpenShift Application and import it to your workspace (have the server adapter created)
> # EXEC: in the OpenShift Explorer: delete the application
> Variant:
> # EXEC: force delete the domain (and have all apps deleted with it)
> Result:
> The server adapter and the project (with git repository) are still there. We should delete the server adapter and remove the remote from the git repository of the project
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-10512) Explorer: Delete server and disconnect GIT when deleting OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10512?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10512:
-------------------------------------
Estimated Difficulty: Medium
> Explorer: Delete server and disconnect GIT when deleting OpenShift application
> ------------------------------------------------------------------------------
>
> Key: JBIDE-10512
> URL: https://issues.jboss.org/browse/JBIDE-10512
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Lucia Jelinkova
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
>
> # EXEC: create a new OpenShift Application and import it to your workspace (have the server adapter created)
> # EXEC: in the OpenShift Explorer: delete the application
> Variant:
> # EXEC: force delete the domain (and have all apps deleted with it)
> Result:
> The server adapter and the project (with git repository) are still there. We should delete the server adapter and remove the remote from the git repository of the project
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16108) Preferences: Timeout preferences should not set system properties but operation specific timeout
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16108?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16108:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Preferences: Timeout preferences should not set system properties but operation specific timeout
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16108
> URL: https://issues.jboss.org/browse/JBIDE-16108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Labels: preferences
> Fix For: 4.2.x
>
>
> In JBIDE-16046 we introduced an Eclipse Preferences to set the openshift-java-clilent timeouts. These preferences currently set the lib specific system property which is not good. Consider the following usecase:
> 1) User launches Eclipse and has system property set to 10000 (-D): Eclipse Preferences display 10000
> 2) User sets preference to 1234
> 3) restarts Ecllipse: Preferences display 1234
> 3) happens because we load the value from eclipse preferences and override the system property
> We should keep both separate: System property and Eclipse preferences:
> We use operation specific timeouts in all Eclipse code and make the Eclipse preferences provide some value for this. Leaving the system property alone.
> We should also:
> * add a checkbox for "[ ] use default"
> * change openshift-java-client to differentiate "no value" (<0) and value set (>=0)
> * remove current hard-coded safe default in openshift-java-client, replace it by system-property we already have).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15931) Explorer: Useless menu items on multiple application selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15931?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15931:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Explorer: Useless menu items on multiple application selection
> --------------------------------------------------------------
>
> Key: JBIDE-15931
> URL: https://issues.jboss.org/browse/JBIDE-15931
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
> Attachments: menu_items.png
>
>
> There are 2 useless menu items in context menu of the multiple application selection. See attached image.
> It is useless to have menu item to display details about application, also server adapter is 1 to 1 relation application:adapter, so this is I think useless too. Also those menu items are disabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15931) Explorer: Useless menu items on multiple application selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15931?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15931:
-------------------------------------
Estimated Difficulty: Low
> Explorer: Useless menu items on multiple application selection
> --------------------------------------------------------------
>
> Key: JBIDE-15931
> URL: https://issues.jboss.org/browse/JBIDE-15931
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
> Attachments: menu_items.png
>
>
> There are 2 useless menu items in context menu of the multiple application selection. See attached image.
> It is useless to have menu item to display details about application, also server adapter is 1 to 1 relation application:adapter, so this is I think useless too. Also those menu items are disabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16129:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: env_var_wizard
> Fix For: 4.2.x
>
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16129:
-------------------------------------
Estimated Difficulty: Low
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: env_var_wizard
> Fix For: 4.2.x
>
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months