Skip to content

Commit

Permalink
Commit from JBoss Tools
Browse files Browse the repository at this point in the history
  • Loading branch information
gastaldi committed Mar 4, 2014
1 parent 0b29698 commit 2ee840c
Show file tree
Hide file tree
Showing 17 changed files with 656 additions and 4 deletions.
3 changes: 3 additions & 0 deletions .gitignore
Expand Up @@ -16,3 +16,6 @@ docs/reference/src/main/docbook/en-US/version_info.xml
.factorypath
atlassian-ide-plugin.xml
.externalToolBuilders
target
.settings/*
!.settings/.jsdtscope
3 changes: 3 additions & 0 deletions .openshift/action_hooks/README.md
@@ -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
18 changes: 18 additions & 0 deletions .openshift/config/modules/README
@@ -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.

0 comments on commit 2ee840c

Please sign in to comment.