This will cause the class to run acts_as_journal which will create the
Journal sub-classes and prevent uninitialized constants since the sub-classes
are created on the fly.

If the Journal or the Journaled object don't save successfully,
put out the reasons why instead of aborting the migrations. Journaled
objects might failure from the :touch update, which are safe to ignore.

Contributed by MAEDA, Go

Contributed by Artem Naluzhnyy

Some models (Changeset) require custom options passed to
acts_as_activity_provider but acts_as_journalized wasn't accepting these
for :timestamp or :author_key

This will let them pick up the committer string if user is nil

Was due to Journals touching the parent record but the Journal
not having it's STI class correct during the type update.

Contributed by Artem Naluzhnyy.

Contributed by Artem Naluzhnyy.

Contributed by Artem Naluzhnyy.

Getting rid of "rake/rdoctask is deprecated." warning. #477

works with all rdoc versions since 2.4.2
see https://github.com/rdoc/rdoc/blob/master/History.txt

https://www.chiliproject.org/projects/chiliproject/wiki/HowTo_Release

Conflicts:
	test/unit/journal_test.rb