Bump org.cassandraunit:cassandra-unit from 4.3.1.0 to 5.4.0

[dependabot]

Bumps org.cassandraunit:cassandra-unit from 4.3.1.0 to 5.4.0.

Release notes

Sourced from org.cassandraunit:cassandra-unit's releases.

5.4.0

Changed

• The jamm memory-meter agent is no longer needed. The surefire setup consumers copy loses three of its lines: -javaagent:${com.github.jbellis:jamm:jar}, -Djdk.attach.allowAttachSelf=true, and the whole maven-dependency-plugin properties execution that existed only to resolve that path. What remains is one plugin and the JPMS --add-exports / --add-opens set.

  Cassandra never required the agent unconditionally: ObjectSizes builds its meter as MemoryMeter.builder().withGuessing(INSTRUMENTATION_AND_SPECIFICATION, UNSAFE), a fallback chain, so with no agent loaded it measures through Unsafe instead. Object sizes are then derived from field offsets rather than from instrumentation, which shifts memtable accounting slightly in a node holding a test fixture. The full suite passes either way.

  This removes the most error-prone part of the setup. An unresolved ${...} agent path killed the fork before surefire could report anything, surfacing only as The forked VM terminated without properly saying goodbye — the single most common first-run failure.

  Projects on 5.3.0 and earlier must keep all three. Their instructions are unchanged.

---

Maven Central: https://central.sonatype.com/artifact/org.cassandraunit/cassandra-unit/5.4.0 Full commit log: jsevellec/cassandra-unit@cassandra-unit-parent-5.3.0...cassandra-unit-parent-5.4.0

5.3.0

Added

• Spring Boot tests work with no wiring. Annotate a @SpringBootTest class with @EmbeddedCassandra and the node's address is published into the test's Environment as spring.cassandra.contact-points, spring.cassandra.port and spring.cassandra.local-datacenter before the context refreshes, so Boot's auto-configured CqlSession connects to the embedded node instead of to the driver default of 9042.

  This is what issue #217 asked for in 2017. It matters most with @EmbeddedCassandra(configuration = "cu-cassandra-rndport.yaml"), where the port is chosen at startup and so cannot be written into a properties file at all.

  The mechanism is a ContextCustomizerFactory registered in META-INF/spring.factories. It returns null for any class without the annotation — contributing nothing, not even a context cache key entry — and names no type from cassandra-unit, so a project using this module for one test class does not load the embedded server for the rest.

• @EmbeddedCassandra(exposeProperties = false) turns that off, for tests that set spring.cassandra.* themselves and want their own values to win.

• org.cassandraunit.SpringSessions, in cassandra-unit-dataset, loads fixtures through a

... (truncated)

Changelog

Sourced from org.cassandraunit:cassandra-unit's changelog.

5.4.0 (2026-09-20)

Changed

• The jamm memory-meter agent is no longer needed. The surefire setup consumers copy loses three of its lines: -javaagent:${com.github.jbellis:jamm:jar}, -Djdk.attach.allowAttachSelf=true, and the whole maven-dependency-plugin properties execution that existed only to resolve that path. What remains is one plugin and the JPMS --add-exports / --add-opens set.

  Cassandra never required the agent unconditionally: ObjectSizes builds its meter as MemoryMeter.builder().withGuessing(INSTRUMENTATION_AND_SPECIFICATION, UNSAFE), a fallback chain, so with no agent loaded it measures through Unsafe instead. Object sizes are then derived from field offsets rather than from instrumentation, which shifts memtable accounting slightly in a node holding a test fixture. The full suite passes either way.

  This removes the most error-prone part of the setup. An unresolved ${...} agent path killed the fork before surefire could report anything, surfacing only as The forked VM terminated without properly saying goodbye — the single most common first-run failure.

  Projects on 5.3.0 and earlier must keep all three. Their instructions are unchanged.

5.3.0 (2026-09-20)

Added

• Spring Boot tests work with no wiring. Annotate a @SpringBootTest class with @EmbeddedCassandra and the node's address is published into the test's Environment as spring.cassandra.contact-points, spring.cassandra.port and spring.cassandra.local-datacenter before the context refreshes, so Boot's auto-configured CqlSession connects to the embedded node instead of to the driver default of 9042.

  This is what issue #217 asked for in 2017. It matters most with @EmbeddedCassandra(configuration = "cu-cassandra-rndport.yaml"), where the port is chosen at startup and so cannot be written into a properties file at all.

  The mechanism is a ContextCustomizerFactory registered in META-INF/spring.factories. It returns null for any class without the annotation — contributing nothing, not even a context cache key entry — and names no type from cassandra-unit, so a project using this module for one test class does not load the embedded server for the rest.

• @EmbeddedCassandra(exposeProperties = false) turns that off, for tests that set spring.cassandra.* themselves and want their own values to win.

• org.cassandraunit.SpringSessions, in cassandra-unit-dataset, loads fixtures through a CqlSession bean from the test's ApplicationContext:

  CqlDataSetExtension.using(SpringSessions.fromApplicationContext())

... (truncated)

Commits

• 69a591e [maven-release-plugin] prepare release cassandra-unit-parent-5.4.0
• 6b036f9 docs: changelog for 5.4.0
• a6f1ad2 chore: github release when releasing
• 68f48bb docs: adjust docs again
• 3afb878 docs: adjust the docs again
• 257f9b9 docs: adjust the doc again
• 6af4e23 docs: adjust docs
• 3bab391 feat: drop the jamm agent from the surefire setup
• 060c821 chore: pom description adjustment
• 7e329a7 [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)