[arquillian-issues] [JBoss JIRA] Commented: (ARQ-272) Allow @Deployment to be optional
Aslak Knutsen (JIRA)
jira-events at lists.jboss.org
Tue Apr 26 05:48:18 EDT 2011
[ https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597920#comment-12597920 ]
Aslak Knutsen commented on ARQ-272:
-----------------------------------
Keep in mind that this is not a feature the will go into Arquillian Core. A non defined @Deployment has another meaning in Arq Core. This can be implemented as a DeploymentScenarioGenerator specially for the OSGi Container test Suite.
> Allow @Deployment to be optional
> --------------------------------
>
> Key: ARQ-272
> URL: https://issues.jboss.org/browse/ARQ-272
> Project: Arquillian
> Issue Type: Feature Request
> Components: OSGi Containers
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 1.0.0.Beta1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the arquillian-issues
mailing list