Bernardo commented on MSITE-782:

I'll try to be as detailed as possible, as there are a few projects mixed on 

If you need any more info, just ask for it.

h5. Velocity Tool

First of all, the code for the Velocity tool being used can be found in this 

The configuration file for the Maven Site Fixer Velocity tool can be found 
inside of it, in the path "src/main/resources/tools.xml".

h5. Maven Skin

This Velocity tool is loaded into the skin. The Maven skin code can be found 

Inside the Docs Maven Skin POM the Velocity tool is declared as a dependency:
         <!-- Maven Site Fixer -->
         <!-- Velocity -->

h5. Test project

Finally, in the test project the Maven skin is set as a dependency of the Maven 
Site plugin, in the build section:
            <!-- Site -->
            <!-- Generates the Maven Site -->
                  <!-- Docs Maven Skin -->
                  <!-- Velocity -->

> 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
> 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

Reply via email to