VIVO Documentation
...
Step | Action | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1) Create directory structures in Vitro-languages and VIVO-languages The demonstration is for the integration of the French Canadian fr_CA in Vitro-languages and VIVO-Languages |
| ||||||||||||||
2) Translate the content of each properties file 2) Translate the content of each properties file ('all_en_CA.properties' 'all_en_CA.properties') into the target language (here, the en_CA) |
| ||||||||||||||
|
| ||||||||||||||
|
|
...
Step | Action | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Edit and modify ./core/home/pom.xml Add the dependency (in bold) in the POM file | . . . | ||||||||||
Edit and modify ./core/webapp/pom.xml Add the dependency (in bold) in the POM file | . . . | ||||||||||
Edit and modify ./fr_CA/home/pom.xml Pay particular attention to the version number which must correspond to the version currently under development. | ... <groupId>org.vivoweb</groupId> <parent> <name>VIVO Languages for Home fr_CA</name> ... | ||||||||||
Adding Edit and modify ./fr_CA/webapp/pom.xml Pay particular attention to the version number which must correspond to the version currently under development. (Line 7 and 13). | ...
Code Block |
<modelVersion>4.0.0</modelVersion>
<groupId>org.vivoweb</groupId>
<artifactId>vivo-languages-webapp-fr_CA</artifactId>
<version>1.11.2-SNAPSHOT</version>
<packaging>war</packaging>
<parent>
<groupId>org.vivoweb</groupId>
<artifactId>vivo-languages-fr_CA</artifactId>
<version>1.11.2-SNAPSHOT</version>
<relativePath>..</relativePath>
</parent>
<name>VIVO Languages for Web App fr_CA</name> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> <packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes> <archiveClasses>false</archiveClasses> <archive> <manifest> <addClasspath>true</addClasspath> </manifest> </archive> </configuration> </plugin> <plugin> <artifactId>maven-clean-plugin</artifactId> <configuration> <filesets> <fileset> <directory>overlays</directory> </fileset> </filesets> </configuration> </plugin> </plugins> </build> </project>
| |||||||||
Edit and modify ./fr_CA/pom.xml Pay particular attention to the version number which must correspond to the version currently under development. | ... <modelVersion>4.0.0</modelVersion> <groupId>org.vivoweb</groupId> | Editing ./pom.xml Add the following lines | Code Block |
| |||||||
Editing ./pom.xml Add the following line which is in bold | . . . |
...
...
Step | Action |
---|---|
Editing ./home/pom.xml Add the dependency (in bold) in the POM file | . . . |
Editing ./webapp/pom.xml Add the dependency (in bold) in the POM file | . . . <dependency> |
Editing ./webapp_dep/pom.xml Add the dependency (in bold) in the POM file | . . . |
...
Action | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
start compilingBefore starting the compilation make sure you have correctly configured the settings_i18n_linux.xml file as described above. The -DskipTests option is optional.
Observe lines 9, 21 and 30 which indicate that the new language is included in the installation process. |
At the end you should see a compilation end looking like this:
|
...