[arquillian-issues] [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated ARQ-272:
-------------------------------

    Description: 
OSGi test cases frequently generate non-trivial bundle deployments as part of their test methods.

The bundle that contains the test case is automatically generated by ARQ. To be precise, the test class is always added to the @Deployment. The bundle manifest is generated or extended by the required Import/Export-Package statements.

If @Deployment was missing, ARQ could generate an Archive that contains just the test class, which would reduce the noise in ARQ OSGi tests considerably.

Currently this code is required in every OSGi test case that does not operate on a single bundle deployment.

   @Deployment
   public static Archive<?> createDeployment()
   {
      return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
   }


  was:
OSGi test cases frequently generate non-trivial bundle deployments as part of their test methods.

The bundle that contains the test case is automatically generated by ARQ. To be precise, the test class is always added to the @Deployment. The bundle manifest is generated or extended by the required Import/Export-Package statements.

If @Deployment was missing, ARQ could generate an Archive that contains the test class, which would reduce the noise in ARQ OSGi tests considerably.



> Allow @Deployment to be optional
> --------------------------------
>
>                 Key: ARQ-272
>                 URL: https://jira.jboss.org/browse/ARQ-272
>             Project: Arquillian
>          Issue Type: Feature Request
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: 1.0.0.Alpha4
>
>
> OSGi test cases frequently generate non-trivial bundle deployments as part of their test methods.
> The bundle that contains the test case is automatically generated by ARQ. To be precise, the test class is always added to the @Deployment. The bundle manifest is generated or extended by the required Import/Export-Package statements.
> If @Deployment was missing, ARQ could generate an Archive that contains just the test class, which would reduce the noise in ARQ OSGi tests considerably.
> Currently this code is required in every OSGi test case that does not operate on a single bundle deployment.
>    @Deployment
>    public static Archive<?> createDeployment()
>    {
>       return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
>    }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira