… grained (down from SvnRevision to SvnNode).

* Move TerminatingValidator out of test source into main source, as it might be useful.

…ing.

… having the Consumer do that.

* SvnDumpFileParser will not add nodes to an SvnRevision, as those should be consumed separately.
* Update SvnDumpWriterImpl and SvnDumpInMemory to work with this new way.

…ad of getting the SvnDump as a whole.

* Previously, this was implemented as a separate class, ConsumerChain.
* Because of the granularity changes to SvnDumpFileParser to parse SvnNodes separately from their SvnRevision, many SvnDumpConsumers can no longer properly operate.
* Instead of teaching the ConsumerChain how to represent and handle SvnNode additions/deletions that may come from an SvnDumpMutator, I'm teaching SvnDumpConsumers how to chain to each other.
* This removes the need for a separate ConsumerChain class.
* This also places the burder of continuing the consumer chain on each consumer, which is a downside of this approach.

…rForEmptyRevisions to properly chain.

…ded in SvnDumpFileParserTest.consume

…ependently from other nodes in the revision.

* This means we don't have to hold all the nodes in memory at the same time, just one node.
* This should fix the "SvnRevision >30GB" requirement.

* We're going to split up the file content of SvnNodes into smaller pieces, so that we don't have to store the entire file content in memory.

* Add ending calls to SvnDumpConsumer: endRevision(...), endNode(...), and endChunks().  Makes SvnDumpWriterImpl code much cleaner and clearer.

…fixes #5.

* You can change the chunk size by calling setFileContentChunkSize(long) on the SvnDumpFileParser.