[arquillian-issues] [JBoss JIRA] (ARQ-1014) Packaging Processor phase is skipped when the deployment is not testable

[Aslak Knutsen (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen updated ARQ-1014:
-------------------------------

    Summary: Packaging Processor phase is skipped when the deployment is not testable  (was: Instrumentation is skipped when the deployment is not testable)

    
> Packaging Processor phase is skipped when the deployment is not testable
> ------------------------------------------------------------------------
>
>                 Key: ARQ-1014
>                 URL: https://issues.jboss.org/browse/ARQ-1014
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Jacoco
>    Affects Versions: 1.0.0.Alpha3
>            Reporter: Jan Papousek
>             Fix For: 2.0.0.Beta1
>
>
> Documentation of [Deployment|https://github.com/arquillian/arquillian-core/blob/master/container/test-api/src/main/java/org/jboss/arquillian/container/test/api/Deployment.java].testable() says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all [application archive processors|https://github.com/arquillian/arquillian-core/blob/master/container/test-spi/src/main/java/org/jboss/arquillian/container/test/spi/client/deployment/ApplicationArchiveProcessor.java] (see [code|https://github.com/arquillian/arquillian-core/blob/master/container/test-impl-base/src/main/java/org/jboss/arquillian/container/test/impl/client/deployment/DeploymentGenerator.java#L156]), so Jacoco instrumentation is not processed.
> I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator.

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