build(deps): bump org.mybatis.generator:mybatis-generator-core from 1.4.0 to 1.4.2

[dependabot]

Bumps org.mybatis.generator:mybatis-generator-core from 1.4.0 to 1.4.2.

Release notes

Sourced from org.mybatis.generator:mybatis-generator-core's releases.

MyBatis Generator Release 1.4.2

This is a small maintenance release. The most visible change is a switch from the "javax" namespace to the "jakarta" namespace for the generated annotation.

There are several other relatively minor changes.

For all users, the changes are fully detailed in the documentation here: https://mybatis.org/generator/whatsNew.html and the GitHub milestone here: https://github.com/mybatis/generator/issues?q=milestone%3A1.4.2

The new artifacts are available in Maven central at

<dependency>
    <groupId>org.mybatis.generator</groupId>
    <artifactId>mybatis-generator</artifactId>
    <version>1.4.2</version>
</dependency>

and

<dependency>
    <groupId>org.mybatis.generator</groupId>
    <artifactId>mybatis-generator-maven-plugin</artifactId>
    <version>1.4.2</version>
</dependency>

You can install the eclipse feature from the eclipse market place here: https://marketplace.eclipse.org/content/mybatis-generator

MyBatis Generator Release 1.4.1

This release is primarily focused on improving the generated code targeting MyBatis Dynamic SQL.

For Java users (targetRuntime = "MyBatis3DynamicSQL") the changes are relatively minor and should be transparent to most users.

For Kotlin users (targetRuntime = "MyBatis3Kotlin") the changes are more impactful and are aligned with updates to the Kotlin DSL in newer versions of MyBatis Dynamic SQL. After upgrading, the generated code will be different than Kotlin code generated with earlier versions of MyBatis Generator. There is information about making changes to accommodate these changes here: https://mybatis.org/generator/whatsNew.html

There are several other relatively minor changes.

For all users, the changes are fully detailed in the documentation here: https://mybatis.org/generator/whatsNew.html and the GitHub milestone here: https://github.com/mybatis/generator/issues?q=milestone%3A1.4.1

The new artifacts are available in Maven central at

<dependency>
    <groupId>org.mybatis.generator</groupId>
    <artifactId>mybatis-generator</artifactId>
    <version>1.4.1</version>
</dependency>

and

... (truncated)

Changelog

Sourced from org.mybatis.generator:mybatis-generator-core's changelog.

Pre-requisites:

1. Make sure you have your SSH key setup to GitHub per these instructions:

   https://help.github.com/categories/ssh/

2. Make sure you have generated a GPG key and have the gpg executable in your path per these instructions:

   https://github.com/mybatis/committers-stuff/wiki/Release-Process

---

Before releasing:

1. Make sure the version numbers are updated in the runningWithMaven.xhtml page
2. Make sure the GitHub issues and pull requests are associated with the GitHub milestone for this release.

---

Releasing Core:

1. Clone the main repo (with ssh), checkout the master branch
2. cd core
3. mvn release:prepare
4. mvn release:perform
5. Logon to https://oss.sonatype.org/
6. Find the mybatis staging repo
7. Verify everything looks OK (I usually delete the bundle files as they're not really maven artifacts)
8. Close the repo
9. Release the repo

---

Update the site:

The site deployment plugin is broken on Mac M1 and with newer keys on any platform. Therefore it is disabled in the normal release. Here's how to do it manually:

1. Clone the main repo and checkout the release tag. e.g.:

   git clone https://github.com/mybatis/generator.git cd generator git checkout mybatis-generator-1.4.2

2. cd core/mybatis-generator-core

3. mvn clean site

4. Checkout a copy of the main repo in a temp directory:

   mkdir ~/temp/temp-generator

... (truncated)

Commits

• 32b746c [maven-release-plugin] prepare release mybatis-generator-1.4.2
• 33c76e6 Skip site deploy - site plugin is totally broken
• a13d28c [maven-release-plugin] rollback the release of mybatis-generator-1.4.2
• 0e12bb2 [maven-release-plugin] prepare for next development iteration
• c23a850 [maven-release-plugin] prepare release mybatis-generator-1.4.2
• dc9782b Update Copyrights
• 64aa79f [maven-release-plugin] rollback the release of mybatis-generator-1.4.2
• a04ab7c [maven-release-plugin] prepare for next development iteration
• 1ef1f1a [maven-release-plugin] prepare release mybatis-generator-1.4.2
• cf65c62 [maven-release-plugin] rollback the release of mybatis-generator-1.4.2
• 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 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)