Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
titleHelp us to Test 1.8.0 during the Testathon (Sept 12-23, 2011)!

The DSpace 1.8.0 Testathon has begun! This is your opportunity to get a preview of the upcoming 1.8.0 release, while also helping us to fully test the system and squash any last bugs!

...

  • Wiki Markup
    *The dspace.cfg has been "split up":* Many "module" configurations have now been moved out of the 'dspace.cfg' and into separate configuration files in the {{\[dspace\]/config/modules/}} directory.
    • Wiki Markup
      Authentication Configurations are now in {{\[dspace\]/config/modules/authenticate*.cfg}} files
    • Wiki Markup
      Bulk Metadata Editing Configurations are now in the {{\[dspace\]/config/modules/bulkedit.cfg}} file
    • Wiki Markup
      Discovery Configurations are now in the {{\[dspace\]/config/modules/discovery.cfg}} file
    • Wiki Markup
      OAI-PMH / OAI-ORE Configurations are now in the {{\[dspace\]/config/modules/oai.cfg}} file
    • Wiki Markup
      Solr Statistics Configurations are now in the {{\[dspace\]/config/modules/solr-statistics.cfg}} file
    • Wiki Markup
      SWORD (client & server) Configurations are now in {{\[dspace\]/config/modules/sword*.cfg}} files
  • Behavior of 'ant update' has changed: The ant update upgrade command now defaults to replacing any existing configuration files (though the existing configuration files will first be backed up to a file with the suffix *.old).
    • In prior versions of DSpace (before 1.8.0), this ant update command would leave existing configuration files intact (and you would have to manually merge in new configuration settings, which would be in a file with the suffix *.new). If you prefer this previous behavior, you can still achieve the same result by running:
      • ant -Doverwrite=false update.
    • Wiki Markup
      *WARNING:* If you choose to run {{ant -Doverwrite=false update}} please be aware that this will not auto-upgrade any of your configuration files. This means you must closely watch the output of this command, and ensure you manually upgrade all configuration files in the {{\[dspace\]/config/}} directory as well as all Solr configurations/schemas in the {{\[dspace\]/solr/search/conf/}} and {{\[dspace\]/solr/statistics/conf/}} directories.

...