ArchUnit v0.9.3 Release Notes
Release Date: 2018-11-20 // over 5 years ago-
๐ Bug Fixes
๐ Fixed memory leak in combination of the newly added
ArchRule.AssertionError
and JUnit 4. JUnit 4 keeps references to all thrownAssertionErrors
through the whole run. SinceArchRule.AssertionError
kept a reference toEvaluationResult
this could consume a lot of memory, if the respective results were big.
๐ This release removesArchRule.AssertionError
(introduced in version 0.9.0).๐ฅ Note that this is in theory a breaking change , since it would have been possible to catch and process
ArchRule.AssertionError
. There does not seem to be any clean solution to this problem though, and due to the slim probability that the removal of this part of the API will in fact affect any user, the step seems justified.๐ If anybody should against all odds have a problem with this, feel free to open an issue and we will find a different solution.
โ Also
ArchUnitTestEngine
's engine id has been adjusted fromjunit-archunit
toarchunit
to get rid of the warning JUnit 5 emits since version1.3.0
.