Lots of changes: CVS log, release notes, change logs

The jde/lisp/ChangeLog has been removed.  It had the same information
as the $Log$ entries in each emacs lisp file but was just in a
different format.

I've moved all of the $Log$ entries in each emacs lisp file to
jde/doc/history/cvs-revision-log.xml, which is in subversion log xml
format.  My current plan is to write a transform that creates HTML
output that is easier on the eyes than a ChangeLog.  If someone loves
ChangeLog, they can write a transform or munge the previously
mentioned svn2cl.xsl, but that isn't my priority.

Once the transform is complete, an XSLT task will be invoked from ant
to create the HTML documentation in the history directory from both
the cvs-revision-log.xml and (append on) the svn log output.  This is
one of the many steps I'm trying to get to to generate a complete
documentation site from a build (much like the apache projects).

It's possible that the old ChangeLog also had changes from other files
like the Java source, but I think those changes are less important for
now, and we can go back and do that at a later time as we can reuse
what I wrote for the emacs lisp code (doc/history/jde-log.el).

--

I realize the files in jde/doc/history and really jde/doc in general don't
seem organized, but we aren't to a point to where it makes a
difference.

--

Also, the jde/lisp/ReleaseNotes.txt is now in jde/doc/history for the
same reasons and I've started it's replacement:
jde/doc/history/release-notes.xml.  It currently has a few entries
more for just example, but I'd like *only large changes* to be added
to this file.  This is really more of a big changes or feature set
that is put out with each new release.

Like the svn log XML files, this will also have a transform (albeit a
different .xsl file) to generate more HTML output.

--

I have also added $Id$ tags to all the emacs lisp files and have run
`whitespace-cleanup' to change all spaces to tabs (think `tabify').
It also gets rid of trailing space.

--

There are a LOT of changes and I wouldn't be surprised if something
broke in the process.  That said, I did do a good deal of testing
before committing at each interval.

Let me know if you have any questions or conerns.

-- 
Paul Landes
[email protected]

------------------------------------------------------------------------------
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