[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578233#comment-15578233 ]
Hudson commented on DOXIASITETOOLS-168: --------------------------------------- FAILURE: Integrated in Jenkins build maven-plugins #7349 (See [https://builds.apache.org/job/maven-plugins/7349/]) [MSITE-782] check that Velocity tools declared in /META-INF/maven/site-tools.xml are discovered after DOXIASITETOOLS-168 r1765053 (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1765073]) * (add) maven-site-plugin/src/it/doxia-formats/src/main/resources/META-INF * (add) maven-site-plugin/src/it/doxia-formats/src/main/resources/META-INF/maven * (add) maven-site-plugin/src/it/doxia-formats/src/main/resources/META-INF/maven/site-tools.xml * (delete) maven-site-plugin/src/it/doxia-formats/src/main/resources/tools.xml * (edit) maven-site-plugin/src/it/doxia-formats/src/site/apt/velocity-context.apt.vm * (delete) maven-site-plugin/src/it/doxia-formats/verify.groovy.edited > Add ability to explicitly load custom Velocity tools > ---------------------------------------------------- > > Key: DOXIASITETOOLS-168 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-168 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site renderer > Affects Versions: 1.7.1 > Reporter: Michael Osipov > Assignee: Michael Osipov > Fix For: 1.7.2 > > > Previous versions instructed Velocity to load tools implicitly from > classpath. We never supported this officially. Now that the toolbox is > created explicitly, this options is gone. Provide a way to load tools > explicitly designated for the Maven Site Plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)