Some form of @Deployment targeting is needed to support multiple containers in same run

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

@Deployment @GlassFishV3Container
public static Archive<?> createDeploymentForGlassFish()

Although the second way (multiple @Deployment methods) looks a little bit more correct/clean, the first one (passing some org.jboss.arquillian.container.spi.Container metadata as a deployment method param) would be a bit more practical imho. Mainly because of the test archives will mostly not differ a lot and the second way would require duplicate information or additional util method creating archive base.

Some thoughts from Andy Gibbons a while back: http://www.andygibson.net/blog/braindrop/do-we-need-to-giftwrap-shrinkwrap/

I like the idea of profiles and conditional archive elements/parts. However this might require a lot of API changes. I think even the ugly if-else + Container metadata would be great atm...