[arquillian-issues] [JBoss JIRA] (ARQ-1524) Implement deployment logic when native plugin is not on class path

[Stefan Miklosovic (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809508#comment-12809508 ] 

Stefan Miklosovic commented on ARQ-1524:
----------------------------------------

The trick here is to isolate deployment logic into services and get them all upon container start and sort them according to precedence. Deployment services in native plugin will have higher precedence than these in container adapter so once native is on cp, these will be used, otherwise default deployment services from container itself will be used.
                
> Implement deployment logic when native plugin is not on class path
> ------------------------------------------------------------------
>
>                 Key: ARQ-1524
>                 URL: https://issues.jboss.org/browse/ARQ-1524
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Droidium
>    Affects Versions: droidium_1.0.0.Alpha1
>            Reporter: Stefan Miklosovic
>
> When native plugin is not on class path, we can install packages to Android device directly via Android's injection install and uninstall methods however since Android container without native plugin is not capable to follow Arquillian deployment logic, we have to use these methods so @Deployment method has to be kind of dummy.
> There has to be deployment logic implemented when native plugin is not on class path. This has to be investigated further. 
> This is the logical continuation of ARQ-1521

--
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