chore(deps): bump io.jstach.rainbowgum:rainbowgum from 0.4.1 to 0.6.0

[dependabot[bot]]

Bumps io.jstach.rainbowgum:rainbowgum from 0.4.1 to 0.6.0.

Release notes

Sourced from io.jstach.rainbowgum:rainbowgum's releases.

v0.6.0

Major refactoring as we move towards 1.0.0

• partial rolling support has been added such that logrotate and other agents can rotate files with out data loss
  • Unfortunately this feature requires some manual integration but In the future will make this easier and provide a Spring Boot actuator endpoint for rolling signaling.
• jlink was not working because of the eclipse null annotations missing module-info.java. The annotations are now marked as provided so jlink will work. Thanks @​bowbahdoe !
• rainbowgum-jdk module will now safely detect if java.logging is available and thus is now a requires static.
• property and builder error messaging has improved

What's Changed

• Fix property error messages and output reg by @​agentgt in jstachio/rainbowgum#84

New Contributors

• @​agentgt made their first contribution in jstachio/rainbowgum#84

Full Changelog: https://github.com/jstachio/rainbowgum/compare/v0.5.0...v0.6.0

v0.5.0

First true release (not a pre-release) of Rainbow Gum.

Rainbow Gum is mostly production ready!

• Coverage is close to 90%
• Over 10,000 tests have been added since 0.4.0
• Many bugs have been fixed and some bloat has been removed
• Current benchmarking shows Rainbow Gum to be faster than all known SLF4J implementations
• The OOB Jansi formatter no longer has a weird threadlocal usage caused by Jansi itself

0.4.0 users may find some breaking changes but the API should be far more stable going forward at least in the core module. Highly recommend upgrading given the various bugs found.

The plan for v0.6.0 is resilience (e.g. reopening files) and file rolling.

Changelog

Sourced from io.jstach.rainbowgum:rainbowgum's changelog.

Explanation

This project does not use the maven release plugin for a variety of reasons:

• Creates an environment that can be very different from the normal snapshot deploy process by forking
• Needlessly edits the pom file twice and checkins it in which requires every pom file in the project to be changed.
• Because it constantly changes the SNAPSHOT pom on each release downstream projects have to remember to update their SNAPSHOT version even for patch releases.

Unlike the maven release plugin we do not constantly change the pom for each patch version. The release version is stored in a properties file called version.properties. The pom only should change (commited change) if the minor or major version changes.

For example say the pom is 0.7.0-SNAPSHOT and our last release is 0.6.0.

If we now want to make a patch version of 0.6.1 the pom file will not need to be updated (except by the release script for deployment). However if we are actually wanting to finally release 0.7.0 then the pom must be updated to something like 0.8.0-SNAPSHOT.

The vh script will mostly make sure you do not violate this.

Directions

Deploying SNAPSHOTs

If you just want to deploy a snapshot to centrals snapshot repositories run:

mvn clean deploy -Pcentral

Deploying Releases

Here is the process for release:

1. Edit version.properties to the desired release version by calling:

2. bin/vh set current NEW_VERSION

3. If this is not a patch release you will need to update the pom to a later snapshot

4. bin/vh set pom VERSION-SNAPSHOT # where VERSION is the new minor/major version

5. Checkin the file version.properties (and pom file if minor or major version change). It will serve as the commit for tagging reproducible builds.

6. run bin/vh release which will tag and temporarily update the pom for release. DO NOT CHECKIN THE ALTERED POM

7. Run the commands it tells you to run

Updating Documentation

All the documentation should be in the aggregated javadoc. While sites like javadoc.io can host singular jars they cannot really host aggregate javadoc (e.g. mutltimodule).

... (truncated)

Commits

• 088d4a1 Release v0.6.0
• 62f8de2 Upgrade log4j
• e2be11c lock in rabbitmqoutput should be final
• 982e7b5 Update maven wrapper
• 509ac27 Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.6.3 to 3.7.0
• a06a037 Bump org.apache.maven.plugins:maven-help-plugin from 3.4.0 to 3.4.1
• e71e90f Fix errorprone paren issue
• 8d46ed5 Make java.logging optional
• dc35731 Simplify log appenders
• 8c42497 Fix rolling limitation description
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #115.