Running the Mirage 2 build (
mvn package -Dmirage.on=true) as the "root" user (or via sudo) will result in the following error from "Bower". This will result in a broken Mirage 2 build. The fix is to ensure you are building DSpace as a non-root user account. For more information on this Bower error, see: http://serverfault.com/questions/548537/cant-get-bower-working-bower-esudo-cannot-be-run-with-sudo
bower ESUDO Cannot be run with sudo Additional error details: Since bower is a user command, there is no need to execute it with superuser permissions.
- The Mirage 2 build requires git. Ensure that git is installed before you launch the Mirage 2 build.
The Mirage 2 build process will attempt to retrieve some dependencies from GitHub via the "git" protocol. This requires outgoing access to github.com, port 9418. If the machine on which you're running the build has access restrictions in place for that port but outgoing access via HTTPS (port 443) is allowed, you can substitute the https protocol by running (with the same user account that will run the maven step):
Code Block language bash
git config --global url."https://github.com/".insteadOf git://github.com/
For more information on this issue, see
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2428
- If you want to use the "quick build" option (where you run maven in
[dspace-src]/dspace/), you must install the build dependencies locally, see
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2368
- Maven 3.3.1 is not supported, see
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2533
Mirage 2 adds two configuration options to dspace.cfg that affect the rendering of bitstream labels on item pages: