On 6 Sep 06, at 3:02 AM 6 Sep 06, Jason Dillon wrote:
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?
The initial idea long ago was to have a clear API reporting, we ended
up with Doxia which is a document generation API which is not quite
what we intended. I think what we're looking at here is a data api
but also a data collection api. I'm not so keen on RDF as the whole
system would probably end up being pretty slow, and if we're going to
use an XML type system then it would probably make sense to use
XRadar. It already completely works and I know the people who
developed it would love to help.
We initially wanted all the plugins to not only have Doxia sinks for
creating reports but also have a standard data sink so you could just
take a raw data and render it however you wish.
Anyway XRadar is here if we're just going to snag existing XML:
http://xradar.sourceforge.net/
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
