[ https://issues.apache.org/jira/browse/OPENEJB-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970629#comment-13970629 ]
Xavier Dury commented on OPENEJB-2089: -------------------------------------- Well, you already implemented (1) while I was writing my comment :-) > Provide ApplicationComposer feature as a JUnit @Rule > ---------------------------------------------------- > > Key: OPENEJB-2089 > URL: https://issues.apache.org/jira/browse/OPENEJB-2089 > Project: OpenEJB > Issue Type: Improvement > Components: tests > Reporter: Xavier Dury > Assignee: Romain Manni-Bucau > Attachments: OPENEJB-2089.patch, OPENEJB-modules-as-param.patch > > > Currently, ApplicationComposer uses the only one shot we have at specifying > which Runner a JUnit test should use. > This can easily be circumvented by exposing the same functionality through a > JUnit @Rule (TestRule). > By doing this, we could use ApplicationComposer with an other Runner (like > Parameterized) and/or other @Rules. -- This message was sent by Atlassian JIRA (v6.2#6252)