[
https://issues.jboss.org/browse/JBIDE-16330?page=com.atlassian.jira.plugi...
]
Gorkem Ercan commented on JBIDE-16330:
--------------------------------------
It does try to minimize the number of emulator instances to save on resources. I guess we
can ask to restart the instance in case of an edit to selected AVD on launch configuration
or just give a warning
Deployment to Android emulator ignores saved run configuration
--------------------------------------------------------------
Key: JBIDE-16330
URL:
https://issues.jboss.org/browse/JBIDE-16330
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.Final
Reporter: Vineet Reynolds
Priority: Minor
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The deployment to an emulator is always performed on a currently running AVD even if the
runtime config for the project specifies a different AVD.
Ignore/reject if this is by design. But from the point of view of the user, it would be
better to ensure consistency - when a user wants to run his project on a specific AVD, he
needs to create a runtime config, but the moment a different AVD is running, this config
is ignored.
--
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