Announce: 20061230 release of FitLibrary in Java for FitNesse

That's available at https://sourceforge.net/projects/fitlibrary/

This release includes some new new capability and a fix. Changes include
the following. See the UserGuide included in the download zip file for
further details.

 * FitLibrary now enables debugging when running storytests.
 * CompareFileFixture now handles absolute file names as well as
relative file names.
 * An empty tables cell may be interpreted as follows, depending on what
value the cell is expected to hold:
  * An empty list, set, array, map
  * A null value for an object, including Integer, etc
 * FitLibrary accesses private getter/setters for properties. This
allows for setter injection without generally exposing properties.
 * FitLibrary accesses private nullary constructors. This allows for
object creation without generally exposing the constructor.
 * Use of HR to separate phases of DomainFixture
 * The method that is called for a calculation rules may return an
object that's a subtype of the declared return type of the method. The
actual type of the result is used to check it against the expected value
 * Fixed problem with a startUp() method being called more than once for
suite fixtures, etc.
 * Lots of storytests have been added to check that exceptions are
caught correctly and nulls are handled correctly
 * Experimental feature: If it exists, the method startCreatingObject()
of a domain adapter or sut is called when DomainFixture (and other
fixtures) automatically create an object; the object is passed as an
argument. This allows for specialised setup of the object before it has
property values automatically injected into it. The corresponding method
endCreatingObject() is called at the end of automatic injection.
 * Experimental feature: A parse delegate may be specified for any type,
and so will be override any provided Parser for that type for the
duration of the storytest concerned.
 * Experimental feature: A revised mechanism for supporting polymorhism
is included. I will later add support for tailoring the way that the
type is specified in the table.  The documentation is still to be completed.
 * Only relevant to those who write their own fixtures: The
interpretation cycle passes extra type information; this is used in
FitLibrary2 to track the generic types of objects (which is missing at
runtime, due to ''erasure'' in Java). The way that Parsers are selected
has been changed considerably. Some class names have been changed, and
the package structure has changed in minor ways. FitLibraryServer has
changed considerably.

Cheers, Rick