Skip to content

Latest commit

 

History

History
70 lines (60 loc) · 2.91 KB

build-and-run-the-quickstart-with-provisioned-server.adoc

File metadata and controls

70 lines (60 loc) · 2.91 KB

Building and running the quickstart application with provisioned {productName} server

Instead of using a standard {productName} server distribution, you can alternatively provision a {productName} server to deploy and run the quickstart, by activating the Maven profile named provisioned-server when building the quickstart:

$ mvn {mavenServerProvisioningCommand} -Pprovisioned-server

The provisioned {productName} server, with the quickstart deployed, can then be found in the target/server directory, and its usage is similar to a standard server distribution.

The server provisioning functionality is provided by the WildFly Maven Plugin, and you may find its configuration in the quickstart pom.xml:

        <profile>
            <id>provisioned-server</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.wildfly.plugins</groupId>
                        <artifactId>wildfly-maven-plugin</artifactId>
                        <configuration>
                            <feature-packs>
                                <feature-pack>
                                    <location>org.wildfly:wildfly-galleon-pack:${version.server}</location>
                                </feature-pack>
                            </feature-packs>
                            <layers>
                                <!-- layers may be used to customize the provisioned server -->
                                <layer>cloud-server</layer>
                            </layers>
                            <!-- deploys the quickstart on root web context -->
                            <runtimeName>ROOT.war</runtimeName>
                        </configuration>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>package</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                    <!-- ... -->
                </plugins>
            </build>
        </profile>
Note

Since the plugin configuration above deploys quickstart on root web context of the provisioned server, the URL to access the application should not have the /{artifactId} path segment after HOST:PORT.