I think the wildfly-arquillian-container-remote one is there to allow testing against an already running container, without having arquillian control its lifecycle. I personally don't use that so often, but perhaps others have different opinions / habits? Cheers On Fri, Dec 13, 2019 at 7:00 PM Rebecca Searls <rsearls(a)redhat.com <mailto:rsearls@redhat.com>> wrote: Module testsuite/arquillian-utils has profile arquillian.remote.  This profile uses archive org.wildfly.arquillian:wildfly-arquillian-container-remote when running tests within the module.  The default profile in arquillian-utils uses archive org.wildfly.arquillian:wildfly-arquillian-container-managed. Both profiles have existed since the creation of module testsuite/arquillian-utils 7/12/16 (RESTEASY-1361). Is this still used?  Who uses it?  I am inclined to remove it if no one vouches for its use. _______________________________________________ resteasy-dev mailing list resteasy-dev(a)lists.jboss.org <mailto:resteasy-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/resteasy-dev -- Alessio Soldano Associate Manager, Software Engineering Red Hat <https://www.redhat.com> <https://www.redhat.com> _______________________________________________ resteasy-dev mailing list resteasy-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/resteasy-dev