Arnaud Bailly-3 wrote: > > Hi, > A couple of weeks ago I posted a proposal about a centralized > reporting feature for maven that would allow easy aggregation of > information at whatever level is needed. This proposal is centered > around the idea of creating and maintaining a RDF database that could > be used by plugins to find information or store information to be > latter processed by other plugins or external tools. > > I am trying to implement a small proof of concept without modifying > maven base codebase and using only plugins. I plan to do the > following: > 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 >
Hi Arnaud, I'm afraid I not replying to answer your questions but I am very excited that someone is taking this on! I've always felt that the Maven reporting system is one of its most underleveraged features. For me the killer feature list reads: dependency management, reporting, build lifecycle, plugin architecture and POM. What I have found from promoting a low-cost (read open-source or cheap such as JIRA/Confluence) ALM environment based upon Maven and Eclipse (as the integration backbones) is that it's Mavens ability to construct a complete project portal, snapshotted from the current source base, that has senior management, CMMi experts and a industry luminaries alike (no names but we're talking gang-of-four level) all 'ooh-ing' in their seats. Information sharing, collaboration and, critically, governance reporting and enforcement (be it tests reports, quality metrics, heuristics, plan adherence, etc) are seen as essential if an organisation is to properly manage its distributed and sub-contracted software development projects (read: without there being an overworked technical lead/architect burning midnight oil trawling through artefact repositories, running bespoke tools, updating spreadsheets and generating management reports:)) I would like to suggest to the maven core team, and i feel cheaky saying this as i know how busy they are and how hard they work (deseve a medal I tell you, or at the least an IPO!) is that they properly invest in the reporting side of things. Currently the reporting plugins don't have the same support that build plugins have in terms of standard Maven features (e.g. plugin configuration, dependency managemnt) and many aspects of the reporting environment are just not as well developed or thought out as other areas of Maven are (e.g. hardcoded project-info reports, difficulties integrating bespoke reports/pages into the site environment, lack of a framework to support project measures, etc). The development of a proper maven/apache framework to supports report/measure execution, storage, aggregation, distribution, querying, publication and of course site integration would result in Maven being elevated to the place it always set out to be, project comprehension and technical management, and really enable IT organisations to bridge the gap between the technical disciplines (code, docs, tests) and the managerial/governance disciplines (quality, progress, process). As someone who spends his time researching s/w development methods, processes and tools strategies for a 1+ billion dollar IT company I know this is what we need and I think Maven is the perfect platform for it. soapbox-eof John Allen -- View this message in context: http://www.nabble.com/Maven-central-reporting-API-tf2195661.html#a6137872 Sent from the Maven Developers forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
