Fixed major issue with 2.1.0 that prevented packages defined with wildcards from even being investigated. Caused when issue-45 was fixed.

1. architecture-rules-2.1.1.jar
2. architecture-rules-2.1.1-sources.jar
3. architecture-rules-2.1.1-test-sources.jar

Maven 2 – pom.xml

1. <groupId>com.seventytwomiles<groupId>
   <artifactId>architecturerules<artifactId>
   <version>2.1.1<version>
       

Also, you must add our maven repository.

Javadocs

This version’s (2.1.1) api documentation (javadocs) are available here.

Changes

• issue-54 report class creating the cyclic redundancy usability

This big release, one year after the initial public release of Architecture Rules, finally offers wild card support. You can now use .* and ..* when defining packages to specify one package, or many sub-packages respectively. We’ve also added support for configuration method chaining, better Exception class hierarchy and metadata, and new tests, javadocs, and a copy of the Apache 2.0 License in the archive.

1. architecture-rules-2.1.0.jar
2. architecture-rules-2.1.0-sources.jar
3. architecture-rules-2.1.0-test-sources.jar

Javadocs

This version’s (2.1.0) api documentation (javadocs) are available here.

Changes

• issue-12 report class creating the cyclic redundancy usability
• issue-27 make testArchitecture() public usability
• issue-28 configuration method chaining usability maintainability
• issue-37 package license file
• issue-39 maven-license-plugin
• issue-40 support for wildcards usability
• issue-42 provide API to retrieve list of violations usability
• issue-43 Exceptions should implement an ArchitectureRulesException
• issue-44 meaningful defaults with maven plugin usability
• issue-45 JPackage equals method not symetric
• issue-46 classpath conflict with common-io and spring usability