Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
17 changed files
with
656 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
For information about which action hooks are supported, consult the OpenShift documentation: | ||
|
||
https://github.com/openshift/origin-server/blob/master/node/README.writing_applications.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
Place your JBoss EAP6.0 modules in this directory. This directory is added to the | ||
module path of the EAP6.0 server associated with your application. It has the | ||
same structure as the standard EAP6.0 modules directory. | ||
|
||
The modules placed in this directory will be added to or override the default modules | ||
provided by the OpenShift JBoss EAP6.0 cartridge. | ||
|
||
Scenarios: | ||
1) Replace a default module with a new module that contains a bug fix or new feature | ||
2) Add a module that does not exist in the base OpenShift EAP6.0 cartridge in order to add | ||
a new component. Typically these new modules will need to be enabled and configured in | ||
standalone.xml | ||
|
||
Unless one of the above scenarios is required there is no need to modify the | ||
modules directory. | ||
|
||
NOTE: Replacing default modules as in scenario 1 can cause conflicts between modules so | ||
should be done with caution and adequate testing. |
Oops, something went wrong.