On 8/31/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote:
 1. a base plugin to create initially the RDF database and populate it
 with basic pom's information
 2. a modified compiler plugin to store source files structure
 information
 3. a modified surefire plugin to store test results in the graph
 attached to the test source files and projects
 4. a modified test report lpugin that would take advantage of the RDF
 graph to generate aggregated reports

Why don't you implement the collection and RDF submission into a
post-process... so that you don't need to modify existing plugins, but
just provide RDF builders that take a plugins output (like surefire's
xml reports) and turns that into RDF and submit it to the reporting
server?

There are some folks at the Geronimo project who may be interested in
something like this too.  A few of us have been talking about a
similar system to upload reports, and then a webapp to query the data
and produce nice roll up views and pretty graphs.

I spent some time pondering the idea today and it seems relatively
easy to do.  A goal of the plugin would get executed from the
top-level module when the build starts, to create a ticket or
something (and capture system details and basic build intel), then
modules execute, run reports, etc, and then run a report goal, which
processes a number of configured "builders" that take the output of
previously run maven plugins and converts them into a common xml
format, and then uploads the data to the reporting server with the
ticket.

All aggregation is handled by the reporting server.  Based on the
ticket and the module's pom details the server should be able to
correlate all of the modules reports and produce a roll up for that
build, and access to other builds (and roll ups of those builds) and
of course drill down into the details which were submitted, yada yada
yada.

Anyways, just some thoughts ;-)

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to