You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by ka...@apache.org on 2002/02/24 21:00:18 UTC
cvs commit: jakarta-turbine-maven/xdocs musings.xml project.xml
kaz 02/02/24 12:00:18
Modified: xdocs project.xml
Added: xdocs musings.xml
Log:
Converted NOTES to an xdoc and added link to site.
Revision Changes Path
1.10 +1 -0 jakarta-turbine-maven/xdocs/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/project.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- project.xml 24 Feb 2002 15:37:33 -0000 1.9
+++ project.xml 24 Feb 2002 20:00:17 -0000 1.10
@@ -21,6 +21,7 @@
<menu name="Development">
<item name="Building" href="/bootstrap.html"/>
<item name="Dependencies" href="/dependencies.html"/>
+ <item name="Musings" href="/musings.html"/>
<item name="JavaDocs" href="/apidocs/index.html"/>
<item name="Source XReference" href="/xref/index.html"/>
</menu>
1.1 jakarta-turbine-maven/xdocs/musings.xml
Index: musings.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="pete@kazmier.com">Pete Kazmier</author>
<author email="jason@zenplex.com">Jason van Zyl</author>
<title>Musings</title>
</properties>
<body>
<section name="Musings">
<p>
The following is a list of things that are being contemplated
for Maven.
</p>
<ul>
<li>
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.
</li>
<li>
possibly incorporate gretel, looks similiar to quilt.
http://www.cs.uoregon.edu/research/perpetual/dasada/Software/Gretel/
</li>
<li>
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.
</li>
<li>
have to figure out the structure for a jar repository and the naming
conventions.
</li>
<li>
separate the test inputs from the test classes, makes the include/exclude
patterns much easier to deal with
</li>
<li>
encourage the use of a central repository of JARs -> ${lib.repo}
</li>
<li>
object model for a java project
</li>
<li>
the project is the unit of work for alexandria and that's
the idea we want to stress.
</li>
<li>
cvs log analyser
</li>
<li>
build tool
</li>
<li>
updater
</li>
<li>
cross referencer
</li>
<li>
source formatter
</li>
<li>
make something like webgain's Quality Analyser
</li>
<li>
audit
</li>
<li>
cover (david peugh's quilt)
</li>
<li>
metrics (easy enough with the java parser)
</li>
<li>
indexing tool for javadocs. search the repositories for code
that might be useful.
</li>
<li>
graphs for cvs activity
</li>
<li>
source metrics
</li>
<li>
tool for taking patches
</li>
<li>
updating tool
</li>
<li>
installer help (webstart/jnlp)
</li>
<li>
integrate ceki's dir layout
</li>
<li>
integrate berin's build file
</li>
<li>
standard location for libs versus distributions
</li>
<li>
javadoc viewer
</li>
<li>
make the tools easily integrated into cvs
</li>
<li>
lxr finding all the source files that use a particular file
</li>
</ul>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>