⬆️(deps): Update database-rider.version to v1.44.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.github.database-rider:rider-cucumber	1.28.0 -> 1.44.0
com.github.database-rider:rider-junit5	1.28.0 -> 1.44.0
com.github.database-rider:rider-cdi	1.28.0 -> 1.44.0
com.github.database-rider:rider-spring	1.28.0 -> 1.44.0
com.github.database-rider:rider-core	1.28.0 -> 1.44.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

database-rider/database-rider (com.github.database-rider:rider-cucumber)

v1.44.0

Compare Source

Release notes

• Enable JSON Schema support #​600
• Respect @​DBRider in junit5 @​BeforeAll, @​BeforeEach, @​AfterAll, @​AfterEach methods #​601

Heroes

@​Micky002 @​vaa25

v1.43.0

Compare Source

Release notes

• Feature request: wildcard/regex support for skipCleaningFor in @​DataSet #​597
• Add dataset value attribute and provider attribute duplication use log #​599
• use java.util.Base64 instead of javax.xml.bind.DatatypeConverter for encoding Base64 #​591
• shouldExportJSONDataSetWithEscapedQuotes(ExportDataSetIt.java:176) for windows environment #​582

Heroes

@​tomlux @​netmikey @​coiouhkc @​diqksrk

v1.42.0

Compare Source

Release notes

• Extract base class MapDataSet from JSONDataSet, to simplify integration with other test frameworks #​569
• DataSetConfig should allow to configure DataSetProvider instance #​567
• Add SnakeYAML 2.x compatibility #​579
• keeping table export ordering indicated in "includeTables" #​581

Heroes

@​beskow @​xak2000 @​tomlux

v1.41.1

Compare Source

Release notes

• Fix rider-junit5 jakarta classifier #​565

Make sure to declare rider-core and rider-junit5 with jakarta classifier:

<dependency>
    <groupId>com.github.database-rider</groupId>
    <artifactId>rider-junit5</artifactId>
    <version>1.41.1</version>
    <scope>test</scope>
    <exclusions>
        <exclusion>
            <groupId>com.github.database-rider</groupId>
            <artifactId>rider-core</artifactId>
        </exclusion>
    </exclusions>
    <classifier>jakarta</classifier>
</dependency>
<dependency>
    <groupId>com.github.database-rider</groupId>
    <artifactId>rider-core</artifactId>
    <version>1.41.1</version>
    <scope>test</scope>
    <classifier>jakarta</classifier>
</dependency>

Heroes

@​jowko

v1.41.0

Compare Source

Release notes

• Add jakarta classifier for rider-junit5 module #​565

v1.40.0

Compare Source

Release notes

• Updated the version for tuprolog from 0.20.2 to 0.20.9. #​564
• Make rider-core compatible with jakarta persistence #​561

Now both rider-core and rider-cdi have the jakarta maven classifier

Heroes

@​abigailCortis @​HongHanh9527

v1.39.0

Compare Source

Release notes

• Dataset provider is lost during merge #​559

Heroes

@​mdiachuk

v1.38.1

Release notes

• Support quarkus 3.x in rider-cdi (#​496)

To use rider-cdi with quarkus 3 or any Jakarta application, enable the jakarta classifier in rider-cdi:

  <dependency>
      <groupId>com.github.database-rider</groupId>
      <artifactId>rider-cdi</artifactId>
      <version>1.38.1</version>
      <scope>test</scope>
      <classifier>jakarta</classifier>
      <exclusions>
        <exclusion>
          <artifactId>stax-api</artifactId>
          <groupId>stax</groupId>
        </exclusion>
      </exclusions>
    </dependency>

Heroes

@​DeMol-EE @​mkwapisz @​matjazs

v1.37.1

Compare Source

Release notes

• It's not possible to use dbunit.yaml (instead of yml) https://github.com/database-rider/database-rider/issues/548

Heroes

@​vladimirfx

v1.37.0

Compare Source

Release Notes

• It's not possible to use dbunit.yaml (instead of yml) #​548
• Execute statement with default options #​549
• Add support for skipping specific timescaleDB schemas during cleanup #​553

Heroes

tiagomistral, haoadoreorange, dfitisoff-k

v1.36.0

Compare Source

Release Notes

• Require JDK 8 as minimal java version (#​541)
• Prolog-like expected data set assertion (#​363)
• Inconsistent logging across framework (#​519)

Heroes

jowko and coiouhkc

v1.35.1

Compare Source

Release Notes

• Support xlsx dataset (#​525)
• Correct mysql-connector dependency to scope test (#​528)
• Only run release job in master (#​529)
• Add @​BeforeAll hook and documentation note to SpringBootDBUnitTest (#​513)

Heroes

@​opengl-8080 @​bergerst @​niels1voo

v1.35.0

Compare Source

Release Notes

• [MySQL] Schema resolver always returns null (#​505)

Heroes

@​coiouhkc

v1.34.0

Compare Source

Release Notes

• Read DBUnit configuration from system properties and environment variables (#​483)

Heroes

@​netmikey

v1.33.0

Compare Source

Release notes

In this release, we updated DBUnit to 2.7.3 and replaced org.codehaus.jackson by jackson-databind.

• cleaning DB does not work with H2 (#​461)
• Dependencies with vulnerabilities (#​478)
• Vulnerable version of jackson-mapper-lgpl (#​457)

Heroes

@​trks1970

v1.32.3

Compare Source

Release notes

• clearDatabase does not take table ordering into account (#​417)

Heroes

@​vincentstradiot

v1.32.2

Compare Source

Release Notes

• DisableConstraints=true for H2 executes non-H2 SQL Statement (#​375)
• Missing javax.annotation.Priority in DBUnitInterceptorImpl (#​384)
• Spring @​Transactional tests is broken in version 1.27 (#​365 )

Heroes

@​vkrauze @​JapuDCret @​bergerst @​jpbassinello

v1.32.1

Compare Source

Release notes

• Cannot read columnSensing config from dbunit.yml (#​379)

Heroes

@​entireboy

v1.32.0

Compare Source

Release notes

• Ability to handle property Map<String, Object> in EntityManagerProvider.instance() (#​364)

Heroes

@​duschata

v1.31.0

Compare Source

Release notes

• Usage of scripting in @ExpectedDataSet (#​358)
• DBRIDER-358 = add scripting support in @​ExpectedDataSet (#​359)

This release enables the use of javascript or groovy assertions in @ExpectedDataSet, for example, consider the following dataset:

USER:
  - ID: "js:(value > 0)"
    NAME: "js:(value != null && value.contains('@​realpestano'))"
  - ID: "groovy:(value > 0)"
    NAME: "groovy:(value != null && value.contains('@​dbunit'))"

To enable the scripting you mainly need the js: or groovy: prefix followed by an expression which evaluates to boolean inside a parentheses. The value in the expression refers to the actual value that should be in database after the test runs.

    @​Test
    @​DataSet(value = "yml/empty.yml", transactional = true)
    @​ExpectedDataSet(value = "yml/expectedUserWithScripting.yml")
    public void shouldEvaluateScriptsInExpectedDataSet() {
        User u = new User(1);
        u.setName("@​realpestano");
        User u2 = new User(2);
        u2.setName("@​dbunit");
        em().persist(u);
        em().persist(u2);
    }

Heroes

@​coiouhkc

v1.30.0

Release Notes

• Add alwaysCleanBefore and alwaysCleanAfter DBUnit properties (#​355)

Heroes

@​raphiz

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codeclimate]

Code Climate has analyzed commit 5f845cf and detected 0 issues on this pull request.

View more on Code Climate.