Page History

...

For ease of use, the Configuration documentation is broken into several parts:

• General Configuration Reference#General Configuration - addresses general conventions used with configuring not only the dspace.cfg file, but other configuration files which use similar conventions.
• The Configuration Reference#The build.properties Configuration Properties File - specifies the basic build.properties file settings (these basic settings are used when building/installing/upgrading DSpace)
• The Configuration Reference#The dspace.cfg Configuration Properties File - specifies the basic dspace.cfg file settings (these settings are used when DSpace is actually running)

• Optional Configuration Reference#Optional or Advanced Configuration Settings - contain other more advanced settings that are optional in the dspace.cfg configuration file.

  Info
  As of version 1.8 much of the DSpace configuration has been moved to discrete configuration files related to specific functionality and is documented in subsequent sections of this document.

...

1. A developer or user downloads a copy of DSpace to build & install
2. He/She can edit the [dspace-source]/build.properties to specify the very basic settings for building & installing DSpace
   
   1. OR, alternatively he/she can copy/rename the "build.properties" to a different "*.properties" file & edit it.  For example, you could choose  to create a separate properties file for each environment (dev.properties, test.properties, prod.properties)
3. He/She can then build the DSpace Installation Package using the *.properties file they choose
   
   1. Running simply "mvn package" will always use the default "build.properties" settings.
   2. Passing in the "-Denv" (environment) flag, will cause the build process to use a custom properties file.  Some examples:
      
      1. "mvn package -Denv=test" would build DSpace using a custom file named [dspace-source]/test.properties
      2. "mvn package -Denv=local" would build DSpace using a custom file named [dspace-source]/local.properties
      3. "mvn package -Denv=john" would build DSpace using a custom file named [dspace-source]/john.properties
4. No matter which build options are used, the values in the enabled properties file will be automatically copied over to your [dspace-source]/dspace/target/dspace-[version]-build/dspace.cfg file in the DSpace Installation Package. That way they can be installed using the appropriate Apache Ant command (see Installation Installing DSpace for all the details of the full install.)

...