Jeremy Long

Encoding must be done at the point of output. Otherwise you run into the problem of using the wrong encoding.

We can add a Jakarta module, copy over the JSP and update appropriately.

looks like a dependency version conflict. You'll need to figure out which version you need to add the constraint for. As an example see https://github.com/dependency-check/dependency-check-gradle?tab=readme-ov-file#gradle-build-environment

There is a difference between the build env and the compile time dependencies. Plugins and tasks can have dependencies that do not affect the dependencies of the build itself -...

you can find the conflict by running `./gradlew buildEnv`

The plugin will scan only the projects it is applied to. If you apply it to the root it will scan everything - but each project will get its own...

There is no contradiction. You can apply the plugin to an entire multi-project build and only scan a specific project by specifying `scanProjects`

Or you can only apply the plugin to a specific build. Multiple ways to achieve the same goal.

> Sharing build logic between projects is meant to be done through plugins. Do you mean conventions? Also - if you don't mind I would love a PR to update...

Yes, several people use this option. They build a database on one node, save the database, and then copy the DB to any other node that is running ODC and...