[arquillian-issues] [JBoss JIRA] (ARQ-417) Support maven deployments

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen commented on ARQ-417:
-----------------------------------

completely forgotten to check this one.. 

On top of my head, setting the maven cords+version in source code doesn't sound to useful. Maybe a arq/extension config, replaceDeployment
                
> Support maven deployments
> -------------------------
>
>                 Key: ARQ-417
>                 URL: https://issues.jboss.org/browse/ARQ-417
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Configuration
>            Reporter: Adrian Cole
>            Assignee: Karel Piwko
>
> Microdeployments via ShrinkWrap are a nimble deployment mechanism that allows developers to test bytecode skipping the build.  Another usecase is to have ARQ in a CI loop, testing artifacts post-deploy.  For this sort of scenario, it would be useful to reuse test cases from the microdeployments, but have them leveraged against code pulled from maven artifacts published in a prior step.  
> For example, we could have an @Maven annotation which could define the coordinates of an ear file, and place that on a test scenario that performs the war, ejb, cdi, etc tests of from the dependent modules.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira