VIVO Documentation
Page History
...
go into each language folder (
VIVO-language
andVitro-language
) and 'install' them with Maven ("mvn install
")next, go into the VIVO project folder and uncomment the section for multiple language support in the two
pom.xml
files listed below:
(search for '<!-- Dependencies for multilingual support -->'
inside<!-- Overlays for multilingual support -->
' inside of the files)VIVO/installer/home/pom.xml
VIVO/installer/webapp/pom.xml
<version>
in thepom.xml
-files to the same version as in the 'VIVO-language/pom.xml
' and 'Vitro-language/pom.xml
' file respectively.
(In this example we had to change<version>[2.0.0,2.1.0)</version>
<version>2.0.0-SNAPSHOT</version>
in three places: 2x in'VIVO/installer/webapp/pom.xml'
and 1x in'VIVO/installer/home/pom.xml'
)
Note that these should be thehome/pom.xml
andwebapp/pom.xml
in whatever installer project is being used to deploy VIVO.- after that, we have to build VIVO again, so go into the VIVO project folder and
- "
mvn install -s installer/my-settings.xml
"
- "
- now edit the '
/vivo_home_dir/config/runtime.properties
' file in your VIVO home directory (as declared in your 'VIVO/installer/my-settings.xml
' file)- uncomment/add '
RDFService.languageFilter = true
' - uncomment/add '
languages.selectableLocales = en_US, de_DE'
- uncomment/add '
- restart the tomcat
- you should now be able to select your installed language (in this case German) in the header of your VIVO site
...
Overview
Content Tools