Re: [jdee-devel] Suggestions for replacement of legacy revision documentation
Brought to you by:
paullandes
From: David B. <dav...@gm...> - 2009-08-02 10:43:42
|
Maven builds support both of those goals. I'd take a look at http://maven.apache.org/plugins/maven-changelog-plugin/ And: http://maven.apache.org/guides/mini/guide-site.html You'd have to convert to maven, I imagine that would involve removing a lot the existing ant build.xml. Maybe more than you want take on. -Dave On Aug 2, 2009, at 1:55 AM, Paul Landes <la...@ma...> wrote: > Currently the revision documentation is nested in the emacs comments > at the ends of each Emacs Lisp source code file. I'd like to remove > these comments and move them to an XML file or some such thing. Then > in the Ant build could use an XSLT transform to create an HTML > document that folds into the standard documentation for the site. > This last part (a site documentation generation) is a more long term > goal. > > So the way I see it, we'd have two parts: > > - Add the Emacs Lisp to some data format file that's easy to parse in > either Java or Emacs land (XML or Emacs symbol expressions). > > - Integrate subversion commit comments to add to the legacy comments > to create the cumulative revision history in human readable format. > > I'm sure this is a problem that has been solved many times. > > Thanks all. > > -- > Paul Landes > la...@ma... > > --- > --- > --- > --------------------------------------------------------------------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > jdee-devel mailing list > jde...@li... > https://lists.sourceforge.net/lists/listinfo/jdee-devel |