maven-plugins/tasklist/plugin.jelly
kaz 2d9dc3397b Restored the ability to allow a user to select the name of the tag to be
used for the generation of the tasklist instead of the hardcoding of
"@todo" in the vdoclet template.  I didn't even realize this
functionality was removed until doing a doc update that Tim O'Brien
supplied and I saw the maven.tasklist.taskTag.  Fixing this required
some changes to vdoclet, namely, adapting the JellyContext to a Velocity
context.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113033 13f79535-47bb-0310-9956-ffa450edef68
2003-03-03 21:20:57 +00:00

55 lines
1.5 KiB
XML

<?xml version="1.0"?>
<project
xmlns:j="jelly:core"
xmlns:doc="doc"
xmlns:vdoclet="vdoclet">
<goal name="maven-tasklist-plugin:register">
<doc:registerReport
name="Task List"
pluginName="maven-tasklist-plugin"
link="task-list"
description="Report on tasks specified in the source code."/>
</goal>
<goal name="maven-tasklist-plugin:deregister">
<doc:deregisterReport name="Task List"/>
</goal>
<!-- ================================================================== -->
<!-- T A S K C R E A T I O N -->
<!-- ================================================================== -->
<goal name="tasklist" prereqs="maven-tasklist-plugin:report"/>
<goal
name="maven-tasklist-plugin:report"
prereqs="xdoc:init"
description="Generate a list of tasks from @todo tags in your code">
<j:set var="genDocs"
value="${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.gen.docs')}"/>
<j:set var="encoding"
value="${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.docs.outputencoding')}"/>
<j:set var="taskTag" value="${maven.tasklist.taskTag}"/>
<j:if test="${sourcesPresent == 'true'}">
<echo>Generating tasklist ...</echo>
<vdoclet:vdoclet
srcDir="${pom.build.sourceDirectory}"
destDir="${genDocs}"
template="plugin-resources/templates/tasklist.vm"
outputFile="task-list.xml"
encoding="${encoding}"
/>
</j:if>
</goal>
</project>