Arquillian - EAP 5.1

jndi.properties
#java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.initial=org.jboss.security.jndi.LoginInitialContextFactory
java.naming.factory.url.pkgs=org.jboss.naming\:org.jnp.interfaces
java.naming.provider.url=jnp://localhost:1099
java.naming.security.principal=admin
java.naming.security.credentials=admin
java.naming.security.protocol=jmx-console

auth.conf
jmx-console {
    org.jboss.security.ClientLoginModule required;
};

examples/junit/pom.xml:jbossas-remote-51
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <configuration>
        <argLine>-Djava.security.auth.login.config=src/test/jboss-resources/auth.conf</argLine>
        <includes>
            <include>com/acme/ejb/*</include>
            <include>com/acme/jms/*</include>
            <include>com/acme/resources/*</include>
        </includes>
    </configuration>
</plugin>


org.jboss.profileservice.management.client.upload.DeploymentProgressImpl missing from jboss-as-client:5.1.0.GA. Added to jbossas-remote-51 profile:

<dependency>
    <groupId>org.jboss.jbossas</groupId>
    <artifactId>jboss-as-profileservice</artifactId>
    <version>6.0.0.20100429-M3</version>
    <type>jar</type>
    <classifier>client</classifier>
</dependency>

Unless you remove this line in the 5.1 container(not sure if it is really needed? This makes it equal to to remote-60 container, but the remote-60 container expects CDI Enrichers which breaks the 5.1 Deployment) the first test case will fail(shows up as the last for some strange reason? Maven surefire test failure/sucess order?)
org.jboss.arquillian.jbossas.remote51.JBossASRemoteContainer.initDeploymentManager -> VFS.init();