Changelog History
Page 2
-
v0.9.2 Changes
November 11, 2018 -
v0.9.1 Changes
August 20, 2018๐ Bug Fixes
- ๐ Fixed a bug where classes in Jars with white spaces (like Kotlin class files could have) cause an exception during the import (see #103)
-
v0.9.0 Changes
August 19, 2018Important
๐ The Maven coordinates for
com.tngtech.archunit:archunit-junit
have changed, since there is now support for JUnit 4 and JUnit 5. The new coordinates for the equivalent artifact are nowcom.tngtech.archunit:archunit-junit4:0.9.0
โจ Enhancements
Core
๐
archunit-ignore-patterns.txt
can now contain comments (see #88; many thanks to @bedla)a
JavaClass
'directDependenciesFromSelf
anddirectDependenciesToSelf
now contain further dependencies. This affects many rules as well, likelayeredArchitecture()
which might now detect more violations than before. In particular dependencies now contain dependencies from- fields of a certain type
- method/constructor parameters of a certain type
- method return types
๐ (see #92 and #96; many thanks to @msherman32)
๐ the plugin mechanism activating Java >= 9 support now supports EA versions (see #93; many thanks to @jqno)
Lang
- ๐ the rule API now supports a concise way to assert properties of a single class (see #60; many thanks to @msherman32)
- ๐ the rule API can now assert that classes
haveOnlyFinalFields()
(see #86; many thanks to @bgalek) - ๐ the rule API now allows to assert that there are at least / at most / exactly
x
classes matched by a rule (see #83; many thanks to @bedla) - rules can now be derived from PlantUML component diagrams (compare the User Guide; see #4; many thanks to @msherman32)
- ๐ the rule API now allows to check more general for dependencies instead of just accesses (like interfaces, field types, method parameters, ...) (see #69)
- ๐ the rule API now includes several methods to restrict what classes should "only" do, i.e.
classes().should().onlyDependOnClassesThat()...
oronlyCallMethodsThat(..)
, etc. (see #84)
JUnit
- ArchUnit now offers extended JUnit 5 support (compare the User Guide; see #34)
Kotlin
- rule suits with JUnit 4 / JUnit 5 can now be written in a concise way and source locations are reported correctly (compare the User Guide; see #77)
-
v0.8.3 Changes
July 20, 2018๐ Bug Fixes
๐ Fixed bug where deeply nested super classes missing from the import were not resolved correctly from the classpath (see #91; many thanks to @svenackermann for reporting and debugging)