Releases: mybatis/parent
Mybatis Parent 48
- Plugin Updates
- Allow java 17, 21, 23, 24, 25 to build with
- Target java 17 now
- Require maven 3.9.9 to build project
- Set bcel via property instead of directly
note: 47 not released as attempt to remove developer block due to git supplying similar and more accurate data turned out to be required by maven central requirement checks. Restored as it was for now with note to review and remove those that are no longer active on project so there is a balance on the central requirement and removal of likely stale data.
Mybatis Parent 46
Updated plugins / libraries
This was done per user asking due to issues with doxia 2 causing on downstreams. I'm not at all convinced that Maven got this working properly yet but this is on the final copies and few patches since. So the point of the release is just to confirm site pages. No other items should be expected.
Do note this is still on java 11.
Mybatis Parent 45
Parent
- Require java 17 to build and allow java 24 (full matrix: 17, 21, 22, 23, and 24)
- Add 'edu' import to impsort group
- Require maven 3.9.8 to build
- Update plugins / dependencies
- Drop profile to allow < java 17 for building
- Drop java 8 from osgi headers. If downstream still needs them, add them back as follows
<bnd>
-removeheaders: JAVA_1_8_HOME,JAVA_8_HOME,JAVA_11_HOME,JAVA_17_HOME,JAVA_21_HOME,JAVA_22_HOME,JAVA_23_HOME,JAVA_24_HOME
</bnd>
GHA
- Drop java 11 from matrix
- Add java 24-ea to matrix
- Bump maven to 3.9.8
Mybatis Parent 44
- Plugin / Dependency Updates
- Move to java 11 runtimes
- Require maven 3.9.7
- Bump maven wrapper to 3.3.2
- Update GHA
- Drop codeql as it doesn't seem to work with pom only projects
- Remove 'unlicensed' from license plugin as now in default core license plugin
note: Eventual plan is to move to java 17. For now, just moving to 11 so we can coordinate updates throughout mybatis projects in orderly fashion.
Mybatis Parent 43
Usage
- Allow jdk 23 usage
- Update plugins / Update dependencies
- Add sonar override to management at latest
Build
- Fix sonar.logon
- More https
- Fix renovate config
- Add codeql gha but needs some work to be usable. Mainly the matrix language needs setup.
Mybatis Parent 42
- Plugin updates / dependency updates
- Fix to 'url'
- Bump copyright to 2024
- Add hack to control 'topSiteURL' to get around maven bug with staging. For multi module builds, this must be set to empty and site GHA adjusted for same. For example, if project spring-boot-starter, the staging ends up one folder higher than staging as spring-boot-starter.git.
- Remove old hack for versions plugin to see the parent release. Maven now supports that out of the box as a new report.
- Require maven 3.9.6 to build
- Updated readme to reflect current state
Mybatis Parent 41
-
[POTENTIALLY BREAKING] Move from maven-bundle-plugin to bnd-maven-plugin. Note that bnd plugin which is replacement of the older one does not provide
include resources
. However, not sure how valuable that was given it pointed to our source code path for resources and included mention of license / notice which doesn't seem necessary for OSGI. -
[BREAKING] Upgrade maven site to site 2.0.0 (changed from decoration xsd). Downstream sites needs same upgrade and when using multiple languages, add 'default' instead of 'en' otherwise it will sub packages 'en' whereas it used to treat that as default.
-
Enable sort pom by default (currently all underlying usage sorted manually via plugin)
-
Pick up impsort groups for config,de,examples from mybatis dynamic sql
-
Add git commit id to the javadoc jars as well
-
Hard fork of coveralls plugin to my fork (com.github.hazendaz.maven) to incorporate all changes from various upstreams and dropping dependency on bind-api (javax namespace)
-
Bump bnd plugin to 7.0.0 and drop back to 6.4.1 for java 16 or lower builds (plugin is at 6.4.0 on older builds)
Build
- Added 'site' GHA in order to show how to on demand run site distribution as current maven process only handles single module builds. This requires a level of setup in GHA with a key added for the process. Therefore its existence is not enough to use it. These will be setup across all of mybatis in coming weeks.
Mybatis Parent 40
- Plugin updates
- Drop support of jdk 20
- Move maven site to 4 milestones
- Secure the sites for logo and blog for mybatis
- Require maven 3.9.5 as applied long overdue fixes from maven
- For arrays in maven plugins use correct naming. Maven does not care but it makes more sense.
- Disable modular via legacy Mode for javadocs given issues we are facing
- Drop jdk 20 from osgi and add jdk 22
- Prohibit legacy license usage
- Remove m2e license setup as now part of plugin per 4.3
- Adjust m2e flags for compiler to match that of my base-parent to avoid potential issues
- Fill in taglist plugin entirely
- Patch bcel to secure version on clirr plugin
Mybatis Parent 39
- Plugin updates
- Allow jdk 22 to build
Mybatis Parent 38
BREAKING CHANGES INCLUDED IN THIS RELEASE
- General library / plugin updates
- Removed left over bit of the ci-only profile mybatis core used as that was removed as it didn't work well. This has no impact as removal in downstream usage was already previously done.
- Removed 'useReleaseProfile' from release plugin as we used the default 'false' and its deprecated
- Switched whitespace maven plugin used for trimming files to my forked copy which is greatly upgraded over original.
- Drop jdk 18/19 from osgi headers
- Drop jdk 19 support in builds
- Update license plugin to use non deprecated license sets, if downstream project has special exclusions, it will need updated to same or it will break expectations.
- Set required maven version to 3.5.0 to build as one plugin requires it.
- Rewrite site distribution from obsolete wagon-git to using standard maven. This will work well for single module projects. Any multi module will have issues with this setup at the current time. This was an acceptable staged approach due to overhead on multi module sites. In those cases, set site to be skipped during release and manually deploy instead until further work can be addressed. Do note that the mybatis-parent gh-pages was quite corrupted by sub projects so that could be a possible issue elsewhere. The scm publish used with this will try to clean that up but in case of this project failed to do so on windows requiring manual cleanup.
- Drop surefire arg for jdk attach allow attach self as deprecated and used for jmockit which was itself not using correctly and long since works differently
- Dropped changes plugin as it is not very well on newer projects and we no longer use changes.xml
- Added rewrite plugin into formatting to enforce star imports not used.
- Remove 'additionalParam' usage from javadocs as long since deleted and our javadocs are ok since