Page History

...

You can configure a proxy to use for some or all of your HTTP requests in Maven 2.0. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore‚Äîin keystore‚ in the mean time, please ensure your settings.xml file (usually ${user.home}/.m2/settings.xml) is secured with permissions appropriate for your operating system).

...

1. Wiki Markup
   *The installation directory*, referred to as __\[dspace\]__ . This is the location where DSpace is installed and running off of it is the location that gets defined in the dspace.cfg as "dspace.dir". It is where all the DSpace configuration files, command line scripts, documentation and webapps will be installed to.

2. Wiki Markup
   *The source directory*, referred to as __\[dspace-source\]__ . This is the location where the DSpace release distribution has been unzipped into. It usually has the name of the archive that you expanded such as _dspace\-<version>_{_}{\-}release{-}_ or _dspace<version>dspace\-<version>\-src\-release_. It is the directory where all of your "build" commands will be run.

3. Wiki Markup

   *The web deployment directory*. This is the directory that contains your DSpace web application(s). In DSpace 1.5.x and above, this corresponds to __\[dspace\]/webapps__ by default. However, if you are using Tomcat, you may decide to copy your DSpace web applications from __\[dspace\]/webapps/__ to _\[tomcat\]/webapps/_ (with _\[tomcat\]_ being wherever you installed Tomcat‚ÄîalsoTomcat‚ also known as _$CATALINA_HOME_). For details on the contents of these separate directory trees, refer to directories.html. _Note that the \_\[dspace-source\]_ and _\[dspace\]_ directories are always separate\!\_

Installation

This method gets you up and running with DSpace quickly and easily. It is identical in both the Default Release and Source Release distributions.

...