forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: cvs commit: xml-forrest/src/documentation/content/xdocs your-project.xml
Date Sat, 23 Nov 2002 13:43:20 GMT

Jeff Turner wrote:
> On Sat, Nov 23, 2002 at 01:59:09PM +0100, Nicola Ken Barozzi wrote:
> ...
> 
>>> -    <version>1.0</version>
>>> +    <version>$Revision$</version>
>>
>>The above includes the revision.
>>
>>It's also possible to include all CVS commits in the file, and we could 
>>add a <cvslog> </cvslog> section that gets transformed into xml and used

>>as revision info.
>>
>>Below is an example in a real build.xml file.
>>
>>This is just a RT, FYI.
>>
>><!--
>>$Id: build.xml,v 1.7 2002/11/16 13:52:47 nicolaken Exp $
>>
>>$Log: build.xml,v $
>>Revision 1.7  2002/11/16 13:52:47  nicolaken
>>Added a "gump" target that adds a datestamped jar to the build dir for 
>>Forrest
>>jar publishing.
>>
>>Revision 1.6  2002/11/04 00:33:17  chalko
>>Increased version to 0.5-beta1
> 
> ....
> 
> That's an interesting idea..
> 
> If we had something that could parse the log format and generate SAX
> events, we could style the contents of <cvslog> into HTML.
> 
> Might be possible with Simon St.Laurent's "regular fragmentations"
> filter:
> 
> http://regfrag.sourceforge.net/
> 
> Maybe it could be done with chaperon.. don't know.

There is a task in Ant that does things with the changelog.
Maybe it's usefull... I don't have time to hack on it now, just a note.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Mime
View raw message