[arquillian-issues] [JBoss JIRA] (ARQ-920) Support @Deployment on non-public member (method or field)

Dan Allen (JIRA) jira-events at lists.jboss.org
Sun May 13 13:49:17 EDT 2012


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

Dan Allen commented on ARQ-920:
-------------------------------

The benefit here is that it reduces one extra keyword that has to be repeatedly typed, which is going to reduce friction of using Arquillian.

{code:java}
@RunWith(Arquillian.class)
public class MyTestCase {
    @Deployment
    static JavaArchive createDeployment() {
        return ShrinkWrap.create(JavaArchive.class);
    }
}
{code}

or

{code:java}
@RunWith(Arquillian.class)
public class MyTestCase {
    @Deployment
    static JavaArchive deployment = ShrinkWrap.create(JavaArchive.class);
}
{code}
                
> Support @Deployment on non-public member (method or field)
> ----------------------------------------------------------
>
>                 Key: ARQ-920
>                 URL: https://issues.jboss.org/browse/ARQ-920
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Dan Allen
>            Priority: Minor
>              Labels: starter
>
> I don't see a reason why we are forcing the @Deployment member (method or field) to be public. It's common to have non-public injection points, so it's reasonable to assume we can honor non-public members for defining a @Deployment as well.

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

        


More information about the arquillian-issues mailing list