Closed averbraeck closed 4 months ago
For one, it needs an explicit skin. The site.xml
files have been updated with:
<skin>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-fluido-skin</artifactId>
<version>1.11.1</version>
</skin>
The site.xml
files still referred to the project ots-xsd. This has been removed.
The ots-editor
project has been added to the site.xml
file as one of the menu items in the MODULES
menu.
The banners need to be updated. artifactId
needs to be preceded by project.
, and the project name has to be explicitly mentioned as the left banner:
<bannerLeft>
<name>${project.name}</name>
</bannerLeft>
<bannerRight>
<name>${project.artifactId} ${project.version}</name>
</bannerRight>
The Maven fluido skin has been updated to: 2.0.0-M8.
The project
tag in site.xml
now starts with:
<project name="${project.artifactId} ${project.version}"
Eclipse had quite some trouble running the site generation with the EMBEDDED maven compiler, and failed with errors. This is a known issue. Installing a local Maven compiler (3.9.6) and setting it as default solves the problem. This will most probably not play a role when generating documentation with github actions and on the Delft server, since these use an explicit Maven compiler and not an embedded one.
Site generation outside of Eclipse works fine. The site is not yet visible at opentrafficsim.org, but that is a separate issue.
The maven-site plugin has been updated from version 3 to version 4. This needs some changes.