active-fedora 12.0.3 → 12.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 74801c6b7c20e589016a06beb4bfb08b5cae15c8d2c9da1d3b90ba31da494b93
-  data.tar.gz: 3ba72febc4344898aedc515c07eea090bffe96748a5bab209745f0306e8cf5f9
+  metadata.gz: 363d470665c889210749fbfda14d9af3ef74fccdcf317ae0c57be7d5faba7391
+  data.tar.gz: 7898ead9d053ebb747d4d6c3897b9d230f69051dc8b000d4a234bd024034ac4b
 SHA512:
-  metadata.gz: 703f5492c6bf6b23c2c343d0a24039b15b2b7f02976d1603c8a49a12afc00eec10079da508e668e8dfca84bc63065e09f43b95441723326ef233d20d32489c8d
-  data.tar.gz: a0f39c00a6ef9a78c9f81fd96c364244e970a64ae8da4c706cb3052c26acfd3bf2f782bb2d0421cb1702f54176c38311081c03cc33530e0eb92411c9b3ce95e2
+  metadata.gz: e93ea3410149be925080cf7779aa7e6188ea4389d23325f1c726f91dcb7802ddc1d5d158372e8c688c8c750350b1e0208c8b29748f7961219991b1213664eda8
+  data.tar.gz: db58fd4a0d54261ac57befb1f8bcab0906b7fa83ab15ddce064b129e028cee8807ee247795461c195d6a02f9a82c4741e078e633b550e6aff1c91d82a28b38cf

data/.rubocop.yml

@@ -98,7 +98,7 @@ Metrics/ClassLength:
 Metrics/MethodLength:
   Enabled: false
 
-Style/MethodName:
+Naming/MethodName:
   Exclude:
     - 'lib/active_fedora/with_metadata.rb'
 
@@ -106,7 +106,7 @@ Style/AndOr:
   Exclude:
     - 'lib/active_fedora/associations/has_many_association.rb'
 
-Style/AccessorMethodName:
+Naming/AccessorMethodName:
   Exclude:
     - 'lib/active_fedora/with_metadata/metadata_node.rb'
     - 'lib/active_fedora/fedora_attributes.rb'
@@ -114,7 +114,7 @@ Style/AccessorMethodName:
     - 'lib/active_fedora/associations/has_many_association.rb'
     - 'lib/active_fedora/associations/association.rb'
 
-Style/PredicateName:
+Naming/PredicateName:
   Exclude:
     - 'lib/active_fedora/attribute_methods.rb'
     - 'lib/active_fedora/relation/finder_methods.rb'
@@ -156,11 +156,11 @@ Style/BlockDelimiters:
   Exclude:
     - 'spec/**/*'
 
-Style/BlockEndNewline:
+Layout/BlockEndNewline:
   Exclude:
     - 'spec/**/*'
 
-Style/MultilineBlockLayout:
+Layout/MultilineBlockLayout:
   Exclude:
     - 'spec/**/*'
 
@@ -172,7 +172,7 @@ Style/Lambda:
   Exclude:
     - 'spec/**/*'
 
-Style/IndentationConsistency:
+Layout/IndentationConsistency:
   EnforcedStyle: rails
 
 Style/CollectionMethods:
@@ -215,7 +215,7 @@ Style/ClassVars:
 Style/SignalException:
   Enabled: false
 
-Style/FileName:
+Naming/FileName:
   Exclude:
     - 'lib/active-fedora.rb'
 

data/.rubocop_todo.yml

@@ -1,110 +1,20 @@
 # This configuration was generated by
 # `rubocop --auto-gen-config`
-# on 2017-02-28 19:30:31 -0600 using RuboCop version 0.47.1.
+# on 2018-05-16 14:10:19 -0500 using RuboCop version 0.56.0.
 # The point is for the user to remove these configuration records
 # one by one as the offenses are removed from the code base.
 # Note that changes in the inspected code, or installation of new
 # versions of RuboCop, may require this file to be generated again.
 
-# Offense count: 211
-# Configuration parameters: CountComments, ExcludedMethods.
-Metrics/BlockLength:
-  Max: 577
-
-# Offense count: 65
-RSpec/BeforeAfterAll:
-  Enabled: false
-
-# Offense count: 114
-# Configuration parameters: Max.
-RSpec/ExampleLength:
-  Enabled: false
-
-# Offense count: 15
-RSpec/LetSetup:
-  Exclude:
-    - 'spec/integration/collection_association_spec.rb'
-    - 'spec/integration/delete_all_spec.rb'
-    - 'spec/integration/has_many_associations_spec.rb'
-    - 'spec/integration/nested_attribute_spec.rb'
-    - 'spec/integration/persistence_spec.rb'
-    - 'spec/unit/has_and_belongs_to_many_association_spec.rb'
-
 # Offense count: 1
-RSpec/MessageChain:
-  Exclude:
-    - 'spec/unit/file_spec.rb'
-
-# Offense count: 241
-RSpec/MultipleExpectations:
-  Max: 8
-
-# Offense count: 181
-# Configuration parameters: Max.
-RSpec/NestedGroups:
-  Enabled: false
-
-# Offense count: 24
-RSpec/ScatteredSetup:
-  Exclude:
-    - 'spec/integration/base_spec.rb'
-    - 'spec/integration/direct_container_spec.rb'
-    - 'spec/integration/has_and_belongs_to_many_associations_spec.rb'
-    - 'spec/integration/indexing_spec.rb'
-    - 'spec/integration/indirect_container_spec.rb'
-    - 'spec/integration/json_serialization_spec.rb'
-    - 'spec/unit/attached_files_spec.rb'
-    - 'spec/unit/base_spec.rb'
-    - 'spec/unit/loadable_from_json_spec.rb'
-    - 'spec/unit/rdf/indexing_service_spec.rb'
-
-# Offense count: 94
-RSpec/SubjectStub:
-  Exclude:
-    - 'spec/integration/associations_spec.rb'
-    - 'spec/integration/autosave_association_spec.rb'
-    - 'spec/integration/versionable_spec.rb'
-    - 'spec/unit/attached_files_spec.rb'
-    - 'spec/unit/base_extra_spec.rb'
-    - 'spec/unit/file_configurator_spec.rb'
-    - 'spec/unit/file_spec.rb'
-    - 'spec/unit/has_and_belongs_to_many_association_spec.rb'
-    - 'spec/unit/persistence_spec.rb'
-    - 'spec/unit/solr_config_options_spec.rb'
-    - 'spec/unit/validations_spec.rb'
-
-# Offense count: 20
-# Configuration parameters: IgnoreSymbolicNames.
-RSpec/VerifiedDoubles:
-  Exclude:
-    - 'spec/unit/association_hash_spec.rb'
-    - 'spec/unit/files_hash_spec.rb'
-    - 'spec/unit/query_spec.rb'
-    - 'spec/unit/schema_indexing_strategy_spec.rb'
-    - 'spec/unit/solr_config_options_spec.rb'
-    - 'spec/unit/solr_service_spec.rb'
-
-# Offense count: 3
-Rails/FilePath:
+# Cop supports --auto-correct.
+# Configuration parameters: PreferredDelimiters.
+Style/PercentLiteralDelimiters:
   Exclude:
-    - 'lib/active_fedora/file_configurator.rb'
-    - 'spec/unit/file_configurator_spec.rb'
+    - 'Rakefile'
 
-# Offense count: 2
-Security/MarshalLoad:
-  Exclude:
-    - 'spec/integration/marshal_spec.rb'
-
-# Offense count: 20
-# Configuration parameters: MinBodyLength.
-Style/GuardClause:
-  Enabled: false
-
-# Offense count: 20
-# Configuration parameters: EnforcedStyle, SupportedStyles.
-# SupportedStyles: snake_case, normalcase, non_integer
-Style/VariableNumber:
-  Exclude:
-    - 'spec/integration/associations_spec.rb'
-    - 'spec/unit/ordered_spec.rb'
-    - 'spec/unit/orders/ordered_list_spec.rb'
+# Offense count: 1
+# Configuration parameters: AllowHeredoc, AllowURI, URISchemes, IgnoreCopDirectives, IgnoredPatterns.
+# URISchemes: http, https
+Metrics/LineLength:
+  Max: 82

data/.travis.yml

@@ -0,0 +1,21 @@
+language: ruby
+cache: bundler
+sudo: false
+rvm: 2.4
+matrix:
+  include:
+    - rvm: 2.3
+      env: RAILS_VERSION=4.2.10
+           BUNDLER_VERSION=1.17.3
+    - env: RAILS_VERSION=5.0.7
+    - env: RAILS_VERSION=5.1.6
+    - rvm: 2.5
+    - env: RAILS_VERSION=5.2.1
+    - rvm: 2.6
+global_env:
+  - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
+before_install:
+  - gem update --system
+  - if [ ! -z $BUNDLER_VERSION ]; then gem install bundler -v $BUNDLER_VERSION; else gem install bundler; fi
+before_script:
+  - jdk_switcher use oraclejdk8

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+The Samvera community is dedicated to providing a welcoming and
+positive experience for all its members, whether they are at a formal
+gathering, in a social setting, or taking part in activities online.
+The Samvera community welcomes participation from people all over the
+world and these members bring with them a wide variety of
+professional, personal and social backgrounds; whatever these may be,
+we treat colleagues with dignity and respect.
+
+Community members communicate primarily in English, though for many of
+them this is not their native language. We therefore strive to express
+ourselves simply and clearly remembering that unnecessary use of
+jargon and slang will be a barrier to understanding for many of our
+colleagues.  We are sensitive to the fact that the international
+nature of the community means that we span many different social norms
+around language and behaviour and we strive to conduct ourselves,
+online and in person, in ways that are unlikely to cause offence.
+
+Samvera conversations are often information-rich and intended to
+generate discussion and debate.  We discuss ideas from a standpoint of
+mutual respect and reasoned argument.
+
+Community members work together to promote a respectful and safe
+community. In the event that someone’s conduct is causing offence or
+distress, Samvera has a detailed
+[Anti-Harassment Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+which can be applied to address the problem. The first step in dealing
+with any serious misconduct is to contact a local meeting organizer,
+the
+[Samvera community helpers](https://wiki.duraspace.org/display/samvera/Samvera+Community+Helpers)
+([email](mailto:helpers@samvera.org)), a community member you
+trust, or the
+[Samvera Steering Group](https://wiki.duraspace.org/display/samvera/Samvera+Steering+Group+membership)
+immediately; at Samvera events, these people can be identified by
+distinctive name badges. The
+[Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+should be consulted for fuller details.

data/CONTRIBUTING.md

@@ -1,21 +1,24 @@
 # How to Contribute
 
-We want your help to make Project Hydra great.
-There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
+We want your help to make the Samvera community great. There are a few guidelines
+that we need contributors to follow so that we can have a chance of
+keeping on top of things.
 
 ## Code of Conduct
 
-The Hydra community is dedicated to providing a welcoming and positive experience for all its
-members, whether they are at a formal gathering, in a social setting, or taking part in activities
-online.  Please see our [Code of Conduct](https://wiki.duraspace.org/display/hydra/Code+of+Conduct)
-for more information.
+The Samvera Community is dedicated to providing a welcoming and positive
+experience for all its members, whether they are at a formal gathering, in
+a social setting, or taking part in activities online. Please see our
+[Code of Conduct](CODE_OF_CONDUCT.md) for more information.
 
-## Hydra Project Intellectual Property Licensing and Ownership
+## Samvera Community Intellectual Property Licensing and Ownership
 
-All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Hydra Project Steering Group.
-If the contributor works for an institution, the institution must have a Corporate Contributor License Agreement (cCLA) on file.
+All code contributors must have an Individual Contributor License Agreement
+(iCLA) on file with the Samvera Steering Group. If the contributor works for
+an institution, the institution must have a Corporate Contributor License
+Agreement (cCLA) on file.
 
-https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership
+https://wiki.duraspace.org/display/samvera/Samvera+Community+Intellectual+Property+Licensing+and+Ownership
 
 You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.
 
@@ -31,7 +34,7 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 ### Reporting Issues
 
 * Make sure you have a [GitHub account](https://github.com/signup/free)
-* Submit a [Github issue](./issues) by:
+* Submit a [Github issue](https://github.com/samvera/active_fedora/issues) by:
   * Clearly describing the issue
     * Provide a descriptive summary
     * Explain the expected behavior
@@ -48,7 +51,7 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
   * Please avoid working directly on the `master` branch.
   * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
 * Make sure you have added sufficient tests and documentation for your changes.
-  * Test functionality with RSpec; est features / UI with Capybara.
+  * Test functionality with RSpec; Test features / UI with Capybara.
 * Run _all_ the tests to assure nothing else was accidentally broken.
 
 ### Documenting Code
@@ -60,15 +63,11 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
   * If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
   * This work greatly increases the usability of the code base and supports the on-ramping of new committers.
   * We will all be understanding of one another's time constraints in this area.
-* YARD examples:
-  * [Hydra::Works::RemoveGenericFile](https://github.com/projecthydra-labs/hydra-works/blob/master/lib/hydra/works/services/generic_work/remove_generic_file.rb)
-  * [ActiveTriples::LocalName::Minter](https://github.com/ActiveTriples/active_triples-local_name/blob/master/lib/active_triples/local_name/minter.rb)
 * [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
 
 ### Committing changes
 
 * Make commits of logical units.
-  * Your commit should include a high level description of your work in HISTORY.textile
 * Check for unnecessary whitespace with `git diff --check` before committing.
 * Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 * If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
@@ -103,6 +102,10 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
       long to fit in 72 characters
 ```
 
+* Make sure you have added the necessary tests for your changes.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+* When you are ready to submit a pull request
+
 ### Submitting Changes
 
 * Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
@@ -125,9 +128,7 @@ We adopted [Github's Pull Request Review](https://help.github.com/articles/about
 Common checks that may occur in our repositories:
 
 1. Travis CI - where our automated tests are running
-2. Hound CI - where we check for style violations
-3. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
-4. CodeClimate - is our code remaining healthy (at least according to static code analysis)
+2. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
 
 If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
 
@@ -144,16 +145,17 @@ First, the person contributing the code is putting themselves out there. Be mind
 This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:
 
   * Does the commit message explain what is going on?
-  * Does the code changes have tests? _Not all changes need new tests, some changes are refactors_
+  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
   * Do new or changed methods, modules, and classes have documentation?
   * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
   * Does the description of the new/changed specs match your understanding of what the spec is doing?
+  * Did the Travis tests complete successfully?
 
 If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
 
 # Additional Resources
 
 * [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
 * [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
 * [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)

data/Gemfile

@@ -4,7 +4,7 @@ source "https://rubygems.org"
 
 gemspec path: File.expand_path('..', __FILE__)
 
-gem 'byebug' unless ENV['CI']
+gem 'byebug' unless ENV['TRAVIS']
 gem 'pry-byebug' unless ENV['CI']
 
 gem 'activemodel', ENV['RAILS_VERSION'] if ENV['RAILS_VERSION']
@@ -12,7 +12,6 @@ gem 'activemodel', ENV['RAILS_VERSION'] if ENV['RAILS_VERSION']
 group :test do
   gem 'simplecov', require: false
   gem 'coveralls', require: false
-  gem 'rspec_junit_formatter'
 end
 
 gem 'jruby-openssl', platform: :jruby

data/History.txt

@@ -238,30 +238,30 @@ v9.8.0
 
 v9.7.1
  2016-01-22 : The jcr/mix versionable predicate is no longer used [Adam Wead]
- 
+
  2016-01-22 : Add detail to SolrQueryBuilder.construct_query_for_pids deprecation warning [David Chandek-Stark]
- 
+
  2016-01-21 : Updating to the latest Rubocop [Michael J. Giarlo]
- 
+
  2015-12-04 : Adds :PID property to ActiveFedora::RDF::Fcrepo::Model vocab [David Chandek-Stark]
 
 v9.7.0
  2015-11-25 : Allowing access to the gone? method from outside the object [Carolyn Cole]
- 
+
  2015-11-24 : Use rdf-vocab gem for DC vocab [Justin Coyne]
- 
+
  2015-11-24 : Silence deprecation warning in test [Justin Coyne]
- 
+
  2015-11-24 : Test deprecation using mocks [Justin Coyne]
- 
+
  2015-11-24 : Give an error when the user queries for a non-existant reflection [Justin Coyne]
- 
+
  2015-11-20 : Re-add get_config_path method (removed in 9.6.0) with deprecation warning. [Jim Coble]
- 
+
  2015-11-11 : Don't try to parse empty dates [Adam Wead]
- 
+
  2015-11-10 : Adds explicit require of 'rdf/vocab'. [David Chandek-Stark]
- 
+
  2015-11-09 : ids_reader should not return duplicates. [Trey Terrell]
 
 v9.6.2
@@ -282,7 +282,7 @@ v9.6.0 (yanked due to error parsing nil dates)
 
   2015-10-27: Create failing test for issue with datastreams resetting to old
   version after save related to
-  https://github.com/projecthydra/active_fedora/issues/913 [Kathryn Cassidy]
+  https://github.com/samvera/active_fedora/issues/913 [Kathryn Cassidy]
 
   2015-10-26: Save timezone information for DateTime values. Load from Solr as
   DateTime rather than String when index type is :date. [Olli Lyytinen]
@@ -984,7 +984,7 @@ v9.0.0
 
   2014-10-30: Rely on autosave associations when setting nested attributes This
   brings us closer to parity with ActiveRecord and fixes a problem present in
-  https://github.com/projecthydra/hydra-head/pull/211 [Justin Coyne]
+  https://github.com/samvera/hydra-head/pull/211 [Justin Coyne]
 
   2014-10-30: Use attached_files rather than the deprecated datastreams method
   [Justin Coyne]
@@ -1082,11 +1082,11 @@ v9.0.0
   [Justin Coyne]
 
   2014-10-27: Reload the lastModified after an implicit save via
-  HasManyAssociation#concat Fixes an error like this:     RuntimeError:           
-  ERR STATUS: 409 Could not remove triple containing predicate           
-  http://fedora.info/definitions/v4/repository#lastModified to            node    
+  HasManyAssociation#concat Fixes an error like this:     RuntimeError:
+  ERR STATUS: 409 Could not remove triple containing predicate
+  http://fedora.info/definitions/v4/repository#lastModified to            node
          /test/1a/de/75/90/1ade7590-02aa-4e63-8c60-e5c34e11c170...            when
-  updating           
+  updating
   http://localhost:8983/fedora/rest/test/1a/de/75/90/1ade7590-02aa-4e63-8c60-e5c34e11c170.
   [Justin Coyne]
 
@@ -2131,7 +2131,7 @@ Improved loading from solr
 RDF datastreams
 Replaced solr-ruby with rsolr. Note: remove any calls to .hits
 load_instance is now deprecated, replaced with find
-Find and load_instance_from_solr always instantiate the model defined in the object. 
+Find and load_instance_from_solr always instantiate the model defined in the object.
 Run a stub :environment task in the fixture loading rake tasks (which is overridden by rails)
 Find raises ObjectNotFoundError when the object isn't found
 Removed dependency on solrizer-fedora
@@ -2217,7 +2217,7 @@ HYDRA-722 updating AF::Base#label= and then saving doesn't persist the change
 JettyWrapper to 1.2.0
 Upgrade to rspec2
 add_file_datastream should take a prefix option.
-Added assert_content_model method 
+Added assert_content_model method
 Updates for ruby 1.9 compatibility
 
 3.1.4
@@ -2268,7 +2268,7 @@ added belongs_to and has_many model relationships
 added nested_attributes_for
 Added dependency on rails > 3.0.0
 
-2.3.7 
+2.3.7
 
 HYDRA-650 -- Fixed relationship inheritance (Rick Johnson)
 
@@ -2277,7 +2277,7 @@ HYDRA-650 -- Fixed relationship inheritance (Rick Johnson)
 YANKED
 Removed Bundler.require, which was causing odd dependency order resolving.
 
-2.3.5 
+2.3.5
 
 YANKED
 branched so that trunk now require rails 3.
@@ -2292,7 +2292,7 @@ Fixed HYDRA-590
 
 HYDRUS-151: Base.update_datastream_attributes now relies on update_indexed_attributes instead of update_attributes.  This makes it easier to support non-javascript forms (and makes update_datastream_attributes worth using).
 
-2.0.4 
+2.0.4
 
 collection_members_append now returns self.
 
@@ -2352,13 +2352,13 @@ Misc bug fixes
 
 1.2.1
 
-TERMPORARY: removed solrizer from gem dependency list (cyclic reference breaks bundler) 
+TERMPORARY: removed solrizer from gem dependency list (cyclic reference breaks bundler)
 
 1.2
 
 Now support using OM::XML::Terminologies in NokogiriDatastreams
 
-resolved #504 -- Allow SSL certificate client authentication for connections to Fedora 
+resolved #504 -- Allow SSL certificate client authentication for connections to Fedora
 
 Added Experimental methods for has_datastream, named_datastream, and remove_relationship (contributed by Rick Johnson at Notre Dame)
 
@@ -2379,7 +2379,7 @@ MetadataDatastream.update_indexed_attributes was no longer marking the object di
 
 solrizer fix to ensure that Nokogiri Datastreams are included in Base.to_solr
 
-1.1.7 
+1.1.7
 
 Nokogiri Datastream support using Nokogiri and OM::XML.  Includes indexing of xml contents into solr based on accessors declared using OM::XML:Accessor module.
 You now have the option of calling has_metadata without passing in a block
@@ -2391,9 +2391,9 @@ Bug #959: Base.delete fails to delete objects from Solr even when ENABLE_SOLR_UP
 
 1.1.5
 
-Feature: Base.save triggers Solrizer if you've required the gem in your app 
+Feature: Base.save triggers Solrizer if you've required the gem in your app
 
-1.1.2 
+1.1.2
 
 Bug: Model.find_by_solr fails when you pass it an argument of :all
 Testing: Updated RSpec tests to run against localhost:8983 with Fedora 3.3 (instead of localhost:8080 with Fedora 3.2).  This means you can use a copy of hydra-jetty from http://github.com/hydraproject/hydra-jetty
@@ -2413,7 +2413,7 @@ Feature #822: Export & Ingest Fedora Objects
 
 Bundled ruby-fedora into active-fedora, removing external gem dependency
 
-Field names now map to solr field names using solr_mappings.yml.  You can put your own into RAILS_ROOT/config/solr_mappings.yml or rely on the default within the gem.  
+Field names now map to solr field names using solr_mappings.yml.  You can put your own into RAILS_ROOT/config/solr_mappings.yml or rely on the default within the gem.
 
 * Bug #552: Model relationship should be asserted using hasModel instead of conformsTo
 * Bug #614: Datastream should have mime_type accessors
@@ -2455,7 +2455,7 @@ Minor update.
 
 * 1 major enhancement:
   * ruby-fedora is now compatible with Fedora 3.2.1
-  
+
 Changelog:
 * ToDo #272: Datastream.new should accept a :prefix option for auto-incrementing DSIDs
 * ToDo #275: Update RubyFedora to work with Fedora 3.2 REST API