WildFly Exploded Deployments with CLI: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by [[WildFly_Exploded_Deployments_with_auto-deploy-exploded|configuring the deployment scanner]], using marker files or via CLI. The procedure to trigger the deployment with CLI is described below. | Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by [[WildFly_Exploded_Deployments_with_auto-deploy-exploded|configuring the deployment scanner]], using [[WildFly_Exploded_Deployments_with_Marker_Files|marker files]] or via CLI. The procedure to trigger the deployment with CLI is described below. | ||
Revision as of 23:17, 31 March 2016
Internal
Overview
Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by configuring the deployment scanner, using marker files or via CLI. The procedure to trigger the deployment with CLI is described below.