commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james_strac...@yahoo.co.uk>
Subject [general] Should maven projects still use STATUS.html? (was Re: cvs commit: jakarta-commons-sandbox/jelly STATUS.html)
Date Thu, 10 Oct 2002 12:11:19 GMT
:-). This brings up an interesting point I've been meaning to get around to
asking for some time.

Much of the information thats expected in the original PROPOSAL.html and
STATUS.html is actually inside the Maven descriptor (dependencies, aim,
committers, versions etc). Should we decide only the missing pieces required
for Maven generated sites and just document those? Or we could generate the
STATUS.html and PROPOSAL.html from the project.xml descriptor?

I just wanna avoid both stale documentation, unnecessary work and dual
keying.

James
-------
http://radio.weblogs.com/0112098/
----- Original Message -----
From: <morgand@apache.org>
To: <jakarta-commons-sandbox-cvs@apache.org>
Sent: Wednesday, October 09, 2002 10:00 PM
Subject: cvs commit: jakarta-commons-sandbox/jelly STATUS.html


> morgand     2002/10/09 14:00:52
>
>   Added:       jelly    STATUS.html
>   Log:
>   adding required STATUS.html doc and myself as contributor, because I
>   am patch-challenged :)
>
>   Revision  Changes    Path
>   1.7       +20 -57    jakarta-commons-sandbox/jelly/STATUS.html
>
>
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:commons-dev-help@jakarta.apache.org>
>

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message