First, thanks to everyone who has stuck with this project so far. I have received input and feedback from every user on the mailing lists. Thanks for sticking with us this far, supporting this project, and giving the time to give back to the project through submitting issues, talking to us here on these lists, and talking through instant messengers.
Second, the reason for the email is to share that I released 2.1.0 of Architecture Rules tonight. It has been a long time since the last release and we have added some great new features, fixed some big issues, and made a few minor improvements to the API (hopefully without breaking any backwards compatibility.) You can checkout the release page for a complete list of changes. I've also added a blog post to introduce some of the new features, and to introduce the project to developers. The blog post also lays out a road map for the next release, which will probably be 3.0.0 given the changes that I'd like to see made.
2.1.0 release, download, and changes:
http://72miles.com/architecturerules/releases/release-2102.1.0 blog post:
http://72miles.com/blog/posts/category/open-source/architecture-rules/
for maven2 users:
http://72miles.com/architecturerules/maven-repositoryThe biggest new features is the support of wildcard package names. You can read how to add wildcards to your existing configurations or new configurations either in the documentation or on my blog post about wildcard support.
wildcard documentation:
http://72miles.com/architecturerules/sample-configuration#wildcardswildcard blog post:
http://72miles.com/blog/posts/architecture-rules-wildcard-support/
Please upgrade to 2.1.0 and please take the time to report any issues or ask any questions that you may have at the user group
architecture...@googlegroups.com.
Thanks everyone.
~ Mike Nereson
~
http://72miles.com/blog