Skip to content

Releases: kennedykori/jutils

v2.0.0

23 Jan 08:25
47dbfd0
Compare
Choose a tag to compare

2.0.0 (2024-01-23)

⚠ BREAKING CHANGES

  • change base package name from com.kori_47.utils to io.github.kennedykori.utils.

This change has been necessitated by the
shutdown of Bintray.
As such, the project will be migrating to Maven Central as the primary
hosting platform for the project binaries. Maven Central is a more
stable hosting service. Hopefully, this will result in a better and
more reliable experience.

A change of the base package name is a breaking change and will result in a new major release.

Migrate from v1.x.x to v2.x.x

Change the import statement as follows:

-import static com.kori_47.utils.ObjectUtils.*;
+import static io.github.kennedykori.utils.ObjectUtils.*;

That's it. The library API remains the same.

  • change base package name

A change of the base package name is a breaking change and should
result in a new major release.

Features

Refactors

v2.0.0-dev.1

13 Jan 22:31
Compare
Choose a tag to compare
v2.0.0-dev.1 Pre-release
Pre-release

2.0.0-dev.1 (2024-01-13)

⚠ BREAKING CHANGES

  • change base package name from com.kori_47.utils to io.github.kennedykori.utils.

This change has been necessitated by the
shutdown of Bintray.
As such, the project will be migrating to Maven Central as the primary
hosting platform for the project binaries. Maven Central is a more
stable hosting service. Hopefully, this will result in a better and
more reliable experience.

A change of the base package name is a breaking change and will result in a new major release.

Migrate from v1.x.x to v2.x.x

Change the import statement as follows:

-import static com.kori_47.utils.ObjectUtils.*;
+import static io.github.kennedykori.utils.ObjectUtils.*;

That's it. The library API remains the same.

  • change base package name

A change of the base package name is a breaking change and should
result in a new major release.

Features

Refactors

v1.2.0

23 Jan 01:25
66f18c9
Compare
Choose a tag to compare

The following static utility methods were added in these release:

  • Methods for checking if a number is equal to a given base value.
  • Methods for validating if a number is equal to a given base value.

A number in this context includes the following primitives: int, long, float, double and instances of the java.math.BigDecimal class.

v1.1.0

19 Dec 20:51
Compare
Choose a tag to compare

The following static utility methods were added in these release:

  • Methods for checking and validating if a number is less than a given base value.
  • Methods for checking and validating if a number is less than or equal to a given base value.
  • Methods for checking and validating if a number is greater than a given base value.
  • Methods for checking and validating if a number is greater than or equal a given base value.

A number in this context includes the following primitives: int, long, float, double and instances of the java.math.BigDecimal class.

Initial Release

18 Oct 23:08
Compare
Choose a tag to compare

The initial release has one utility class which is composed of static methods that can be used to:

  • Check if a number is negative.
  • Check if a number falls within a specified range.
  • Validate that a number is not negative.
  • Validate that a number falls within a specified range.

A number in this context includes the following primitives: int, long, float, double and instances of the java.math.BigDecimal class.

  • Check if an object is serializable, i.e, the object implements the java.io.Serializable interface.
  • Validate that an object is serializable, i.e, the object implements the java.io.Serializable interface.
  • Check if the length of a java.lang.String falls within a given range.
  • Check if the length a java.lang.String is less than a specified value.
  • Check if the length of a java.lang.String is greater than a specified value.
  • Validate that the length of a java.lang.String falls within a specified range.
  • Validate that the length of a java.lang.String is less than a specified range.
  • Validate that the length of a java.lang.String is greater than a specified range.
  • Check that a java.lang.String is not empty.
  • Validate that a java.lang.String is not empty.

It should be noted that the methods that check for a given condition generally return true if the condition is met or false otherwise. Conditions that validate that a value meets a given condition will return the value if the value passes the checks or otherwise throw a java.lang.IllegalArgumentException.