Page History

...

Users/Developers may also choose to copy the build.properties under a different name for different environments (e.g. development, test & production), and choose which environment to build DSpace for by passing a "-Denv" (environment) flag to the Maven build process (e.g. "mvn package -Denv=test" would build DSpace using a custom "test.properties" file).

...

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 , so that in the DSpace Installation Package. That way they can be installed using the appropriate Apache Ant command (see Installation for all the details of the full install.)

...