[
https://issues.jboss.org/browse/MODCLUSTER-254?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-254:
-------------------------------------------
Issue Type: Enhancement (was: Bug)
Priority: Optional (was: Critical)
AS7-1718 CLONE - mod_cluster needs consistent naming
----------------------------------------------------
Key: MODCLUSTER-254
URL:
https://issues.jboss.org/browse/MODCLUSTER-254
Project: mod_cluster
Issue Type: Enhancement
Affects Versions: 1.1.3.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Optional
Cloning over from AS7-1718 to reflect the community upstream request in mod_cluster.
---
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira