[jboss-jira] [JBoss JIRA] (WFLY-9939) Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-9939:
-----------------------------------
    Description: 
Our openshift images are overriding the org.jboss.as.clustering.jgroups module.xml in order to include a dependency on the org.openshift.ping module. This is fragile because any update to the overridden module.xml needs to be applied to the override file as well, and that can easily break.

Let's make the need for this go away. Possibilities:

1) Add an optional dependency on module "org.openshift.ping" to the org.jboss.as.clustering.jgroups module. The openshift images then just add that module. In bare metal installations the module is not present.

2) Change the standalone-openshift.xml configs such that whatever is using this module declares a "module" attribute, removing the need for the module.xml dependency. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track making the config change and removing the override.)

3) Ship whatever's needed from org.openshift.ping in WF itself, eliminating the need for that module. This may already be in progress as I've seen some relevant JIRAs. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override and the installation of the org.openshift.ping module.) 

[~luck3y] FYI.

  was:
Our openshift images are overriding the org.jboss.as.clustering.jgroups module.xml in order to include a dependency on the org.openshift.ping module. This is fragile because any update to the overridden module.xml needs to be applied to the override file as well, and that can easily break.

Let's make the need for this go away. Possibilities:

1) Add an optional dependency on module "org.openshift.ping" to the org.jboss.as.clustering.jgroups module. The openshift images then just add that module. In bare metal installations the module is not present.

2) Change the standalone-openshift.xml configs such that whatever is using this module declares a "module" attribute, removing the need for the module.xml dependency. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override.)

3) Ship whatever's needed from org.openshift.ping in WF itself, eliminating the need for that module. This may already be in progress as I've seen some relevant JIRAs. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override and the installation of the org.openshift.ping module.) 

[~luck3y] FYI.



> Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images
> -------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-9939
>                 URL: https://issues.jboss.org/browse/WFLY-9939
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>
> Our openshift images are overriding the org.jboss.as.clustering.jgroups module.xml in order to include a dependency on the org.openshift.ping module. This is fragile because any update to the overridden module.xml needs to be applied to the override file as well, and that can easily break.
> Let's make the need for this go away. Possibilities:
> 1) Add an optional dependency on module "org.openshift.ping" to the org.jboss.as.clustering.jgroups module. The openshift images then just add that module. In bare metal installations the module is not present.
> 2) Change the standalone-openshift.xml configs such that whatever is using this module declares a "module" attribute, removing the need for the module.xml dependency. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track making the config change and removing the override.)
> 3) Ship whatever's needed from org.openshift.ping in WF itself, eliminating the need for that module. This may already be in progress as I've seen some relevant JIRAs. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override and the installation of the org.openshift.ping module.) 
> [~luck3y] FYI.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)