Hello, I can only present a method to do it, but not all the code, as i'm working...
for example for the jxr plugin - add a postgoal jxr:register-report to register a new report for the cactus jxr - add a postgoal jxr:deregister-report to deregister the new report - add a postgoal jxr:do-report to create the jxr for cactus tests you can do something quite the same for the javancss plugin (i have done it for unit tests) and maybe you can do it for quite a number of reports. Rapha�l --- Laurent PETIT <[EMAIL PROTECTED]> wrote: > Hello, > > Since Unit Tests must be equally considered production code as > application code, I would be happy if I could use some verification, > metrics, javadoc plugins with the src/test java code too. > > And the results should be separated from the src/java results. > > Indeed, it would be great to have some metrics on the current health > of > the unit tests, where for example refactoring may be appropriate, > code > conventions apply, ... > > Do you know : > > - if this is a feature that is in the roadmap ? > - what the workarounds are to do it the "ugly way" for now on ? ;-) > > Thanks in advance, > > -- > Laurent Petit > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ------------------------------------ | Rapha�l Pi�roni | | 33+ 223 351 354 | | mailto:[EMAIL PROTECTED] | | http://www.dexem.com | | mailing:[EMAIL PROTECTED] | ------------------------------------ D�couvrez nos promotions exclusives "destination de la Tunisie, du Maroc, des Bal�ares et la R�p. Dominicaine sur Yahoo! Voyages : http://fr.travel.yahoo.com/promotions/mar14.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
