[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137541#comment-15137541
]
Michael Osipov edited comment on DOXIASITETOOLS-149 at 2/8/16 7:42 PM:
-----------------------------------------------------------------------
Yes, I was referring to the skin project of course. So you want to rely on the
input of the user in that case? Would you create an IT for this? Would make it
easier to test.
Alternatively, we could add a manifest entry with the source encoding of
resources.
was (Author: michael-o):
Yes, I was referring to the skin project of course. So you want to rely on the
input of the user in that case? Would you create an IT for this? Would make it
easier to test.
> 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)
