[JBoss JIRA] (JBIDE-16213) Prohibit deployments to AVDs and devices that do not support the minimum SDK version
by Vineet Reynolds (JIRA)
Vineet Reynolds created JBIDE-16213:
---------------------------------------
Summary: 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-13145) Server Adapter: Should show connection wizard if "Tail files", "Port forwarding" etc and connection/application was removed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13145?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13145:
-------------------------------------
Summary: Server Adapter: Should show connection wizard if "Tail files", "Port forwarding" etc and connection/application was removed (was: Server Adapter: Should show connection wizard if "Tail files" and connection was removed)
> Server Adapter: Should show connection wizard if "Tail files", "Port forwarding" etc and connection/application was removed
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13145
> URL: https://issues.jboss.org/browse/JBIDE-13145
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> # ASSERT: make sure that you have an application on OpenShift that you imported to your workspace (and got a project for it)
> # ASSERT: make sure that you have a server adapter for this project
> # EXEC: in *OpenShift Explorer*: select the connection that you used when importing and pick *Remove from View*
> # EXEC: go to your server adapter and pick *OpenShift->Tail files*
> Result:
> Nothing happens. In the log you'll spot:
> {quote}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-11-23 22:49:23.742
> !MESSAGE Failed to retrieve Application from the selected Server.
> Please verify that the associated OpenShift Application still exists.
> {quote}
> Expected:
> The connection wizard pops up with the server, username filled in from the settings in your project (<project>/.settings/org.jboss.tools.openshift.express.ui.prefs)
--
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-13161) Server adapter: Port forwarding should not display error message after removing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13161?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-13161.
------------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.x)
Resolution: Duplicate Issue
closing as duplicate to JBIDE-13145
> Server adapter: Port forwarding should not display error message after removing connection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13161
> URL: https://issues.jboss.org/browse/JBIDE-13161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha2
>
> Attachments: error-getting-application.png
>
>
> The error message dialog should:
> * not appear to achieve consistent behaviour as in JBIDE-13146 (it's the same situation) - as a temporary solution, until it gets fixed properly as stated in JBIDE-13145
> *or*
> * add to the error message also that the associated connection cannot be found.
--
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-13161) Server adapter: Port forwarding should not display error message after removing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13161?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13161:
-------------------------------------
Steps to Reproduce:
# ASSERT: have a server adapter who's application does not exist any more
# EXEC: pick *OpenShift->Port forwarding* from it's context menu
Resullt:
!error-getting-application.png!
Expected result:
Should pop up connection wizard like in JBIDE-13145
was:
# ASSERT: have a server adapter who's application does not exist any more
# EXEC: pick *OpenShift->Port forwarding* from it's context menu
Resullt:
!error-getting-application.png!
> Server adapter: Port forwarding should not display error message after removing connection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13161
> URL: https://issues.jboss.org/browse/JBIDE-13161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: error-getting-application.png
>
>
> The error message dialog should:
> * not appear to achieve consistent behaviour as in JBIDE-13146 (it's the same situation) - as a temporary solution, until it gets fixed properly as stated in JBIDE-13145
> *or*
> * add to the error message also that the associated connection cannot be found.
--
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-16212) Retain the Android project builder log in the Console view for the "Run as ..." tasks
by Vineet Reynolds (JIRA)
Vineet Reynolds created JBIDE-16212:
---------------------------------------
Summary: Retain the Android project builder log in the Console view for the "Run as ..." tasks
Key: JBIDE-16212
URL: https://issues.jboss.org/browse/JBIDE-16212
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 4.1.1.CR1
Reporter: Vineet Reynolds
When attempting to run a newly created hybrid mobile project (with no changes) on an Android emulator, the deployment to the emulator failed.
The Eclipse workspace log contained no information but the following entry:
{noformat}
!ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2013-12-04 14:50:34.841
!MESSAGE APK installation did not succeed
{noformat}
The error dialog displayed the same message. The Ant build log was not available in the Console view, thus providing no info about whether the build failed or why it failed in a subsequent step. It would be useful to retain this build log in the Console View for debugging purposes or log the build output to a file on disk.
Note - I worked around the reported deployment failure by explicitly choosing the AVD to deploy to. For some reason, the hybrid tools was starting an AVD with API level 7. But the feature request is still valid since build or deployment failure could occur due to any reason (like an expired Debug certificate) and I had to rule out a build failure first.
--
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