vivo/doc/developers.txt
j2blake 89f759fcbc VIVO-2 Modify the build so installers can create a container-neutral VIVO.
Split deploy.properties into build.properties and runtime.properties, with runtime.properties going into the Vitro home directory. Modify ConfigurationProperties to locate the Vitro home directory, either by System property or JNDI Environment variable, or from build.properties, and to read from both build.properties and runtime.properties. Revise the install and upgrade documents for VIVO and Vitro. Change comments and error messages that referred to deploy.properties by name.
2013-01-16 14:52:35 -05:00

45 lines
1.9 KiB
Text

-------------------------------------------------------------------------------
Instructions for VIVO developers
-------------------------------------------------------------------------------
If you are working from the VIVO distribution files, you should follow the
instructions in "install.html", in this directory.
-------------------------------------------------------------------------------
If you are working from the VIVO source files, checked out from the Git
repository, then your working area does not contain the "vitro-core" directory.
Follow these steps:
1) In the VIVO working area, create build.properties as a copy of
example.build.properties
2) Check out the Vitro source files from Git into a separate working
area.
3) Modify build.properties (created in step 1) so vitro.core.dir points to
the Vitro working area (created in step 2). For example:
vitro.core.dir = ../vitro
4) Follow the instructions in "install.html" to complete the installation,
omitting step 3.
-------------------------------------------------------------------------------
Answers to Frequently Asked Questions:
-------------------------------------------------------------------------------
Q: I'm running VIVO in Tomcat on a MacIntosh. When I upload an image file, a
strange icon appears in the dock. What's up with that?
A: The image processing code in VIVO uses javax.imageio.ImageIO, which in turn
uses code in the java.awt package. By default, this package will open a work
area on your screen, producing this icon even though no visible window is
created.
You can prevent this by editing {tomcat}/conf/setenv.sh, and adding the
"java.awt.headless" option. For example,
export CATALINA_OPTS="-Xms1024m -Xmx1024m -XX:MaxPermSize=64m -Djava.awt.headless=true"