...
- At Step 1.2, use the following copy of pom.xml, which has been updated for Spring DM 1.2.
- At Step 1.5, use the name SPRING_DM_1.2 instead of SPRING_DM_1.1 for the User Library.
FEDORA_HOME
Until FEDORA_HOME can be deployed automatically by the war, you must run the fedora installer to create FEDORA_HOME. When running the installer, you should have the following features disabled:
- SSL
- Resource Index
- Messaging
- API-A Auth
fedora.war
Until the Fedora Maven build is able to produce a deployable war artifact, you will need to manually create the Eclipse project that represents the Fedora WAR.
For the Spring DM extender to recognize your fedora.war Eclipse project as a web application, ensure that the project name ends in ".war", e.g. "fedora.war". The project structure should resemble the following:
- fedora.war** WEB-INF*** lib
- MANIFEST*** MANIFEST.MF
At this stage in development, fedora.war should have the following features disabled:
...
As of rev 8183, you can build the fedora-webapp artifact directly from the fedora svn tree and deploy the war in the Spring-DM-Target-Platform described in the step above.
If you are getting java.lang.OutOfMemoryError: Java heap space errors while building with Maven, you may need to allocate more resources to Maven, e.g.
| Code Block |
|---|
export MAVEN_OPTS="-Xms256m -Xmx800m -XX:PermSize=256m -XX:NewSize=64m"
|
...
MANIFEST.MF
Add the following META-INF/MANIFEST.MF to your copy of fedora.war