This sounds a lot like what was discussed back when components went through
Java 6 -> 7 and later Java 7 -> 8 upgrades. So far, we’ve only made Java
requirement updates in the minor version, not the patch version, and as Gary is
saying, we wouldn’t bump the major version without renaming the
There's no rule that you have to change the package name and Maven
coordinates with a major version bump. As long as the API is
compatible, it's OK to keep those. But breaking compatibility with
Java 8 is a pretty big step forward.
The goal is to allow people to produce and accept bug fixes in
Having a new major version for everything is not going to help I'm afraid.
A major new version does not imply a Java platform change. The Maven
tooling is missing a feature to the display dependency updates goal that
let's you specify a maximum Java version, or maybe that exists but i doubt
it.
As a consumer, I would prefer all java version changes to be considered
major breaking changes for all apache commons components.
I've waste lots of hours trying to find the oldest released version that
supports a specific java version as the project can't yet upgrade for
various reasons.
On
On Sun, 15 Oct 2023 at 15:37, Elric wrote:
>
> On 15/10/2023 16:31, Gary Gregory wrote:
> > A major version bump is rather heavy handed when no one is asking for a
> > "real" 2.0 with breaking changes.
>
> Agreed. My 2 cents: a minor version and a clear release note is plenty.
> Critical bug
On 15/10/2023 16:31, Gary Gregory wrote:
A major version bump is rather heavy handed when no one is asking for a
"real" 2.0 with breaking changes.
Agreed. My 2 cents: a minor version and a clear release note is plenty.
Critical bug fixes can still be made by bumping the patch version,
A major version bump is rather heavy handed when no one is asking for a
"real" 2.0 with breaking changes. A major bump would imply a package name
and Maven coordinate change. At least that's what we have done before for
major version changes. We've also done major version changes without those
Not a library I use so I don't have a horse in the race. However, I do
recommend making this a major version bump to 2.0 so as not to close
off the possibility of critical fixes for folks still on older JDKs.
On Sun, Oct 15, 2023 at 8:42 AM Gary Gregory wrote:
>
> We've recently released DBUtils
We've recently released DBUtils after a long period of inactivity. Java 21
is also out. I plan on raising the floor for this component to Java 11 and
GitHub builds will keep testing on Java LTS 11, 17, 21. I've not seen any
Java 21 issues yet.
Gary
