ter
{{Release |number=2.1.1 |description=Fixed major issue with 2.1.0 that prevented packages defined with wildcards from even being investigated. Caused when [http://code.google.com/p/architecturerules/issues/detail?id=54 issue-45] was fixed. |groupId=com.seventytwomiles |artifactId=architecturerules |changeslist=[http://code.google.com/p/architecturerules/issues/detail?id=54 issue-54] report class creating the cyclic redundancy ''usability'' |buzzlist=*[http://www.theserverside.com/news/thread.tss?thread_id=49953 theserverside.com] *[http://blog.architecturerules.org/architecture-rules-210-release/ blog.architecturerules.org] }}
Template Body:
See Releases for a complete list of releases and for information on scheduled upcoming releases.
Released on {{{releasedate}}}
{{{description}}}
Update your pom to include the Maven Repository and add this dependency:
<dependency>
<groupId>org.architecturerules</groupId>
<artifactId>architecture-rules</artifactId>
<version>{{{number}}}</version>
</dependency>
architecture-rules-{{{number}}}.jar architecture-rules-{{{number}}}-sources.jar architecture-rules-{{{number}}}-test-sources.jar
You may be able to check this release out from SVN via the {{{number}}} tag.
Browse the repository to here to see if it exists.
If it does, check it out with
svn checkout http://architecturerules.googlecode.com/svn/tags/architecture-rules-{{{number}}}
This version’s ({{{number}}}) API documentation (javadocs) are available here.
Architecture Rules {{{number}}} mentioned around the Internet:
see Template:Release