prevents attribute name to be humanized

Without the :default => false, the method's super implementation will
use attribute_name.to_s.humanize as a last resort. This will prevent an
error from beeing raised which will render the rescue statement added
for backwards compatibility useless.

Adding the fix will lead to a lot of warnings. But hey, that will lead
to a faster adaptation of the new standard.
Merge pull request #78 from opf/feature/rails3_disable_default_attribute_name

prevents attribute name to be humanized
remove old-style sample plugin
Merge branch 'feature/rails3' of github.com:opf/openproject into feature/rails3
it's possible again to delete attachments
remove verify in attachment_controller

the new rails routes take care of the method type verification
Merge pull request #80 from opf/feature/rails3_delete_attachments

it's possible again to delete attachments
Merge branch 'feature/rails3' into feature/rails3_broken_links_in_deep_neested_pages

Conflicts:
	extra/sample_plugin/app/models/meeting.rb
	extra/sample_plugin/init.rb