Progrommatic control of dialyzer

Eric Merritt cyberlync@REDACTED
Wed Jun 14 21:46:28 CEST 2006

Very cool, It seems that I missed that project when I started this. It
looks like really good stuff as well. However, I don't think there is
too much duplication though the two projects have somewhat similar low
level functionality the purpose and direction seem to be pretty

The goal for my project is to build and test modules as they change
giving the developer immediate feedback during his work cycle. There
are also the secondary goals of automating a lot of the more difficult
aspects of managing erlang projects, like the whole release management
thing. For now that means that I make the assumption that the project
uses an otp style layout to make this automation possible. In any
case, it's not really meant as a continuous build system, that's just
the easiest way to describe it.  That's why I don't think that we are
duplicating each other.

On 6/13/06, Gordon Guthrie <gordonguthrie@REDACTED> wrote:
> Eric
> There is a continuous build script for Erlang in the jungerl. The full
> documentation is available here:
> It can do some or all of the following:
> * check out from CVS
> * run a compile
> * run a test suite
> * run the dialyzer
> * run a tsunami load test
> All the outputs can be graphed and sent up to a web site.
> At the moment I also have a rough cut of a web site spider enginge that will
> follow all your hyperlinks but it is too shonky to be shown to the world. When
> it is finished I will integrate it.
> Gordon
> Quoting Eric Merritt <cyberlync@REDACTED>:
> > Is there some method to control and use dialyzer pragmatically? I have
> > been fiddling with something akin to a continuous build system for my
> > erlang projects with support for unit tests and the like. I would like
> > to add support for dialyzer and an API would make that simpler. The
> > R11 docs only cover the command line version but just because
> > something isn't documented doesn't mean it doesn't exist. Hence this
> > question to the list.
> >
> >
> -------------------------------------------------
> This mail sent through IMP:

More information about the erlang-questions mailing list