You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by jv...@apache.org on 2003/02/13 04:25:01 UTC
cvs commit: jakarta-turbine-maven/xdocs tasks.xml
jvanzyl 2003/02/12 19:25:01
Modified: xdocs tasks.xml
Log:
o updating tasks.
Revision Changes Path
1.39 +25 -49 jakarta-turbine-maven/xdocs/tasks.xml
Index: tasks.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/tasks.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- tasks.xml 22 Jan 2003 17:53:37 -0000 1.38
+++ tasks.xml 13 Feb 2003 03:25:00 -0000 1.39
@@ -11,41 +11,44 @@
<p>
</p>
- <subsection name="Beta 8">
+ <subsection name="Beta 9">
<p>
- <ul>
- <li>
- Reports incorrectly produced
- </li>
- <li>
- Failed downloads not stopping the build process
- </li>
- <li>
- Release plugin
- </li>
- </ul>
+ Try to fix as many issues as possible and get the documentation up to scratch. We
+ are going to try and get this release out sooner rather than later.
</p>
- </subsection>
+ </subsection>
- <subsection name="Beta 9">
+
+ <subsection name="Beta 10">
<p>
<ul>
<li>
- Switch to classworlds
+ Implement arbitrary artifact type handling. Michal Maczka (Mmaczka@cqs.ch)
+ had a very good solution but we didn't get around to getting it
+ in. Sorry about that Michal, please be patient.
+ </li>
+ <li>
+ Switch to classworlds to allow real isolation in plugins and real
+ embedding of Maven in client applications. This will all revolve around
+ allowing a ClassWorld to be initialized with MavenSession. We would truly
+ like to decouple MavenSession from the CLI front-end. Possibly using a
+ system property to pass in a set of JARs to populate the initial ClassWorld.
+ From there we can create child ClassWorlds for the plugins to execute in.
</li>
<li>
Add the use of checksums in the verification process. Throw an
ArtifactCorruptionException when the the artifact cannot be
- verified against the checksum.
+ verified against the checksum. This mechanism has been implmented, but
+ we were having problems getting the checksums up to ibiblio reliably. We need
+ to thoroughly test the Jelly script that we are using for deployment and we
+ could probably also do with the shell scripts that can be run periodically
+ on repositories to make sure the checksums are valid.
</li>
<li>
- Use the property javadoc tags in the POM hierarchy to generate
- documentation for POM entries and the XSD. We can use vdoclet
- which has proven an invaluable tool.
- </li>
- <li>
Release vs HEAD website (so the inconsistencies we have in our
- current situation can be alleviated.
+ current situation can be alleviated. This is a real problem that needs
+ to be solved. We simply need a way to flag an incremental HEAD site
+ update as opposed to a release update.
</li>
<li>
Addition of POM entries to allow anonymous checkout
@@ -83,36 +86,9 @@
file similar to the jars.list. A plugin is packaged as a jar file.
</li>
<li>
- All plugins must provide intense sizzle, be goal-oriented, cooperate
- in a plug & play manner, and optionally provide a powerpoint
- presentation describing their management potential.
- </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>
- 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>
- Template for usecases.
- </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