[
https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl...
]
Radoslav Husar moved AS7-1718 to MODCLUSTER-254:
------------------------------------------------
Project: mod_cluster (was: Application Server 7)
Key: MODCLUSTER-254 (was: AS7-1718)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 1.1.3.Final
(was: 7.0.0.Final)
(was: 7.0.1.Final)
Component/s: (was: Clustering)
CLONE - mod_cluster needs consistent naming
-------------------------------------------
Key: MODCLUSTER-254
URL:
https://issues.jboss.org/browse/MODCLUSTER-254
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.3.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
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
*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)
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira