Page History

...

You will also need to move your customisations into the new Maven structure.

Maven Structure

...

In moving to Maven, the code has now been re-organized to follow standard Maven conventions. As well as separating out the Java code into "API" projects for both Vitro and VIVO, with the templates, etc. in "webapp" projects, it also means that the directory structure follows the standard. So in "API", all the Java code is in the "src/main/java" directory, and in "webapp" the templates are in "src/main/webapp".

It is recommended that you treat the "installer" (or standard distribution) project(s) as a third tier, and keep local customisations only in those project(s).

For Java files, you can place them directly in the "webapp/src/main/java" directory - these will be compiled and included into your web application as class files. As class files are loaded ahead of jars in WEB-INF/lib, this even allows you to completely overwrite and replace classes that are supplied by the VItro / VIVO jars.

Your theme - and any other template modifications, etc. - should be placed in the "webapp/src/main/webapp" directory.

Any additional dependencies that you need can be added to the webapp/pom.xml, and they will be retrieved from Maven central and included in the packaged application.

Making changes to the home directory

In order to add files to your home directory - e.g. to include additional filegraph RDF - they should be added to the "home/src/main/resources" directory.

If you need to remove a file that is supplied by Vitro / VIVO, then you will need to edit the home/src/main/assembly/home.xml file:

<dependencySet>
    <outputDirectory>/</outputDirectory>
    <unpack>true</unpack>
    <unpackOptions>
        <excludes>
            <exclude></exclude>
        </excludes>
    </unpackOptions>
</dependencySet>

Code / Environment Changes

...