[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136178#comment-15136178
]
Hervé Boutemy commented on DOXIASITETOOLS-92:
---------------------------------------------
I like the idea of being able to upgrade: just need to make sure I understand
what compromise we do (and what we'll have to make clear in maven-site-plugin
release notes, since people will see the consequence through maven-site-plugin)
for the {{site-jar}} IT, it seems natural
for the Stylus skin: do we have any explanations why it fails?
do we have an idea of how many non-Apache Maven skins will fail?
Even if we stopped recently to maintain Stylus skin, I find it a little hard to
have it unusable now: one of the Maven features is that it has pretty good
upgrade compatibility
If we upgrade, is it easy for a user to downgrade and use Stylus Skin? Keeping
one maven-site-plugin IT that uses Stylus skin would be a good sign
Another question: does the default skin work with upgraded Velocity?
> upgrade Velocity from 1.5 to 1.6.4
> ----------------------------------
>
> Key: DOXIASITETOOLS-92
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-92
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Site renderer
> Affects Versions: 1.6
> Reporter: Hervé Boutemy
>
> Velocity 1.5 was released in 2007:
> http://velocity.apache.org/engine/devel/changes-report.html#a1.5
> 1.6.4 was done in 2010
> http://velocity.apache.org/engine/devel/changes-report.html#a1.6.4
> I don't have precise feature in mind, just Velocity Tools 2.0 annoucement
> tells Velocity 1.6 is required (seems to work well with 1.5...):
> http://velocity.apache.org/news.html#tools20
> bq. This should be useable as a drop in replacement for Tools 1.4 or Tools
> 2.0-beta4, with a few minor exceptions. The 2.x series of VelocityTools
> requires Velocity 1.6 and JDK 1.5+.
> From a first test, actual Doxia templates work with 1.6 but not with 1.7, so
> perhaps upgrading to 1.6 is a good step before trying latest 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
