[jboss-jira] [JBoss JIRA] (WFLY-689) mod_cluster needs consistent naming
[
https://issues.jboss.org/browse/WFLY-689?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro closed WFLY-689.
-----------------------------
Assignee: Paul Ferraro
Fix Version/s: 8.0.0.Alpha3
(was: Awaiting Volunteers)
Resolution: Partially Completed
I'm going to close this per discussion/rant here:
https://github.com/wildfly/wildfly/pull/4691
In Wildfly 8, I've attempted to consolidate around using the actual project name (i.e.
"mod_cluster") wherever possible.
Since EAP 6 is already out the door, it appears we are forever stuck with those names
found in configuration files and the management api:
* modcluster as the subsystem name
* org.jboss.as.modcluster as the extension module name
* urn:jboss:domain:modcluster:x.x as the xml namespace
* modcluster as the advertise socket binding name
mod_cluster needs consistent naming
-----------------------------------
Key: WFLY-689
URL: https://issues.jboss.org/browse/WFLY-689
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Minor
Fix For: 8.0.0.Alpha3
We have been running into issues with misspelt modcluster, mod_cluster and mod-cluster
(and Mod-cluster) for quite some time now, making difficult time for users. Surely there
are sometimes rules where we can't stick to proper naming but we should then be able
to minimize to two names.
* project name = mod_cluster
* AS5 microcotainer service name = ModCluster
* console name = "Mod_cluster Status"
* xsd schema filename = mod-cluster (./docs/schema/jboss-as-mod-cluster_1_0.xsd)
* xmlns = modcluster (eg xmlns="urn:jboss:domain:modcluster:1.0")
* xs elements = mod-cluster (eg mod-cluster-config)
* schema comments = mod_cluster (eg <!-- mod_cluster parameters ...)
* jar name = mod_cluster (ie mod_cluster-1.1.3.Final)
* package names org.jboss.modcluster VS org.jboss.mod_cluster
* maven artefacts: artifactId jboss-as-modcluster VS mod_cluster
* subsystem name: "JBoss Application Server: ModCluster Subsystem"
I am not going to name the EAP5 components where names are significantly changed too.
We need this madness to stop soon enough ;-(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira