v2.0.0

What's New

New Feature: Synthetic Data Integration

We have enhanced the Java-Artefacts and improved the Mock Energy Data Holder's API responses by utilising test datasets generated by our Test Data Cli tool.
Earlier this year, we introduced a new Test Data CLI tool that allows you to generate synthetic datasets tailored to the specific requirements of a mock data holder. These datasets are generated in JSON format, making them easy to work with and customise.
The Energy mock data holder of the Java artefacts has been updated to seamlessly consume these synthetic datasets. With this release, we provide clear examples and documentation on how to leverage the test data files within your project. Users can simulate realistic scenarios and responses to Energy API calls, which can make their testing and development process more robust and efficient. The synthetic datasets can be customised to mimic various data scenarios, enabling users to comprehensively test their application's behaviour under different conditions.

Dependency Update: H2

Bumps h2 from 2.1.210 to 2.2.220 in data-holder. The update is automatically raised by Dependabot to ensure that we benefit from the latest enhancements, security fixes, and improvements offered by the H2 Database library.

Versioning Strategy Update

With this release, we want to provide clarity about a change in our versioning strategy to better align with industry standards and project development goals. Beginning with version 2.x.x, Java Artefacts adheres strictly to the widely recognised Semantic Versioning (SemVer) scheme.

Why we are adopting SemVer semantics?

Up until version version 1.24.0, Java Artefacts did not strictly follow SemVer versioning. In our previous versioning approach, we aimed to mirror the Consumer Data Standards (CDS) version we aligned with, resulting in version numbers like 1.22.0 and 1.24.0. However, this approach had some limitations, especially when bundling multiple CDS version changes into a single release. Users had to read the release notes to determine which changes will impact them, whether changes from multiple CDS versions were bundled etc, which made it hard to navigate changes.
To address this, we are now transitioning to adopt SemVer more strictly to provide a more consistent and meaningful versioning system. While this version may appear to be a major jump from our previous release (1.24.0), this is merely a change to our release policy to be consistent with industry practices and improve the developer experience. We will continue to update Java-Artefacts to align with new CDS versions. We are excited about the possibilities this transition brings and remain dedicated to delivering high-quality, feature-rich, and stable releases in the future.

Full Changelog: cds-java-artefacts-1.24.0...cds-java-artefacts-2.0.0