jvanzyl 02/04/14 19:08:52
Modified: xdocs tasks.xml
Log:
Updating the task list, sorting by version, unassigned and complete.
Revision Changes Path
1.13 +126 -103 jakarta-turbine-maven/xdocs/tasks.xml
Index: tasks.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/tasks.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- tasks.xml 9 Apr 2002 13:57:13 -0000 1.12
+++ tasks.xml 15 Apr 2002 02:08:52 -0000 1.13
@@ -9,28 +9,133 @@
<body>
<section name="Tasks">
<p>
+ </p>
+
+ <subsection name="Beta 4">
+ <p>
+ <ul>
+ <li>
+ The exception handling must be cleaned up ASAP in order to provide
+ meaningful information to users. As a stop-gap solution the error
+ can be trapped in the executors and emitted until a way is found
+ to tame the AntTaskAdapter which eats the exceptions. (jvz)
+ </li>
+ <li>
+ Maven:deploy-dist needs to work. (jvz)
+ </li>
+ <li>
+ Roadmap document. (jvz)
+ </li>
+ <li>
+ Formalize how jarResources elements are moved from the project
+ directory layout into the classpath for testing and into the JAR
+ that is packaged with the distribution.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ <subsection name="Beta 5">
+ <p>
+ <ul>
+ <li>
+ Write proposal for globally distributed JAR repository and
distribution
+ repository. There are definite things to be learned from the Perl
folks.(jvz)
+ </li>
+ <li>
+ dep graph (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>
+ Status document (weekly report type thing).
+ </li>
+ <li>
+ Look at release guide in tomcat 4.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ <subsection name="Unassigned">
+ <p>
+ <ul>
+ <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>
+ We need to detect whether we are running in a 1.4 environment and
+ make the necessary adjustments if necessary. I believe there is
+ currently a problem with XML parser classes being duplicated. (jvz)
+ </li>
+ <li>
+ Add support for the various coding specifications so that those
properties
+ can be applied to things like checkstyle and to create a document
+ outlining the coding specification.
+ </li>
+ <li>
+ Specification of the license used so a standard page can be
+ generated.
+ </li>
+ <li>
+ See if jxr can be configured to only generate one file.gif and
+ folder.gif, rather than one per source folder (dIon)
+ </li>
+ <li>
+ Template for usecases.
+ </li>
+ <li>
+ xref produces cross references for <sourceDirectories> and
+ <testSourceDirectories>. javadoc produces html for
+ <sourceDirectories> only.
+ </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>
+ </subsection>
+ </section>
+
+ <section name="Complete">
+ <p>
<ul>
- <li>
- The exception handling must be cleaned up ASAP in order to provide
- meaningful information to users. As a stop-gap solution the error
- can be trapped in the executors and emitted until a way is found
- to tame the AntTaskAdapter which eats the exceptions. (jvz)
- </li>
- <li>
- We need to detect whether we are running in a 1.4 environment and
- make the necessary adjustments if necessary. I believe there is
- currently a problem with XML parser classes being duplicated. (jvz)
- </li>
<li>
- Write proposal for globally distributed JAR repository and distribution
- repository. There are definite things to be learned from the Perl
folks.(jvz)
+ A process for moving things from the task list to a list of items
+ completed so they can be listed in documentation for a release
+ automatically.
</li>
<li>
- Write a proposal for the standard naming of JAR files and implement
- prototype with Maven for demonstration. (jvz)
+ Schema for project.xml (jvz)
</li>
<li>
- Maven updater: a reliable way to transform the project.xml file when
+ Maven POM updater: a reliable way to transform the project.xml file when
changes are made. The coming changes to specification of tests will
change the structure of the project.xml file and it should be easy
for users to absorb these changes. They need to be notified, allowed
@@ -38,101 +143,19 @@
transparently applied.
</li>
<li>
+ Make a document that displays the list of currently registered
+ projects.
+ </li>
+ <li>
Add a maven:xml-validate target which will validate all xml source
against it's DTD (if present). Will most likely need a new element
in project.xml (<xmlSourceDirectories>) similar to source
directories. Any directory listed in an <xmlSourceDirectory>
will be validated.
</li>
- <li>
- Make a document that displays the list of currently registered
- projects.
- </li>
- <li>
- Formalize how jarResources elements are moved from the project
- directory layout into the classpath for testing and into the JAR
- that is packaged with the distribution.
- </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>
- Roadmap document.
- </li>
- <li>
- Status document (weekly report type thing).
- </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>
- <li>
- Template for usecases.
- </li>
- <li>
- A process for moving things from the task list to a list of items
- completed so they can be listed in documentation for a release
- automatically.
- </li>
- <li>
- xref produces cross references for <sourceDirectories> and
- <testSourceDirectories>. javadoc produces html for
- <sourceDirectories> only.
- </li>
- <li>
- See if jxr can be configured to only generate one file.gif and
- folder.gif, rather than one per source folder (dIon)
- </li>
- <li>
- Add support for the various coding specifications so that those
properties
- can be applied to things like checkstyle and to create a document
- outlining the coding specification.
- </li>
- <li>
- Specification of the license used so a standard page can be
- generated.
- </li>
</ul>
</p>
</section>
+
</body>
</document>
