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 05:02:14 UTC
cvs commit: jakarta-turbine-maven/xdocs musings.xml
jvanzyl 2003/02/12 20:02:14
Modified: xdocs musings.xml
Log:
o removing dead entries and items that have been implemented.
Revision Changes Path
1.32 +1 -51 jakarta-turbine-maven/xdocs/musings.xml
Index: musings.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/musings.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- musings.xml 1 Oct 2002 12:30:02 -0000 1.31
+++ musings.xml 13 Feb 2003 04:02:14 -0000 1.32
@@ -20,21 +20,6 @@
the development of the AspectJ compiler.
</li>
<li>
- Repository log analyzer. Right now we have Juan's RCS file parser so
- what would be the best way to leverage that tool. It would be great
- to have graphs of the the activity to see where the hot spots are
- in the project's development.
- </li>
- <li>
- Integrate JRefactory to do some source formatting according to a
- given style. It would be nice to integrate the way checkstyle,
- JRefactory and other tools like that work from some sort of
- source definition. I believe the project object model can
- store this information and we can make little adapters to
- work with the various configuration file formats for the
- various tools that are available for use.
- </li>
- <li>
The integration of Quilt.
David Peugh's is working on this and Quilt is available
<a href="http://quilt.sourceforge.net/">here</a>.
@@ -52,10 +37,6 @@
Find all unreferenced files in a project so that developers know
where the dead code is.
</li>
- <li>
- Have a set of indicators for cvs entries you don't want displayed in
- the generated cvs log xdoc
- </li>
<li>
When doing large builds consult .cvspass in order to find overriding
values. at least make this the default. We want it to be easy for
@@ -75,10 +56,6 @@
of profiles looking for problems.
</li>
<li>
- Integrate a simple link checker for the generated site so that
- it is internally consistent.
- </li>
- <li>
We need an easy way to access information from the project descriptor
and we can't assume that the source of the information is an XML
file. We should access the object model directly. We would like to
@@ -109,9 +86,7 @@
example to start from.
</li>
<li>
- Integration with Scarab, how to make setting up Scarab easy for
- users of Maven. We don't need a separate patch processing tool
- now that we can use Scarab.
+ Integration with various issue tracking systems.
</li>
<li>
Integration with Eyebrowse.
@@ -163,37 +138,12 @@
link entries in the glossary can be used.
</li>
<li>
- A contribution registry: for Fulcrum this might be a registry of
- services, for Torque this might be a registry of ID generation
- strategies. But cataloging these entries easily and having
- them be indexed.
- </li>
- <li>
- Automate announcements to the big sites.
- </li>
- <li>
Automate the archiving of the mail to mail-archive.com or
at least provide instructions on what to do.
</li>
<li>
- Create a project descriptor validator for models stored in
- XML format.
- </li>
- <li>
Standard JavaCC pattern. Maven, Lucene, Jython all need something
like this and now that JavaCC is OSS it will be even easier!
- </li>
- <li>
- Need a tool to help people easily make a project descriptor. A
- wizard type tool to make things as clear, and error free as
- possible (berin).
- </li>
- <li>
- Integrate jdiff (http://jdiff.sourceforge.net) into Maven.
- Looks like it could be really cool to integrate release
- differences reports, so that each release could easily (i.e.
- automatically) document how the API changed from the previous
- release. (suggested by jstrachan)
</li>
<li>
Consider introducing an XML FAQ format for Maven builds. Right now the FAQ