If you're using maven you could download the wildfly-dist ZIP and unzip it into a directory. This would have the advantage of using the correct target runtime you're using too.

Example:
<plugin>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <id>unpack-wildfly</id>
            <phase>process-test-classes</phase>
            <goals>
                <goal>unpack</goal>
            </goals>
            <configuration>
                <artifactItems>
                    <artifactItem>
                        <groupId>org.wildfly</groupId>
                        <artifactId>wildfly-dist</artifactId>
                        <version>${version.org.wildfly.dist}</version>
                        <type>zip</type>
                        <!-- overwrite to clean any previous deployments -->
                        <overWrite>true</overWrite>
                        <outputDirectory>${project.build.directory}</outputDirectory>
                    </artifactItem>
                </artifactItems>
            </configuration>
        </execution>
    </executions>
</plugin>

On 04/30/2015 10:57 AM, Daniel Kreuter wrote:
Hi,

Am 30.04.2015 um 15:47 schrieb Brian Stansberry <brian.stansberry@redhat.com>:


[1] http://wildfly.org/news/2015/03/13/Offline-CLI/

Question is, should be embedded arquillian container still available for
9.x?


Jason Greene would need to rule on that, but I know we were ok with 
dropping it before. Is there much use of it?

One thing I use the embedded module is for our jenkins build because we have no access to a managed or remote WildFly instance on that machine, so yeah I would like to see a working plugin for future versions of WildFly, otherwise I either need to drop my integration tests or stick with 8.2 instead.

Regards,

Daniel


_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

-- 
James R. Perkins
JBoss by Red Hat