The project rendering command mainly provides a simple API in order to integrate build system. The initial main purpose of this command is to be able to combine multiple static site generators in order to build a single website (i.e. writing articles with Hugo and create API docs via Javadoc).

Illustrative Example

The rendering command takes the from-project and creates a file structure at the to-project:

• Check the from-project in order to determine its type.
• Check the to-project in order to determine its type.
• Determine and execute the appropriate build command via dependency injection provided by command.managed.execute.

Let's illustrate this with an example, the deployment of splitcells.net: Here each arrow represent a call of project.render from a project to a project. Note that a project can be just a folder and does not have to be anything special. The calls in this picture are:

1. Copy files from website.default.content/src/main/resources to a temporary folder.
2. Build the network.blog with the static blog generator hugo and copy its files to the temporary folder.
3. Render XML and CommonMark files and place these at the temporal folder.
4. Upload content of temporal folder to the SFTP-Server, which host the website.

• SPDX-License-Identifier: EPL-2.0 OR GPL-2.0-or-later
• SPDX-FileCopyrightText: Contributors To The net.splitcells.* Projects