No Huddle Offense

"Individual commitment to a group effort-that is what makes a team work, a company work, a society work, a civilization work."

OSGi dependencies

November 25th, 2008 • 1 Comment

I have been a great fan of pushing the degree of automation to a limit. And as stated in this blog post: Software engineering and as a follow up of OSGi dependencies and OSGI  Best practices: I now present  the consistency and OSGi dependency checker 🙂

The setting is a multi modul maven project for a OSGI based application – with all the nice maven features turned on (reports (all kind off), scm, issue tracker, mailinglist, etc) – so to speak of a complete Software Development Environment.

The broken window principal says:

"Consider a building with a few broken windows. If the windows are not repaired, the tendency is for vandals to break a few more windows. Eventually, they may even break into the building, and if it's unoccupied, perhaps become squatters or light fires inside.
Or consider a sidewalk. Some litter accumulates. Soon, more litter accumulates. Eventually, people even start leaving bags of trash from take-out restaurants there or breaking into cars."
Source: wikipedia

And to prevent the broken window principal I implemented a small tool doing some of this stuff:

As a result you get e.g. a report and a graph.


The second part of the tool is maybe even nicer 🙂 Beside all the good reports and tools you can use like findbugs, pmd, checkstyle, and others; sometimes I’m missing the very basic stuff. I implemented some consistency checks which can check for the following stuff, and verify the consistency of your project:

You could integrate those checks in the build systems or even force them on checkin like svnchecker does. Or you can use it to generate reports.

One response to “OSGi dependencies”

  1. Robert says:

    Nice stuff. Might be a good idea to implement it as a maven plugin.