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

[Karel Piwko (JIRA)]

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

Karel Piwko commented on ARQ-417:
---------------------------------

Initial prototype present at https://github.com/kpiwko/arquillian-extension-maven-deployer

Usage
{code}
@Deployments(@MavenDeployment(value = "org.jboss.weld.examples.jsf:weld-jsf-login:war:1.1.1.Final",
            settings = "src/test/resources/settings.xml"))
@RunWith(Arquillian.class)
public class WarDeploymentTestCase { 
   ...
{code}

It mirrors all the configuration available for @Deployment methods, such as @Protocol, @TargetsContainer, etc. If extension is activated
but no @Deployments annotation is present, it reverts to default behavior.


I'm falling into following issue with Java 5 compilation from cmdline:
http://bugs.sun.com/view_bug.do?bug_id=6512707

Could we make this extension JDK 6 only? 


> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira