You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Prasad Kashyap <go...@gmail.com> on 2006/11/06 20:47:47 UTC

Re: Progress indicators for project management

Hi Benoit,

Your QALab plugin for m2 looks quite promising. Can it aggregate
surefire-reports too ?

We have a very large multi-module project with junit tests in each
module. surefire-reports are generated in each module during the site
phase. But we'd want to eventually aggregate at the top, a summary of
the surefire tests with links to the reports in the individual
modules.

Cheers
Prasad

On 9/25/06, Benoitx <be...@yahoo.com> wrote:
>
> Christophe
>
> Thanks for trying QALab, as you know from this thread, it is
> work-in-progress.
>
> You can create your exporter that would log things in JDBC if you want, see:
> http://qalab.sourceforge.net/faq.html#my-export
>
> If you write one such item, we would like to include it if it is generic.
>
> I know that the QA generation has changed dramatically between ant/maven 1
> and maven2, some seems to do away without XML, which is extremelly
> surprising and frustrating.
>
> Could you post your settings as it may help us to better understand how
> QALab is used in the community.
>
> Thanks
>
> Benoit.
>
>
> Christophe DENEUX wrote:
> >
> >
> > Hi all,
> >
> > I have quickly try maven-qalab-plugin this weekend and I have notice the
> > following remarks/issues:
> >       - Unable to run maven-qalab-plugin with Findbugs (No XML report is
> > generated by Findbugs)
> >       - I had the PMD, Checkstyle, ... configured in the <reporting> section to
> > have these report in the generated
> > website. To have the QALab reports, I must duplicate the PMD, Checkstyle,
> > ... configuration in the <buil> section
> >       - AS report by Donnchadh, the history is stored in an XML file.
> >
> > Is it not possible to have a maven-qalab-plugin as a report plugin, that:
> >         - parse existing XML files generated by Checkstyle, PMD, ... (each
> > of them declared in the <reporting>
> > section as usually used)
> >         - merge statistics in a database through JDBC
> >         - generated graphs.
> >
> > Thanks,
> > Christophe DENEUX
> >
> > ---------- Initial Header -----------
> >
> > From      : "Benoit Xhenseval" benoitx@yahoo.com
> > To          : donnchadh@computer..org,"Maven Users List"
> > users@maven.apache.org
> > Cc          :
> > Date      : Fri, 22 Sep 2006 05:44:03 -0700 (PDT)
> > Subject : Re: Progress indicators for project management
> >
> >> Hi Donnchadh,
> >>
> >> First of all, thanks for trying the QALab plugin, he hope you'll find it
> >> useful.
> >>
> >> The Maven2 plugin is really more of a beta and I am pleased that we are
> >> resuming development on it shortly,
> > your comments will be taken into account.  I have launched QALab but was
> > not involved in the Maven2 plugin.  I
> > have found Maven2 more complicated than expected when I looked at the way
> > it does reports... i.e. no XML/XSL
> > and using java to write some reports...
> >
> >>
> >> You are right in saying that you question about "inherting" a pom setting
> >> is more of a Maven2 question and I
> > shall let the specialists answer you.
> >>
> >> The idea of qalab storing the data in an xml  was to reduce the
> >> dependencies, this XML can be put in
> > different place; this is something that maven1 and ant users can do
> > easily, we will ensure that it is the case
> > for m2.
> >> One should note that it is possible to define your own "exporter" and
> >> therefore could decide to store the
> > data in say a database for instance. If there is a demand, we may even
> > provide a reference implementation for
> > that?
> >>
> >> So, in summary: hang in there, give us a few weeks or so to sort it out
> >> and we will release QALab v1.0 with
> > a fully defined maven2 plugin.
> >>
> >> Best regards
> >>
> >> Benoit
> >> ----- Original Message ----
> >> From: Donnchadh ? Donnabh?in <do...@gmail.com>
> >> To: Maven Users List <us...@maven.apache.org>
> >> Cc: qalab@objectlab.co.uk
> >> Sent: Thursday, September 21, 2006 6:12:05 PM
> >> Subject: Re: Progress indicators for project management
> >>
> >> I tried it quicly and came across a few issues (most of which are
> >> easily dealt with).
> >>
> >
> >> I took the example configuration on the maven2 QALab plugin page
> >> ( http://qalab.sourceforge.net/maven2/faq.html )
> >>  and simplified it to just working with PMD. I came across the following
> >> issues:
> >>  * By default PMD doesn't seem to produce an XML report
> >>  * When the PMD plugin is instructed to produce an XML report it puts
> >> it in target and the QALab example QALab expects it to be in
> >> target/pmd.
> >>  * By Default, the PMD plugin seems to run in the report phase and the
> >> example runs  in the verify phase
> >>
> >> I got it working in the end with the following configuration
> >>
> >>   <build>
> >>     <plugins>
> >>       <plugin>
> >>         <groupId>org.apache.maven.plugins</groupId>
> >>         <artifactId>maven-pmd-plugin</artifactId>
> >>         <executions>
> >>           <execution>
> >
> >>             <id>pmd</id>
> >>             <phase>verify</phase>
> >>             <goals>
> >>               <goal>pmd</goal>
> >>             </goals>
> >
> >>           </execution>
> >>         </executions>
> >>         <configuration>
> >>           <linkXref>true</linkXref>
> >>           <targetJdk>1.5</targetJdk>
> >>           <format>xml</format>
> >>         </configuration>
> >
> >>       </plugin>
> >>       <plugin>
> >>         <groupId>net.objectlab</groupId>
> >>         <artifactId>maven-qalab-plugin</artifactId>
> >>         <version>2.1</version>
> >>         <executions>
> >>           <execution>
> >
> >>             <id>pmd-merge</id>
> >>             <phase>verify</phase>
> >>             <goals>
> >>               <goal>merge</goal>
> >>             </goals>
> >>             <configuration>
> >>               <handler>net.objectlab.qalab.parser.PMDStatMerge</handler>
> >>               <inputFile>
> >>                 ${project.build.directory}/pmd.xml
> >>               </inputFile>
> >>             </configuration>
> >>           </execution>
> >>           <execution>
> >>             <id>qalab-movers</id>
> >>             <phase>verify</phase>
> >>             <goals>
> >>               <goal>movers</goal>
> >>             </goals>
> >>             <configuration>
> >>               <startTimeHoursOffset>480</startTimeHoursOffset>
> >>             </configuration>
> >>           </execution>
> >>             <execution>
> >>             <id>qalab-chart</id>
> >>             <phase>verify</phase>
> >>             <goals>
> >>             <goal>chart</goal>
> >>             </goals>
> >>             <configuration>
> >>             <summaryOnly>false</summaryOnly>
> >>             </configuration>
> >>             </execution>
> >>         </executions>
> >>         <configuration>
> >>           <types>pmd</types>
> >>         </configuration>
> >>       </plugin>
> >>     </plugins>
> >>   </build>
> >>   <reporting>
> >>     <plugins>
> >>       <plugin>
> >>         <groupId>net.objectlab</groupId>
> >>         <artifactId>maven-qalab-plugin</artifactId>
> >>         <version>2.1</version>
> >>         <reportSets>
> >>           <reportSet>
> >>             <reports>
> >>               <report>report</report>
> >>               <report>movers-report</report>
> >>             </reports>
> >>           </reportSet>
> >>         </reportSets>
> >
> >>       </plugin>
> >>       <plugin>
> >>         <groupId>org.apache.maven.plugins</groupId>
> >>         <artifactId>maven-pmd-plugin</artifactId>
> >
> >>         <configuration>
> >>           <linkXref>true</linkXref>
> >>           <targetJdk>1.5</targetJdk>
> >>           <format>xml</format>
> >>         </configuration>
> >>       </plugin>
> >>     </plugins>
> >>   </reporting>
> >>
> >>
> >> It seems a little verbose. I wonder if a more concise configuration is
> >> possible?
> >> Also, I would like to set it up in my root pom and inherit the
> >> confiuration in the modules, but that doesn't seem very
> >> straightforward.
> >>
> >> Is it possible to configure it in the root pom and bind it to a
> >> lifecycle phase in the child pom (this is a general maven 2 question)?
> >>
> >> A bigger issue is that the history is stored within an xml file in the
> >> project. I imagine that qalab would be run within a continuous
> >> integration context in general and the history would be lost.
> >> Is it possible to override the location of this and store it somewhere
> >> outside the project so that when the continuous integration system
> >> (luntbuild in our case) does a clean build, this history is not lost?
> >>
> >>   Donnchadh
> >>
> >>
> >> On 9/21/06, Christophe Deneux <ch...@capgemini.com> wrote:
> >> >
> >> > Thanks Doug,
> >> >
> >> > I will try QALab. It seems that no Maven2 plugin exists for XRadar.
> >> >
> >> > Christophe
> >> >
> >> > ---------- Initial Header -----------
> >> >
> >> > From      : "Doug Douglass" douglass.doug@gmail.com
> >> > To          : "Maven Users List" users@maven.apache.org
> >> > Cc          :
> >> > Date      : Thu, 21 Sep 2006 08:00:37 -0600
> >> > Subject : Re: Progress indicators for project management
> >> >
> >> > > Checkout qalab[1], there's a maven plugin around for it, though I
> >> haven't
> >> > > used it. Perhaps search the dev@maven list archives, I think there
> >> was a
> >> > > thread over there in the last few weeks regarding the maven reporting
> >> API.
> >> > > Many people are very, very interested in this type of capability.
> >> > >
> >> > > XRadar[2] was another tool name that come to mind.
> >> >
> >> > >
> >> > > Cheers,
> >> > > Doug
> >> > >
> >> > > [1] http://qalab.sourceforge.net/
> >> > >
> >> > > [2] http://xradar.sourceforge.net/
> >> > >
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > This message contains information that may be privileged or confidential
> > and is the property of the Capgemini Group. It is intended only for the
> > person to whom it is addressed. If you are not the intended recipient,
> > you are not authorized to read, print, retain, copy, disseminate,
> > distribute, or use this message or any part thereof. If you receive this
> > message in error, please notify the sender immediately and delete all
> > copies of this message.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Progress-indicators-for-project-management-tf2312119.html#a6484971
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Progress indicators for project management

Posted by Benoitx <be...@yahoo.com>.
It is a possibility but we will not do it for version 1.0 (we working on
it... the M2 plugin is nicely coming along!)

Of course, if you want to develop it, we would be gladly include it with
full credit.
You would need to create a StatMerger which could be simply extending
BaseStatMerge.

The principal objective of QALab is simply to keep track of some stats over
time, it is not an 'aggregate' tool as such...

Keep an eye on QALab... coming soon to a java build near you! :-)

Benoit



prasad wrote:
> 
> Hi Benoit,
> 
> Your QALab plugin for m2 looks quite promising. Can it aggregate
> surefire-reports too ?
> 
> We have a very large multi-module project with junit tests in each
> module. surefire-reports are generated in each module during the site
> phase. But we'd want to eventually aggregate at the top, a summary of
> the surefire tests with links to the reports in the individual
> modules.
> 
> Cheers
> Prasad
> 
> On 9/25/06, Benoitx <be...@yahoo.com> wrote:
>>
>> Christophe
>>
>> Thanks for trying QALab, as you know from this thread, it is
>> work-in-progress.
>>
>> You can create your exporter that would log things in JDBC if you want,
>> see:
>> http://qalab.sourceforge.net/faq.html#my-export
>>
>> If you write one such item, we would like to include it if it is generic.
>>
>> I know that the QA generation has changed dramatically between ant/maven
>> 1
>> and maven2, some seems to do away without XML, which is extremelly
>> surprising and frustrating.
>>
>> Could you post your settings as it may help us to better understand how
>> QALab is used in the community.
>>
>> Thanks
>>
>> Benoit.
>>
>>
>> Christophe DENEUX wrote:
>> >
>> >
>> > Hi all,
>> >
>> > I have quickly try maven-qalab-plugin this weekend and I have notice
>> the
>> > following remarks/issues:
>> >       - Unable to run maven-qalab-plugin with Findbugs (No XML report
>> is
>> > generated by Findbugs)
>> >       - I had the PMD, Checkstyle, ... configured in the <reporting>
>> section to
>> > have these report in the generated
>> > website. To have the QALab reports, I must duplicate the PMD,
>> Checkstyle,
>> > ... configuration in the <buil> section
>> >       - AS report by Donnchadh, the history is stored in an XML file.
>> >
>> > Is it not possible to have a maven-qalab-plugin as a report plugin,
>> that:
>> >         - parse existing XML files generated by Checkstyle, PMD, ...
>> (each
>> > of them declared in the <reporting>
>> > section as usually used)
>> >         - merge statistics in a database through JDBC
>> >         - generated graphs.
>> >
>> > Thanks,
>> > Christophe DENEUX
>> >
>> > ---------- Initial Header -----------
>> >
>> > From      : "Benoit Xhenseval" benoitx@yahoo.com
>> > To          : donnchadh@computer..org,"Maven Users List"
>> > users@maven.apache.org
>> > Cc          :
>> > Date      : Fri, 22 Sep 2006 05:44:03 -0700 (PDT)
>> > Subject : Re: Progress indicators for project management
>> >
>> >> Hi Donnchadh,
>> >>
>> >> First of all, thanks for trying the QALab plugin, he hope you'll find
>> it
>> >> useful.
>> >>
>> >> The Maven2 plugin is really more of a beta and I am pleased that we
>> are
>> >> resuming development on it shortly,
>> > your comments will be taken into account.  I have launched QALab but
>> was
>> > not involved in the Maven2 plugin.  I
>> > have found Maven2 more complicated than expected when I looked at the
>> way
>> > it does reports... i.e. no XML/XSL
>> > and using java to write some reports...
>> >
>> >>
>> >> You are right in saying that you question about "inherting" a pom
>> setting
>> >> is more of a Maven2 question and I
>> > shall let the specialists answer you.
>> >>
>> >> The idea of qalab storing the data in an xml  was to reduce the
>> >> dependencies, this XML can be put in
>> > different place; this is something that maven1 and ant users can do
>> > easily, we will ensure that it is the case
>> > for m2.
>> >> One should note that it is possible to define your own "exporter" and
>> >> therefore could decide to store the
>> > data in say a database for instance. If there is a demand, we may even
>> > provide a reference implementation for
>> > that?
>> >>
>> >> So, in summary: hang in there, give us a few weeks or so to sort it
>> out
>> >> and we will release QALab v1.0 with
>> > a fully defined maven2 plugin.
>> >>
>> >> Best regards
>> >>
>> >> Benoit
>> >> ----- Original Message ----
>> >> From: Donnchadh ? Donnabh?in <do...@gmail.com>
>> >> To: Maven Users List <us...@maven.apache.org>
>> >> Cc: qalab@objectlab.co.uk
>> >> Sent: Thursday, September 21, 2006 6:12:05 PM
>> >> Subject: Re: Progress indicators for project management
>> >>
>> >> I tried it quicly and came across a few issues (most of which are
>> >> easily dealt with).
>> >>
>> >
>> >> I took the example configuration on the maven2 QALab plugin page
>> >> ( http://qalab.sourceforge.net/maven2/faq.html )
>> >>  and simplified it to just working with PMD. I came across the
>> following
>> >> issues:
>> >>  * By default PMD doesn't seem to produce an XML report
>> >>  * When the PMD plugin is instructed to produce an XML report it puts
>> >> it in target and the QALab example QALab expects it to be in
>> >> target/pmd.
>> >>  * By Default, the PMD plugin seems to run in the report phase and the
>> >> example runs  in the verify phase
>> >>
>> >> I got it working in the end with the following configuration
>> >>
>> >>   <build>
>> >>     <plugins>
>> >>       <plugin>
>> >>         <groupId>org.apache.maven.plugins</groupId>
>> >>         <artifactId>maven-pmd-plugin</artifactId>
>> >>         <executions>
>> >>           <execution>
>> >
>> >>             <id>pmd</id>
>> >>             <phase>verify</phase>
>> >>             <goals>
>> >>               <goal>pmd</goal>
>> >>             </goals>
>> >
>> >>           </execution>
>> >>         </executions>
>> >>         <configuration>
>> >>           <linkXref>true</linkXref>
>> >>           <targetJdk>1.5</targetJdk>
>> >>           <format>xml</format>
>> >>         </configuration>
>> >
>> >>       </plugin>
>> >>       <plugin>
>> >>         <groupId>net.objectlab</groupId>
>> >>         <artifactId>maven-qalab-plugin</artifactId>
>> >>         <version>2.1</version>
>> >>         <executions>
>> >>           <execution>
>> >
>> >>             <id>pmd-merge</id>
>> >>             <phase>verify</phase>
>> >>             <goals>
>> >>               <goal>merge</goal>
>> >>             </goals>
>> >>             <configuration>
>> >>              
>> <handler>net.objectlab.qalab.parser.PMDStatMerge</handler>
>> >>               <inputFile>
>> >>                 ${project.build.directory}/pmd.xml
>> >>               </inputFile>
>> >>             </configuration>
>> >>           </execution>
>> >>           <execution>
>> >>             <id>qalab-movers</id>
>> >>             <phase>verify</phase>
>> >>             <goals>
>> >>               <goal>movers</goal>
>> >>             </goals>
>> >>             <configuration>
>> >>               <startTimeHoursOffset>480</startTimeHoursOffset>
>> >>             </configuration>
>> >>           </execution>
>> >>             <execution>
>> >>             <id>qalab-chart</id>
>> >>             <phase>verify</phase>
>> >>             <goals>
>> >>             <goal>chart</goal>
>> >>             </goals>
>> >>             <configuration>
>> >>             <summaryOnly>false</summaryOnly>
>> >>             </configuration>
>> >>             </execution>
>> >>         </executions>
>> >>         <configuration>
>> >>           <types>pmd</types>
>> >>         </configuration>
>> >>       </plugin>
>> >>     </plugins>
>> >>   </build>
>> >>   <reporting>
>> >>     <plugins>
>> >>       <plugin>
>> >>         <groupId>net.objectlab</groupId>
>> >>         <artifactId>maven-qalab-plugin</artifactId>
>> >>         <version>2.1</version>
>> >>         <reportSets>
>> >>           <reportSet>
>> >>             <reports>
>> >>               <report>report</report>
>> >>               <report>movers-report</report>
>> >>             </reports>
>> >>           </reportSet>
>> >>         </reportSets>
>> >
>> >>       </plugin>
>> >>       <plugin>
>> >>         <groupId>org.apache.maven.plugins</groupId>
>> >>         <artifactId>maven-pmd-plugin</artifactId>
>> >
>> >>         <configuration>
>> >>           <linkXref>true</linkXref>
>> >>           <targetJdk>1.5</targetJdk>
>> >>           <format>xml</format>
>> >>         </configuration>
>> >>       </plugin>
>> >>     </plugins>
>> >>   </reporting>
>> >>
>> >>
>> >> It seems a little verbose. I wonder if a more concise configuration is
>> >> possible?
>> >> Also, I would like to set it up in my root pom and inherit the
>> >> confiuration in the modules, but that doesn't seem very
>> >> straightforward.
>> >>
>> >> Is it possible to configure it in the root pom and bind it to a
>> >> lifecycle phase in the child pom (this is a general maven 2 question)?
>> >>
>> >> A bigger issue is that the history is stored within an xml file in the
>> >> project. I imagine that qalab would be run within a continuous
>> >> integration context in general and the history would be lost.
>> >> Is it possible to override the location of this and store it somewhere
>> >> outside the project so that when the continuous integration system
>> >> (luntbuild in our case) does a clean build, this history is not lost?
>> >>
>> >>   Donnchadh
>> >>
>> >>
>> >> On 9/21/06, Christophe Deneux <ch...@capgemini.com> wrote:
>> >> >
>> >> > Thanks Doug,
>> >> >
>> >> > I will try QALab. It seems that no Maven2 plugin exists for XRadar.
>> >> >
>> >> > Christophe
>> >> >
>> >> > ---------- Initial Header -----------
>> >> >
>> >> > From      : "Doug Douglass" douglass.doug@gmail.com
>> >> > To          : "Maven Users List" users@maven.apache.org
>> >> > Cc          :
>> >> > Date      : Thu, 21 Sep 2006 08:00:37 -0600
>> >> > Subject : Re: Progress indicators for project management
>> >> >
>> >> > > Checkout qalab[1], there's a maven plugin around for it, though I
>> >> haven't
>> >> > > used it. Perhaps search the dev@maven list archives, I think there
>> >> was a
>> >> > > thread over there in the last few weeks regarding the maven
>> reporting
>> >> API.
>> >> > > Many people are very, very interested in this type of capability.
>> >> > >
>> >> > > XRadar[2] was another tool name that come to mind.
>> >> >
>> >> > >
>> >> > > Cheers,
>> >> > > Doug
>> >> > >
>> >> > > [1] http://qalab.sourceforge.net/
>> >> > >
>> >> > > [2] http://xradar.sourceforge.net/
>> >> > >
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> > This message contains information that may be privileged or
>> confidential
>> > and is the property of the Capgemini Group. It is intended only for the
>> > person to whom it is addressed. If you are not the intended recipient,
>> > you are not authorized to read, print, retain, copy, disseminate,
>> > distribute, or use this message or any part thereof. If you receive
>> this
>> > message in error, please notify the sender immediately and delete all
>> > copies of this message.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Progress-indicators-for-project-management-tf2312119.html#a6484971
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Progress-indicators-for-project-management-tf2312119s177.html#a7205858
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org