[ 
https://issues.apache.org/jira/browse/MSITE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952566#comment-15952566
 ] 

Hudson commented on MSITE-782:
------------------------------

SUCCESS: Integrated in Jenkins build maven-plugins #8907 (See 
[https://builds.apache.org/job/maven-plugins/8907/])
[MSITE-782] removed reportPlugins parameter: use project.reporting.plugins 
(hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1789855])
* (edit) maven-site-plugin/pom.xml
* (edit) maven-site-plugin/src/it/MSITE-484/parent-usage-test/pom.xml
* (edit) maven-site-plugin/src/it/MSITE-484/pom.xml
* (edit) maven-site-plugin/src/it/MSITE-627/pom.xml
* (edit) maven-site-plugin/src/it/new-configuration/verify.groovy
* (edit) 
maven-site-plugin/src/main/java/org/apache/maven/plugins/site/render/AbstractSiteRenderingMojo.java
* (edit) maven-site-plugin/src/site/apt/maven-3.apt.vm


> Support for custom Velocity tools has disappeared
> -------------------------------------------------
>
>                 Key: MSITE-782
>                 URL: https://issues.apache.org/jira/browse/MSITE-782
>             Project: Maven Site Plugin
>          Issue Type: Bug
>    Affects Versions: 3.5, 3.5.1
>            Reporter: Bernardo
>            Assignee: Michael Osipov
>             Fix For: 3.6
>
>
> Since the version 3.5 any skin using custom velocity tools is no longer 
> working.
> This can be seen on the Reflow maven skin, and also on my own skin, which was 
> developed from the Reflow one.
> The Reflow skin, along its Velocity tools, can be found here:
> https://github.com/andriusvelykis/reflow-maven-skin
> My Maven skin can be found here:
> https://github.com/Bernardo-MG/docs-maven-skin
> My custom velocity tools:
> https://github.com/Bernardo-MG/maven-site-fixer
> All these projects are available through Maven central, making them easy to 
> test.
> To see this problem just use the Reflow skin, which won't print the content 
> of any page. In the case of my own skin, there will be several errors in the 
> HTML code, the most visible being the broken headers.
> It may be actually a Doxia problem, related to this issue:
> https://issues.apache.org/jira/browse/DOXIASITETOOLS-93
> Additionally, there is a related link commenting this problem:
> http://maven.40175.n5.nabble.com/New-maven-site-and-doxia-with-custom-velocity-doxia-td5865376.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to