Page History

...

• Spring-based configuration. Fedora has adopted Spring as a means of configuring its internal components. This move to a modern, enterprise-grade framework offers greater flexibility for integrating repository components, and allows Fedora to more easily adapt to challenging deployment environments. See also Spring Configuration in the documentation.
• Standard WAR file distribution. Fedora runtime configuration has moved entirely outside of the WAR file, allowing a single standardized war file to be included in each release. This allows bugfix releases to be distributed and applied in a much simpler fashion than before: merely replace the old WAR file with the updated one.
• FeSL policy enforcement improvements. Numerous enhancements have been made to FeSL authZ. Notably, the requirement of installing dbxml has been removed. This had been a barrier to FeSL testing and adoption. With the various improvements in FeSL authZ, we consider this feature "beta" and encourage users of Fedora to give it a try and provide feedback.
• FEDORA_HOME environment variable no longer required to run fedora server. Outside of running commandline utilities, FEDORA_HOME is now ignored, and has been completely replaced with more flexible means of specifying the location of the fedora home directory.
• JSON support for RISearch Resource index searches now support JSON, allowing greater ease of use with javascript clients.
• DC datastream fixes. The DC datastream, with contains information needed for the internal functioning of Fedora, is now more robust. If a user inadvertently removes the necessary dc:identifier fields, this will be automatically corrected.
• Build and testing improvements. Numerous testing and development improvements are part of 3.5. Perhaps most notably, deployment and running of a live Fedora instance can now be managed automatically as part of a standard maven build.

For a detailed list of features and bugfixes comprising this release see the tables below.

...