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

Multiple records were found and postgres was returning them in a different
order than what the test assumed.

So the initial journal would have the changes from an Object#new
to the created version of the Object. Also includes a change to the
database migration in order to create these initial journals for
all journaled Objects.

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3635 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5375 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5373 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5371 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5370 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5368 e93f8b46-1217-0410-a6f0-8f06a7374b81

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5367 e93f8b46-1217-0410-a6f0-8f06a7374b81

In one case in a plugin (not able to reproduce in core) journal_attributes_for_user
would set the :user to something different than what's in updated_by thus assigning
the Journal to the wrong user.