[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13384:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
> Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13384
> URL: https://issues.jboss.org/browse/JBIDE-13384
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 3.3.2.Final
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
>
> This issue should find solution to this situation:
> * create application on openshift, then binary deployed another app to it
> * delete the server adapter
> * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically?
> Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO.
--
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, 4 months
[JBoss JIRA] (JBIDE-13106) Tail files: Change icon and tooltip for "close console" to better show difference to closing view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13106:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
> Tail files: Change icon and tooltip for "close console" to better show difference to closing view
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13106
> URL: https://issues.jboss.org/browse/JBIDE-13106
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
> Attachments: different-close-actions.png
>
>
> The Server Log console has 2 distinct actions that are labeled "close console".
> !different-close-actions.png!
> 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation
> 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern.
> We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things.
--
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, 4 months
[JBoss JIRA] (JBIDE-13352) Should be able to remove cartridge with "Remove" in the context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13352:
-------------------------------------
Priority: Minor (was: Major)
> Should be able to remove cartridge with "Remove" in the context menu
> --------------------------------------------------------------------
>
> Key: JBIDE-13352
> URL: https://issues.jboss.org/browse/JBIDE-13352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: remove-embedded-cartridge.png
>
>
> If you have a cartridge embedded to your application you'll see it listed as node below your application:
> !remove-embedded-cartridge.png!
> To remove it, you'll have to select your application and pick "Edit embedded cartridges...". It would be far more intuititive if we'd provide a "Remove" item in the context menu of the cartridge.
--
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, 4 months
[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating OpenShift Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13384:
-------------------------------------
Summary: Server Adapter wizard: Detect binary deployed application in workspace when creating OpenShift Server Adapter (was: Detect binary deployed application in workspace when creating OpenShift Server Adapter)
> Server Adapter wizard: Detect binary deployed application in workspace when creating OpenShift Server Adapter
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13384
> URL: https://issues.jboss.org/browse/JBIDE-13384
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 3.3.2.Final
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
>
> This issue should find solution to this situation:
> * create application on openshift, then binary deployed another app to it
> * delete the server adapter
> * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically?
> Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO.
--
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, 4 months
[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter (for existing app)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13384:
-------------------------------------
Summary: Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter (for existing app) (was: Server Adapter wizard: Detect binary deployed application in workspace when creating OpenShift Server Adapter)
> Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter (for existing app)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13384
> URL: https://issues.jboss.org/browse/JBIDE-13384
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 3.3.2.Final
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
>
> This issue should find solution to this situation:
> * create application on openshift, then binary deployed another app to it
> * delete the server adapter
> * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically?
> Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO.
--
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, 4 months
[JBoss JIRA] (JBIDE-13384) Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13384?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13384:
-------------------------------------
Summary: Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter (was: Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter (for existing app))
> Server Adapter wizard: Detect binary deployed application in workspace when creating new adapter
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13384
> URL: https://issues.jboss.org/browse/JBIDE-13384
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 3.3.2.Final
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
>
> This issue should find solution to this situation:
> * create application on openshift, then binary deployed another app to it
> * delete the server adapter
> * now i'm going to create the server adapter again: Is there a way how we can detect the binary deployed application and attach it to the server automatically?
> Would be nice if we could handle it...i can image a lot of situations which can cause additional troubles by allowing this (like when the binary deployed app is not in the workspace) but for the situation i described it would be great user experience improvement IMO.
--
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, 4 months
[JBoss JIRA] (JBIDE-16213) Prohibit deployments to AVDs and devices that do not support the minimum SDK version
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16213?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-16213:
-----------------------------------------
If possible, the list of AVDs displayed in the runtime configuration should also be filtered so that only allowed/supported AVDs are displayed. Additionally, the default AVD chosen for as the APK deployment target should be within this filtered list of allowed/supported AVDs.
I'm not sure if this applies to real devices since I have only one at the moment.
> Prohibit deployments to AVDs and devices that do not support the minimum SDK version
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16213
> URL: https://issues.jboss.org/browse/JBIDE-16213
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Vineet Reynolds
>
> Based on the comment in JBIDE-16212 it would be useful to prohibit the "Run on Android emulator" (and possibly "Run on Android device") actions from attempting to perform a deployment of an APK on a device/AVD with a lower runtime version.
> The {{AndroidManifest.xml}} in the generated Android project had a min SDK version of 10. Deployments to AVDs/devices with a lower API version should not have been allowed. At the very least, we could display a more meaningful message instead of the current one: http://www.screencast.com/t/eG8pWIP9
--
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, 4 months
[JBoss JIRA] (JBIDE-13106) Tail files: Change icon and tooltip for "close console" to better show difference to closing view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13106:
-------------------------------------
Summary: Tail files: Change icon and tooltip for "close console" to better show difference to closing view (was: Change icon and tooltip for "close console" to better show difference to closing view)
> Tail files: Change icon and tooltip for "close console" to better show difference to closing view
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13106
> URL: https://issues.jboss.org/browse/JBIDE-13106
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
> Attachments: different-close-actions.png
>
>
> The Server Log console has 2 distinct actions that are labeled "close console".
> !different-close-actions.png!
> 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation
> 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern.
> We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things.
--
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, 4 months