| commit | a0e219111031a70b54544dd0c2d4683aabca6903 | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Fri Apr 14 17:49:59 2023 +0000 |
| committer | GitHub <noreply@github.com> | Fri Apr 14 17:49:59 2023 +0000 |
| tree | 043b389a2fc0f124070eaa8dce833c7bda83a533 | |
| parent | aebf5a2a737f4fd5c09fb45035aea049919b5c23 [diff] |
Bump junit from 4.11 to 4.13.1 Bumps [junit](https://github.com/junit-team/junit4) from 4.11 to 4.13.1. - [Release notes](https://github.com/junit-team/junit4/releases) - [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.11.md) - [Commits](https://github.com/junit-team/junit4/compare/r4.11...r4.13.1) --- updated-dependencies: - dependency-name: junit:junit dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
You need to have these two programs installed on your machine:
There are two ways of building the documentation project:
mvn -Plive jetty:run will make a live website copy available locally. This is very convenient while editing the docs to quickly review the changes you made.mvn clean install will build the documentation project, creating 3 representations:target/sitegen/manual.pdf)target/sitegen)If you're an Apache ServiceMix committer, you can publish a new copy of the documentation pages with this command: mvn clean install scm-publish:publish-scm