Upgraded Blacklight to post-4.4 branch 'issue-620' in order to get code in https://github.com/projectblacklight/blacklight/commit/c2a85b2bd634d3bbce8eed0b56cc5ab52661c30f.
Added ObjectsController
Fixed customized #link_to_document helper in BlacklightHelper
Added initial objects routes
Refactored ActiveFedora::Base decorator
Added test for ObjectsController
Added pending tests for objects show view
Removed cruft - mostly unused catalog partials

Removed commented-out authorize! lines

Changed :class_name to 'ActiveFedora::Base' for compatibility with active-fedora 6.4.4+
which effectively requires the :class_name argument to refer to an ActiveFedora model
(ActiveFedora::Base or subclass) and not a module.
See https://github.com/projecthydra/active_fedora/commit/8ac538eb4442bde23e561735e00d28ff50d55744.

Fixed path helper calls in test

Updated hydra-head to 6.4.0.rc4
Updated active-fedora to 6.6.0.rc4

Update hydra-head to 6.4.0.rc4
Update active-fedora to 6.6.0.rc4
Merge pull request #270 from duke-libraries/objects-controller

One test failed on Ruby 1.9.3:

Failures:
  1) DulHydra::Batch::Scripts::BatchProcessor ingest successful ingest behaves like a successful ingest batch should add the objects to the repository, validate them, and have an appropriate batch run record
     Failure/Error: before { bp.execute }
     Errno::ECONNREFUSED:
       Connection refused - connect(2)
     Shared Example Group: "a successful ingest batch" called from ./spec/scripts/batch_processor_spec.rb:69
     # ./lib/dul_hydra/batch/scripts/batch_processor.rb:127:in `send_notification'
     # ./lib/dul_hydra/batch/scripts/batch_processor.rb:46:in `execute'
     # ./spec/scripts/batch_processor_spec.rb:59:in `block (3 levels) in <module:Scripts>'
Finished in 7 minutes 50.61 seconds
347 examples, 1 failure, 20 pending
Failed examples:
rspec ./spec/scripts/batch_processor_spec.rb:11 # DulHydra::Batch::Scripts::BatchProcessor ingest successful ingest behaves like a successful ingest batch should add the objects to the repository, validate them, and have an appropriate batch run record