[
https://issues.jboss.org/browse/ARQ-1528?page=com.atlassian.jira.plugin.s...
]
Stefan Miklosovic commented on ARQ-1528:
----------------------------------------
Since Android undeployment logic was aligned with Arquillian way in ARQ-1557 there is not
theoretically any problem to approach to support multiple Android containers in one test
run.
The only problem is that Android container is configured in arquillian.xml in container
element which contains properties related to Android SDK and these configuration
properties can not be (or should not be) specified in both container defs. For example,
having androidSdkHome in both container elements does not make much sense since you have
always one Android SDK installed locally and there is e.g. only one ANDROID_SDK_HOME
environment property.
In theory, maybe it could be possible to have multiple Android SDK installations but it
seems to me as overkill.
New approach would "extract" Android SDK related properties from Android
container definition to standalone extension, it would look like this
{code}
<group qualifier="containers" default="true">
<container qualifier="android_1" default="true">
<configuration>
</configuration>
</container>
<container qualifier="android_2" default="true">
<configuration>
</configuration>
</container>
</group>
<extension qualifier="android-platform">
<property name="androidSdkHome">...</property>
// all jar signers stuff and so on
</extension>
{code}
Be able to start multiple Android containers simultaneously in one
test run
---------------------------------------------------------------------------
Key: ARQ-1528
URL:
https://issues.jboss.org/browse/ARQ-1528
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha1
Reporter: Stefan Miklosovic
Assignee: Stefan Miklosovic
Priority: Blocker
--
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