[
https://issues.jboss.org/browse/ARQ-1507?page=com.atlassian.jira.plugin.s...
]
Stefan Miklosovic edited comment on ARQ-1507 at 9/30/13 9:10 AM:
-----------------------------------------------------------------
This is indeed needed since these extensions are tightly coupled and in the most cases 80%
(in other words pretty regularly) the main source of errors is the bad configuration of
these extensions. The explicit warning on befalf of container would be great but I would
like to have Android container test and extension agnostic meaning there are no artifacts
put into container impl from Drone or extensions themselves.
was (Author: smikloso):
This is indeed needed since these extensions are tightly coupled and in most cases 80%
(in other words pretty regularly) the main source of errors is bad configuration of these
extension. The explicit warning on befalf of container would be great but I would like to
have Android container test and extension agnostic meaning there are no artifacts put into
container impl from Drone or extensions themselves.
Make usage of Arquillian Droidium stack easier
----------------------------------------------
Key: ARQ-1507
URL:
https://issues.jboss.org/browse/ARQ-1507
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha1
Reporter: Karel Piwko
Currently, Droidium consists of 3 thinks:
1/ Container
2/ Native extension
3/ Web extension
User can arbitrary combine these extensions. For that reason, it would be great if
container, which is always used, will emit some huge warning in case that it discovers
Drone is injected and browser==android and web extension is missing on class path.
Similarly, container should be able to figure out that native extension is missing but it
will likely be needed - as it has access to @Instrumented deployments.
--
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