Well since my modified patch has been committed, I've started work on the Hudson plugin to report the results...
https://hudson.dev.java.net/svn/hudson/trunk/hudson/plugins/mipi I will report back when I have it finished. I am assuming that either people can wait for a Maven reporting mojo, or others would be quicker at writing one than if we swapped and they wrote the hudson plugin while I wrote the reporting mojo. If I have finished the hudson plugin and there is still no reporting mojo, I'll see about writing one -Stephen 2009/1/23 Stephen Connolly <[email protected]>: > > > 2009/1/8 Benjamin Bentmann <[email protected]> >> >> Stephen Connolly wrote: >> >>> Another issue for me is how we handle the integration tests and >>> integration >>> test reporting. >> >> Not sure what exactly you mean with "reporting" here. It wasn't intended >> to produce sites. > > Here you go: > > http://jira.codehaus.org/browse/MINVOKER-76 > > There is a patch attached, and if you get this into invoker for me I'll do > the reporting plugin for Hudson > > ;-) > > I might even write a maven-invoker-reports-plugin to generate a mvn > site:site report > > -Stephen. > >>> >>> AFAIK, the Maven Invoker Plugin, which is what a lot of the mojo plugins >>> use >> >> We have also the Shitty Maven Plugin in use but it shouldn't matter what >> plugin devs choose to orchestrate their ITs. As long as the ITs can be run >> during the ordinary Maven build we're in good position. >> >>> for ITs will either fail the build or not fail the build, and we >>> currently >>> do not have (AFAIK) a means of reporting the results of the Invoker >>> plugin.... hmmm sounds like I'll need to write one! >> >> Sure, there's always place for improvements. >> >> While we are at this reporting topic, another question is if and how to >> notify devs via emails. We could have Hudson send those notifications to >> dev@ or maybe some despot is willing to create a new mailing list. The >> latter option would be my personal favorite because I would rather avoid to >> have d...@mojo end up like d...@commons. >> >> >> Benjamin >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
