WildFly Exploded Deployments with Marker Files: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * WildFly Exploded Deployments") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[WildFly Exploded Deployments]] | * [[WildFly Exploded Deployments]] | ||
* [[WildFly Exploded Deployments with auto-deploy-exploded|WildFly Exploded Deployments with <tt>auto-deploy-exploded</tt>]] | |||
=Overview= | |||
If the <tt>[[WildFly Exploded Deployments with auto-deploy-exploded|auto-deploy-exploded]]</tt> deployment is not enabled in the deployment scanner configuration, an exploded archive can be deployed by placing a <tt>.dodeploy</tt> marker file in the <tt>deployments</tt> directory. For example, if the <tt>deployments</tt> directory contains a <tt>test.ear</tt> directory, the deployment is triggered by placing a <tt>test.ear.dodeploy</tt> marker file. | |||
Latest revision as of 23:04, 31 March 2016
Internal
Overview
If the auto-deploy-exploded deployment is not enabled in the deployment scanner configuration, an exploded archive can be deployed by placing a .dodeploy marker file in the deployments directory. For example, if the deployments directory contains a test.ear directory, the deployment is triggered by placing a test.ear.dodeploy marker file.