Migrate to new Shipkit plugins

[slawekjaranowski]

PR checklist

The following checklist shall help the PR's author, the reviewers and maintainers to ensure the quality of this project.
It is based on our contributors guidelines, especially the "writing code" section.
It shall help to check for completion of the listed points.
If a point does not apply to the given PR's changes, the corresponding entry can be simply marked as done.

Documentation (general)

• There is documentation (Javadoc and site documentation; added or updated)
• There is implementation information to describe why a non-obvious source code / solution got implemented
• Site documentation has its own .adoc file in the docs folder, e.g. docs/report-entries.adoc
• Only one sentence per line (especially in .adoc files)
• Javadoc uses formal style, while sites documentation may use informal style

Documentation (new extension)

• The docs/docs-nav.yml navigation has an entry for the new extension
• The package-info.java contains information about the new extension

Code

• Code adheres to code style, naming conventions etc.
• Successful tests cover all changes
• There are checks which validate correct / false usage / configuration of a functionality and there are tests to verify those

Checks

• Tests use AssertJ or our own PioneerAssert (which are based on AssertJ)
• tested localy by commands:

./gradlew  bintrayUpload -PbintrayDryRun
./gradlew generateChangelog

Contributing

• A prepared commit message exists
• The list of contributions inside README.md mentions the new contribution (real name optional)

---

I hereby agree to the terms of the JUnit Pioneer Contributor License Agreement.

[beatngu13]

Thanks for the PR! 🥳 Just did a quick scan before one of the maintainers finds time.

Afterwards, we shouldn't forget to remove the obsolete secrets (TRAVIS_BRANCH etc.).

[mockitoguy]

@slawekjaranowski, thank you! How did you test this change? (please update the PR description)

[slawekjaranowski]

As I wrote I tested by command:

./gradlew  bintrayUpload -PbintrayDryRun
./gradlew generateChangelog

and examine output log and build directory

[aepfli]

so we have to rethink this approach anyways, as bintray/jcenter is EOL in may 2021 https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

for now this is fine, but we might have to adapt the process of uploading etc, so we directly push to maven central and sign within gradle

[slawekjaranowski]

please re-run GitHub Action for PR

[Bukama]

please re-run GitHub Action for PR

Well that won't restart timeout jobs. Those are only restarted after a new commit.

[aepfli]

LGTM

[slawekjaranowski]

Thank you for approval.
Are there something what I should do before merge?

[nipafx]

Thank you so much for the PR, @slawekjaranowski! I'm sorry that I still didn't take a look at it. It's not for a lack or appreciation, I assure you. I hope to get around to it in the coming days.

[Bukama]

LGTM (aside from the merge conflicts)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[nipafx]

Thanks again @slawekjaranowski, merged. :)

[nipafx]

@slawekjaranowski We just released 1.3.8, but expected 1.3.1 - any idea what happened?

[slawekjaranowski]

@nipafx shipkit-auto-version plugin is responsible for calculating next version during release. In this case we have new 8 commits from last release so version was incremented by 8.

Please look at https://github.com/shipkit/shipkit-auto-version#implementation-details