[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136537#comment-15136537
]
Hudson commented on DOXIASITETOOLS-149:
---------------------------------------
SUCCESS: Integrated in maven-plugins #5068 (See
[https://builds.apache.org/job/maven-plugins/5068/])
[DOXIASITETOOLS-149] updated code for new exception thrown (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1729058])
*
maven-site-plugin/src/main/java/org/apache/maven/plugins/site/render/AbstractSiteRenderingMojo.java
> create a skin descriptor to contain meta-data 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
> Affects Versions: 1.6
> Reporter: 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)