Generic "maven site"-style software??

[Eric Griswold]

Hi,

Some of our non-Java teams are looking at the results generated
by the site-generation capabilities of Maven and have been asking
if there's something that can generate a build-results website with
the various reports: Findbugs, Code-coverage, etc that isn't tied to
a particular build methodology (like Maven) or CI server.

IOW, we're interested in something that can create a presentation from
the data it finds in the build tree as a result of running the build and
build-analysis tools.

Other requirements is that it must be Linux-based; FOSS is much preferred
over commercial.

Thanks in advance,
Eric

[Marc Girod]

On May 13, 4:22 pm, Eric Griswold <eric_grisw...@yahoo.com> wrote:

> IOW, we're interested in something that can create a presentation from
> the data it finds in the build tree as a result of running the build and
> build-analysis tools.

I don't use maven anymore (after changing jobs) and I don't
remember exactly what maven proper provided, and what
we got from CruiseControl or other tools.

I'd like to warn against the false transparency of visual
tools in general.
Most often, they result in fact in real opacity, i.e. in a
discontinuity of the chain of possible representations,
ending at a human-only interface.
The result is to replace semi-conductors with flesh: to
make SCM (i.e. tool supported management of
information) impossible.

So, be sure to produce the information in a parseable
format (greppable maybe... xml is often overkill and more
challenging), and only next to represent it graphically.
This you can do in a generic (independent from your
build tool) way, e.g. in perl (there are good modules to
easily produce all kinds of charts).

The posint is that you should try to avoid breaking the
access to specific outputs of different build tools.
'Build tool' is not a well-defined category, the members
of which would be interchangeable.

This is the area in which ClearCase shines with its
management of derived objects, allowing you to
compare existing DOs through their dependency trees.
When available, such functionality ought to be exposed.

Marc