You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2002/03/30 16:27:09 UTC
cvs commit: jakarta-turbine-maven/xdocs index.xml tasks.xml
jvanzyl 02/03/30 07:27:09
Modified: xdocs index.xml tasks.xml
Log:
Updating the task list.
Revision Changes Path
1.8 +2 -2 jakarta-turbine-maven/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/index.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- index.xml 30 Mar 2002 00:36:29 -0000 1.7
+++ index.xml 30 Mar 2002 15:27:09 -0000 1.8
@@ -34,14 +34,14 @@
</p>
</section>
- <subsection name="The Big Picture">
+ <section name="The Big Picture">
<p>
The intent of Maven is to make intra-project development highly manageable
in the hopes of providing more time for cross-project development. You
might call it cross-project pollenation or the sharing of project
development knowledge, this is what Maven attempts to encourage.
</p>
- </subsection>
+ </section>
</body>
</document>
1.2 +41 -1 jakarta-turbine-maven/xdocs/tasks.xml
Index: tasks.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/tasks.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tasks.xml 29 Mar 2002 17:11:00 -0000 1.1
+++ tasks.xml 30 Mar 2002 15:27:09 -0000 1.2
@@ -10,7 +10,47 @@
<section name="Tasks">
<p>
<ul>
- <li> checkstyle integration (warner) </li>
+ <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>
+ Move the JUnit testing in the direction of using source references
+ and not class references. With our current method we have to explicity
+ exclude inner classes and the core classes are mixed in with the test
+ classes which forces the inclusion of core classes (as opposed to
+ explicit JUnit tests) matching the filters in the JUnit batch tests.
+ </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)
+ </li>
+ <li>
+ Write a proposal for the standard naming of JAR files and implement
+ prototype with Maven for demonstration. (jvz)
+ </li>
+ <li>
+ Maven 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
+ to choose the changes when they wish and have the changes
+ transparently applied.
+ </li>
+ <li>
+ Checkstyle integration (warner)
+ </li>
+ <li>
+ Copy the jarResources elements during the maven:compile phase. (dIon)
+ </li>
+
<li> dep graph (jvz)</li>
<li> maven:deploy-dist needs to work (jvz)</li>
<li> schema for project.xml (jvz)</li>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>