[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139909#comment-15139909
]
Hudson commented on DOXIASITETOOLS-149:
---------------------------------------
SUCCESS: Integrated in doxia-all #249 (See
[https://builds.apache.org/job/doxia-all/249/])
[DOXIASITETOOLS-149] first version is 1.7.0 (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1729489])
* ./doxia-sitetools/doxia-skin-model/pom.xml
> Create a skin descriptor to contain metadata about the skin
> -----------------------------------------------------------
>
> Key: DOXIASITETOOLS-149
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-149
> Project: Maven Doxia Sitetools
> Issue Type: New Feature
> Components: Site renderer, Skin model
> Affects Versions: 1.6
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: 1.7
>
>
> currently, a skin is a jar containing at least {{META-INF/maven/site.vm}},
> which is the Velocity template file
> adding a skin descriptor (as XML with Modello, to be consistent with Maven
> style) would permit meta-data definition.
> The first case I see is Doxia Site Tools prerequisites, to have a skin make
> clear that it requires a newer version of Doxia Site Tools (which is a
> dependency of maven-site-plugin = what end-users see): this would permit
> newer Doxia Site Tools versions to provide new features for skins (like
> DOXIASITETOOLS-150) and skins using these features without fearing failing
> because being used in older maven-site-plugin versions
> this would also create a new "skin-model" module that would give us a natural
> place to document practices around skins
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
