[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542641#comment-17542641
]
Herve Boutemy commented on DOXIASITETOOLS-174:
----------------------------------------------
class names are completely independant from XML tag names
https://github.com/apache/maven-doxia-sitetools/blob/master/doxia-decoration-model/src/main/mdo/decoration.mdo#L45
and the current {{DecorationModel}} is perfect
and changing would have been easy, because it does not impact so much code
the only impact that would have been hard to manage is impact on users if they
absolutely needed to change the tag name in their site.xml: but they don't need
> rename site.xml root tag from "project" to "site"
> -------------------------------------------------
>
> Key: DOXIASITETOOLS-174
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-174
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Decoration model
> Affects Versions: 1.7.4
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 2.0.0-M3
>
>
> when looking at [decoration model
> descriptor|http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.7/doxia-decoration-model/decoration.html],
> naming the root element as {{project}} (like for {{pom.xml}}) is misleading
> if the root element could be renamed as {{doxia-decoration}}, the obvious
> (this descriptor is about site decoration, done with Doxia) could perhaps
> become obvious
> (in IT, calling everything a "project" is an issue...)
> I know that this change of xsd schema will break compatibility, but I think
> it can really make a big difference in usability (and I should have had this
> idea for Doxia Sitetools 1.7, when we already made some breaking changes...)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
