[jboss-jira] [JBoss JIRA] Updated: (AS7-1717) mod_cluster needs consistent naming

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated AS7-1717:
--------------------------------

    Description: 
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  ;-(

  was:
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)
* 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  ;-(



> mod_cluster needs consistent naming
> -----------------------------------
>
>                 Key: AS7-1717
>                 URL: https://issues.jboss.org/browse/AS7-1717
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 7.0.0.Final, 7.0.1.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
> * 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira