72Miles

Posts Mentioning RSS Toggle Comment Threads | Keyboard Shortcuts

• 

  Mike 11:24 pm on February 10, 2008 Permalink | Reply
  Tags: Architecture-Rules (13)   

  architecture-rules-2.0.3 

  Released architecture-rules-2.0.3 last month.

  Changes

  • issue-23 determine which dependencies are optional usability
  • issue-24 slashes in unix and windows are different, paths can not be read usability
  • issue-25 cycles test not run with XML configuration usability
  • release notes

  We have already fixed a couple of issue for the next release, and completed a handful of tasks that have made improvements to the library. We have been getting a lot of help from mykola.nickishov. Since he was submitting so many quality patches, we invited him to join the project as a committer. He he accepted. Thanks Mykola.

  We’ll make a release soon which will describe how to setup your pom.xml to pull down Architecture-Rules automatically, and enhance the CyclicReduendencyException message to point out the exact classes that are involved in the cycles, rather that just reporting on the package. If you can’t wait until the next release for these features, the subversion trunk has historically been stable, so you can checkout the project from source.

  Architecture-Rules

   

  Reply Click here to cancel reply.

  Name (required)

  Email (required)

  Web Site

  Notify me of followup comments via e-mail

   
• 

  Mike 6:34 pm on February 2, 2008 Permalink
  Tags: Architecture-Rules (13)   

  Architecture Rules 

  At 72 Miles, we not only heavily rely on open source software, but we also partake in open source software development. We created the project Architecture Rules in response to a tutorial on using JDepend to “assert architectural soundness”.

  Architecture Rules can be described as

  Assert Your Architecture! with this open source java library. Architecture Rules leverages an xml configuration file and optional programmatic configuration to assert your code’s architecture via unit tests or ant tasks. This test is able to assert that specific packages do not depend on others and is able to check for and report on cyclic dependencies among your project’s packages and classes. This project wraps a industry accepted JDepend to simplify the process of maintaining a solid software architecture.

  So far we have made a half dozen releases and have had a few of them submit patches and report some minor issues. We expect this project to eventually become a common tool under most developer’s toolbelts.

  Check it out at http://architecturerules.googlecode.com/svn/docs/index.html