[JBoss JIRA] (JBIDE-14323) Maven Update Project should be hotkey bindable
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-14323:
-----------------------------------------
I agree with Andrew. That should be done in background or at least an option should be provided to enable/disable that feature
> Maven Update Project should be hotkey bindable
> ----------------------------------------------
>
> Key: JBIDE-14323
> URL: https://issues.jboss.org/browse/JBIDE-14323
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Lincoln Baxter III
>
> Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;)
--
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
13 years
[JBoss JIRA] (JBIDE-14323) Maven Update Project should be hotkey bindable
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ]
Lincoln Baxter III commented on JBIDE-14323:
--------------------------------------------
Max, I think that CTRL-1 only works if you are focused on the PROBLEMS or MARKERS views. So still requires mousing.
> Maven Update Project should be hotkey bindable
> ----------------------------------------------
>
> Key: JBIDE-14323
> URL: https://issues.jboss.org/browse/JBIDE-14323
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Lincoln Baxter III
>
> Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;)
--
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
13 years
[JBoss JIRA] (JBIDE-14324) OpenShift Application Wizard: connection that you use to import/create should get set as most recent connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14324:
-------------------------------------
Summary: OpenShift Application Wizard: connection that you use to import/create should get set as most recent connection (was: OpenShift Application Wizard: Connection that you use to import/create should get set as most recent connection)
> OpenShift Application Wizard: connection that you use to import/create should get set as most recent connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14324
> URL: https://issues.jboss.org/browse/JBIDE-14324
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
>
> How to reproduce:
> # ASSERT: make sure you have at least 2 connections in OpenShift Explorer
> # EXEC: launch import/create application wizard and switch the preselected connection in the connection dialog
> # EXEC: import/create some OpenShift application
> # ASSERT: import/create works successfully
> # ASSERT: make sure no connection is selected in OpenShift Explorer (ctrl + click deselects)
> # EXEC: hit *Connect to OpenShift* in OpenShift Explorer toolbar
> Result:
> The connection that was preselected before executing your import/create is still the connection that's being preselected
> Expected result:
> Once you successfully import/create an application the connection that you used should get preselected.
--
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
13 years
[JBoss JIRA] (JBIDE-14324) OpenShift Application Wizard: Connection that you use to import/create should get set as most recent connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14324:
------------------------------------------
The connection dialog behaves in the following way:
* you have *no connection selected* in the OpenShift Explorer:
The most recently created/edited connection is preselected in the combo
* you have *a connection selected* in the OpenShift Explorer:
The selected connection is preselected in the combo
With the fix for this issue the preselected connection should also change once you successfully import/create some application.
> OpenShift Application Wizard: Connection that you use to import/create should get set as most recent connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14324
> URL: https://issues.jboss.org/browse/JBIDE-14324
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
>
> How to reproduce:
> # ASSERT: make sure you have at least 2 connections in OpenShift Explorer
> # EXEC: launch import/create application wizard and switch the preselected connection in the connection dialog
> # EXEC: import/create some OpenShift application
> # ASSERT: import/create works successfully
> # ASSERT: make sure no connection is selected in OpenShift Explorer (ctrl + click deselects)
> # EXEC: hit *Connect to OpenShift* in OpenShift Explorer toolbar
> Result:
> The connection that was preselected before executing your import/create is still the connection that's being preselected
> Expected result:
> Once you successfully import/create an application the connection that you used should get preselected.
--
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
13 years
[JBoss JIRA] (JBIDE-14323) Maven Update Project should be hotkey bindable
by Andrew Rubinger (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ]
Andrew Rubinger commented on JBIDE-14323:
-----------------------------------------
Or better...if the IDE can detect when you need to "Update Maven Project..." - why doesn't it just DO it? This is similar to the project structure refresh problem that used to be in Eclipse before they (thankfully) corrected this.
> Maven Update Project should be hotkey bindable
> ----------------------------------------------
>
> Key: JBIDE-14323
> URL: https://issues.jboss.org/browse/JBIDE-14323
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Lincoln Baxter III
>
> Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;)
--
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
13 years
[JBoss JIRA] (JBIDE-14324) OpenShift Application Wizard: Connection that you use to import/create should get set as most recent connection
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14324:
----------------------------------------
Summary: OpenShift Application Wizard: Connection that you use to import/create should get set as most recent connection
Key: JBIDE-14324
URL: https://issues.jboss.org/browse/JBIDE-14324
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta1
How to reproduce:
# ASSERT: make sure you have at least 2 connections in OpenShift Explorer
# EXEC: launch import/create application wizard and switch the preselected connection in the connection dialog
# EXEC: import/create some OpenShift application
# ASSERT: import/create works successfully
# ASSERT: make sure no connection is selected in OpenShift Explorer (ctrl + click deselects)
# EXEC: hit *Connect to OpenShift* in OpenShift Explorer toolbar
Result:
The connection that was preselected before executing your import/create is still the connection that's being preselected
Expected result:
Once you successfully import/create an application the connection that you used should get preselected.
--
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
13 years