[ https://jira.jboss.org/browse/ARQ-293?page=com.atlassian.jira.plugin.syst... ] Dan Allen edited comment on ARQ-293 at 9/15/10 2:30 AM: -------------------------------------------------------- Note my recommendation here: https://community.jboss.org/message/561762#561762 One way to accomplish this would be to inject a container identifier into the @Deployment method. Another would be to allow multiple @Deployment methods, each annotated with an execution environment qualifier (and perhaps one without a qualifier that's the fallback). Arquillian would then select the appropriate @Deployment method according to which container I am targeting. (See Proposal: Filtering out tests not compatible with target container (http://community.jboss.org/thread/156500)). For example: @Deployment @JBossAS6Container public static Archive<?> createDeploymentForJBossAS() { // prepare for JBoss AS 6 } @Deployment @GlassFishV3Container public static Archive<?> createDeploymentForGlassFish() { // prepare for GlassFish V3 } was (Author: dan.j.allen): Note my recommendation here: https://community.jboss.org/message/561762#561762 {quote}One way to accomplish this would be to inject a container identifier into the @Deployment method. Another would be to allow multiple @Deployment methods, each annotated with an execution environment qualifier (and perhaps one without a qualifier that's the fallback). Arquillian would then select the appropriate @Deployment method according to which container I am targeting. (See Proposal: Filtering out tests not compatible with target container (http://community.jboss.org/thread/156500)). For example: {code:java}@Deployment @JBossAS6Container public static Archive<?> createDeploymentForJBossAS() { // prepare for JBoss AS 6 } @Deployment @GlassFishV3Container public static Archive<?> createDeploymentForGlassFish() { // prepare for GlassFish V3 }{code}{quote} -- 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

[ https://jira.jboss.org/browse/ARQ-293?page=com.atlassian.jira.plugin.syst... ] Dan Allen edited comment on ARQ-293 at 9/15/10 2:31 AM: -------------------------------------------------------- Note my recommendation here: https://community.jboss.org/message/561762#561762 One way to accomplish this would be to inject a container identifier into the @Deployment method. Another would be to allow multiple @Deployment methods, each annotated with an execution environment qualifier (and perhaps one without a qualifier that's the fallback). Arquillian would then select the appropriate @Deployment method according to which container I am targeting. ( See Proposal: Filtering out tests not compatible with target container => http://community.jboss.org/thread/156500 ). For example: @Deployment @JBossAS6Container public static Archive<?> createDeploymentForJBossAS() { // prepare for JBoss AS 6 } @Deployment @GlassFishV3Container public static Archive<?> createDeploymentForGlassFish() { // prepare for GlassFish V3 } was (Author: dan.j.allen): Note my recommendation here: https://community.jboss.org/message/561762#561762 One way to accomplish this would be to inject a container identifier into the @Deployment method. Another would be to allow multiple @Deployment methods, each annotated with an execution environment qualifier (and perhaps one without a qualifier that's the fallback). Arquillian would then select the appropriate @Deployment method according to which container I am targeting. (See Proposal: Filtering out tests not compatible with target container => http://community.jboss.org/thread/156500. For example: @Deployment @JBossAS6Container public static Archive<?> createDeploymentForJBossAS() { // prepare for JBoss AS 6 } @Deployment @GlassFishV3Container public static Archive<?> createDeploymentForGlassFish() { // prepare for GlassFish V3 } -- 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

[ https://issues.jboss.org/browse/ARQ-293?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-293: ------------------------------ Fix Version/s: 1.1.0.Beta1 (was: 1.0.0.Final) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-293?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen commented on ARQ-293: ----------------------------------- Some thoughts from Andy Gibbons a while back: http://www.andygibson.net/blog/braindrop/do-we-need-to-giftwrap-shrinkwrap/ -- 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