[
https://issues.apache.org/jira/browse/CB-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-2944:
---------------------------------
Fix Version/s: (was: 2.7.0)
2.8.0
> Tweak ./cordova/run project-level script for BlackBerry
> --------------------------------------------------------
>
> Key: CB-2944
> URL: https://issues.apache.org/jira/browse/CB-2944
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: BlackBerry
> Reporter: Filip Maj
> Assignee: Lorin Beer
> Fix For: 2.8.0
>
>
> {code}
> run [--target=<id>]
> {code}
> Deploys a build of the app to an available device or emulator.
> Implicitly calls {{build}} first (see CB-2932).
> If {{--target}} is specified, attempts to deploy the app to the device or
> emulator identified by <id>. If the attempt fails, the script will error out
> with code 2 and an appropriate error message. If no {{--target}} is
> specified, follows this multi-device flow:
>
> # Are there any devices connected and available (should use the
> {{list-devices}} script TODO: [issue ref to come] to determine this)? If so,
> deploy to the first available one, if not continue.
> # Are there any actual emulators available, i.e. started/running? (use
> {{list-started-emulators}} script TODO: [issue ref to come] to determine
> this). If so, target the first one. If no, continue.
> # Are there any emulator images available to start? (use
> {{list-emulator-images}} script TODO: [issue ref to come] to determine this).
> If so, call {{start-emulator <id>}} TODO: [issue ref to come] of the first
> available image, wait for it to become ready, then deploy to it.
> # If you get to this step, error out with a "no devices or emulators
> available" and exit with code 2.
--
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
