+
+ 2018-07-01
+
+
+- I want to upgrade DSpace Test to DSpace 5.8 so I took a backup of its current database just in case:
+
+
+$ pg_dump -b -v -o --format=custom -U dspace -f dspace-2018-07-01.backup dspace
+
+
+
+- During the
mvn package stage on the 5.8 branch I kept getting issues with java running out of memory:
+
+
+There is insufficient memory for the Java Runtime Environment to continue.
+
+
+
+
+
+- As the machine only has 8GB of RAM, I reduced the Tomcat memory heap from 5120m to 4096m so I could try to allocate more to the build process:
+
+
+$ export JAVA_OPTS="-Dfile.encoding=UTF-8 -Xmx1024m"
+$ mvn -U -Dmirage2.on=true -Dmirage2.deps.included=false -Denv=dspacetest.cgiar.org -P \!dspace-lni,\!dspace-rdf,\!dspace-sword,\!dspace-swordv2 clean package
+
+
+
+- Then I stopped the Tomcat 7 service, ran the ant update, and manually ran the old and ignored SQL migrations:
+
+
+$ sudo su - postgres
+$ psql dspace
+...
+dspace=# begin;
+BEGIN
+dspace=# \i Atmire-DSpace-5.8-Schema-Migration.sql
+DELETE 0
+UPDATE 1
+DELETE 1
+dspace=# commit
+dspace=# \q
+$ exit
+$ dspace database migrate ignored
+
+
+
+- After that I started Tomcat 7 and DSpace seems to be working, now I need to tell our colleagues to try stuff and report issues they have
+
+
+
+
+
+
+
+
+