[jbosstools-issues] [JBoss JIRA] (JBIDE-16212) [Android] Retain the Android project builder log in the Console view for the "Run as ..." tasks

[Jeff MAURY (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY updated JBIDE-16212:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> [Android] 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
>             Fix For: 4.6.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> 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 was sent by Atlassian JIRA
(v7.5.0#75005)