Versions Compared

Old Version 7

changes.mady.by.user Mark Diggory

Saved on

compared with

New Version 8

changes.mady.by.user Mark H. Wood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: A couple of things that looked like links but weren't; stray XHTML markup removed or replaced with Confluence equivalent

<?xml version="1.0" encoding="utf-8"?>
<html>
<b><font style="color: red">WARNING: WARNING: This page is still under development</font></b>development

The addon-mechanism for DSpace is a compile time modularity mechanism that allows code level separation between DSpace components. The main goal is to be able to extend DSpace without requiring patches and re-patches that lock developers into a single version of DSpace with no path to upgrade. This addon-mechanism moves DSpace closer to a binary distribution. These changes made by this proposal will make all compiled distributions (war files) non unique, so in the future we could just post binaries for DSpace user's to download and deploy. However the installation and upgrade processes will need to be refactored for this to be fully realized, this moves us a bit closer to that goal.

...

6.) Currently, the configuration process is still Ant driven for the moment. Installation and Upgrade can be done via the original targets.

Panel

Wiki Markup
\~% ant \[\-Dconfig=-path-to-your-dspace.cfg\] \[fresh_install\]

How does one

...

decide which addons to use?

Addons can be included into the main dspace/pom.xml as modules, and/or configured in the pom via "profiles" which can be activated via command-line or configuration properies. Addons are included into the build process either via being added as a dependency to the "appropriate" dspace webapplication project, or by inclusion as a dependency into the main dspace/pom.xml project descriptor.

...