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/02/24 15:39:37 UTC
cvs commit: jakarta-turbine-maven/xdocs NOTES
jvanzyl 02/02/24 06:39:37
Added: xdocs NOTES
Log:
- more blurbs
Revision Changes Path
1.1 jakarta-turbine-maven/xdocs/NOTES
Index: NOTES
===================================================================
. figure out how to specify that aspects are required. i would like
to be able to make a huge reactor that the aspectj team can use to watch
the development of ajc.
. possibly incorporate gretel, looks similiar to quilt.
http://www.cs.uoregon.edu/research/perpetual/dasada/Software/Gretel/
. how to easily extend the build system for project specifics, we don't
want people editing the generated build system. has to be easy and clear.
. have to figure out the structure for a jar repository and the naming
conventions.
. separate the test inputs from the test classes, makes the include/exclude
patterns much easier to deal with
. encourage the use of a central repository of JARs -> ${lib.repo}
. object model for a java project
the project is the unit of work for alexandria and that's
the idea we want to stress.
. cvs log analyser
. build tool
. updater
. cross referencer
. source formatter
. make something like webgain's Quality Analyser
. audit
. cover (david peugh's quilt)
. metrics (easy enough with the java parser)
. indexing tool for javadocs. search the repositories for code
that might be useful.
. graphs for cvs activity
. source metrics
. tool for taking patches
. updating tool
. installer help (webstart/jnlp)
. integrate ceki's dir layout
. integrate berin's build file
. standard location for libs versus distributions
. javadoc viewer
. make the tools easily integrated into cvs
. lxr finding all the source files that use a particular file.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>