Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various cleanup to help with maintenance / release process #3337

Merged
merged 4 commits into from
Dec 28, 2024

Conversation

hazendaz
Copy link
Member

  • Dropped old contributors list as not valid place to store that these days. The user list there is mostly unrecognized contributors from long ago. Since we have used git for ~10 years if not more, no reason to store such data as the commit history shows all that. Also believe history was exported for google code so it should also have that information per commit.
  • Remove the pre java 16 profile as we require java 17+
  • Drop derby version in java16+ as we require 17 and the default is already set for java17+
  • Add some adjustments (also added to parent for 49 release) that allow us to release this without messing with extra flags.

Upon this build will effectively build java 8 compliant code without thinking about it.

we cannot validate this data is even valid and best guess is many of these contributors have not contributed in many, many years.  Git history is sufficient to maintain this sort of data.  removing from the pom.
…d remove changing to java 16 with java 16+

Only tests needed the higher value, remove that as unnecessary.  Tests remain compliant with java 17+ at this point.  This further fixes the resulting binary so it doesn't matter what jvm we use to release with and no extra overrides are necessary
@hazendaz hazendaz self-assigned this Dec 28, 2024
@coveralls
Copy link

Coverage Status

coverage: 87.171% (-0.01%) from 87.183%
when pulling 551ba16 on hazendaz:pom-cleanup
into d20ac1d on mybatis:master.

@hazendaz hazendaz merged commit 266542a into mybatis:master Dec 28, 2024
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants