jvanzyl 02/03/29 09:11:00
Added: xdocs tasks.xml
Log:
Adding tasks.xml xdoc
Revision Changes Path
1.1 jakarta-turbine-maven/xdocs/tasks.xml
Index: tasks.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Tasks</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Tasks">
<p>
<ul>
<li> checkstyle integration (warner) </li>
<li> dep graph (jvz)</li>
<li> maven:deploy-dist needs to work (jvz)</li>
<li> schema for project.xml (jvz)</li>
<li> need to restructure the mailing lists and object model so
that we can easily select the dev mailing list for continuous
integration problems. discovered when trying to apply the
nag feature of gump.</li>
<li> todo document => bob suggests just a task list which can be scoped for
for a release if necessary.</li>
<li> roadmap document</li>
<li> status document (weekly report type thing)</li>
<li> faq</li>
<li> look at release guide in tomcat 4</li>
<li> the inceptionYear and organization must be set in order for
javadoc to work. i get illegal pattern char without, need to
make sure those things are set.</li>
<li> how to generally deal with example code and where it belongs
in the source tree and how it should be package in the
distribution.</li>
<li> dealing with contrib and scratchpad areas.</li>
<li> how to shuffle your cvs structure around and keep your history. i
notice
some projects that i'm trying to mavenize have some pretty weird directory
structures but it would be nice to be able to restructure the directory
and still keep the history.</li>
<li> release generated page based on the distribution directory and some
standard text. just looking at things that can be culled from
the turbine site.</li>
<li> same with the how do i contribute blurb at the bottom of the t2
pages. those can be generated.</li>
</ul>
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
