chore(deps): update dependency org.codehaus.mojo:exec-maven-plugin to v3.2.0 (release/3.0.x)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.codehaus.mojo:exec-maven-plugin (source)	3.1.1 -> 3.2.0

---

Release Notes

mojohaus/exec-maven-plugin (org.codehaus.mojo:exec-maven-plugin)

v3.2.0

Compare Source

🚀 New features and improvements

• Enable to exec:java runnables and not only mains with loosely coupled injections (#​408) @​rmannibucau
• Try to get rid of legacy API which can break starting with java 17 (#​409) @​rmannibucau

🐛 Bug Fixes

• Fix #​401 - Maven v4 compatibility (#​414) @​slawekjaranowski

📦 Dependency updates

• Bump org.codehaus.mojo:mojo-parent from 78 to 80 (#​419) @​dependabot
• Bump commons-io:commons-io from 1.1 to 2.7 in /src/it/projects/setup-parent (#​416) @​dependabot
• Bump org.apache.commons:commons-exec from 1.3 to 1.4.0 (#​405) @​dependabot
• Bump org.codehaus.mojo:mojo-parent from 77 to 78 (#​406) @​dependabot
• Bump org.codehaus.plexus:plexus-component-metadata from 2.1.1 to 2.2.0 (#​403) @​dependabot
• Bump org.codehaus.plexus:plexus-component-annotations from 2.1.1 to 2.2.0 (#​404) @​dependabot

👻 Maintenance

• ITs improvement (#​415) @​slawekjaranowski
• Fix documentation formatting, add menu items for new examples (#​412) @​slawekjaranowski
• Execute mexec-137 also on unix family (#​413) @​slawekjaranowski
• Remove unused test (#​410) @​slawekjaranowski

🔧 Build

• Bump release-drafter/release-drafter from 5 to 6 (#​417) @​dependabot

---

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

1. Register at Qodana Cloud and configure the action
2. Use GitHub Code Scanning with Qodana
3. Host Qodana report at GitHub Pages
4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.3.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud