You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by George Stragand <ge...@gmail.com> on 2006/11/29 17:26:36 UTC
Cobertura report with Maven 2?
Hello,
I am upgrading our projects from M1 to M2 and would like to continue to
use the Cobertura plugin. With M2, the Cobertura generated pages only cover
classes which are tested. Is there an option to include all the classes to
see what hasn't been tested? Yes, a better approach would be to write all
the test cases; however that is not practical as we inherited a large amount
of code from a previous developer team which did not see the value in JUnit
(and yes, that team is gone!).
TIA
--G
Re: Cobertura report with Maven 2?
Posted by George Stragand <ge...@gmail.com>.
That did it. I had downloaded 2.1 and thought it was 2.0. Thanks.
On 11/29/06, Rémy Sanlaville <re...@gmail.com> wrote:
>
> If you want to see all classes, you have to use the 2.0 version
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>cobertura-maven-plugin</artifactId>
> <version>2.0</version>
> </plugin>
>
> With the 2.1-SNAPSHOT, I also just have the tested classes.
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>cobertura-maven-plugin</artifactId>
> <version>2.1-SNAPSHOT</version>
> </plugin>
>
> It would be nice to can see all the classes with the 2.1 version
>
> Rémy
>
> 2006/11/29, George Stragand <ge...@gmail.com>:
> >
> > Thanks, that's the same config I have. It should be a no-brainer.
> > What version are you using? I let M2 download what it wanted and ended
> up
> > with 2.0.
> > --G
> >
> > On 11/29/06, Grosskop, Kay <Ka...@ordina.nl> wrote:
> > >
> > > Hoi George,
> > >
> > > We use the cobertura plugin and it lets me navigate the sources of ALL
> > > classes and shows their coverage, also when 0%. If that is what you
> > want. So
> > > it must be a configuration issue.
> > > the configuration however is trivial, so I cannot imagine what went
> > wrong:
> > > [...]
> > > <plugin>
> > > <groupId>org.codehaus.mojo</groupId>
> > > <artifactId>cobertura-maven-plugin</artifactId>
> > > </plugin>
> > > </plugins>
> > > </reporting>
> > >
> > > Kay
> > >
> > > ________________________________
> > >
> > > Van: George Stragand [mailto:george.stragand@gmail.com]
> > > Verzonden: wo 29-11-2006 17:26
> > > Aan: users@maven.apache.org
> > > Onderwerp: Cobertura report with Maven 2?
> > >
> > >
> > >
> > > Hello,
> > > I am upgrading our projects from M1 to M2 and would like to
> continue
> > to
> > > use the Cobertura plugin. With M2, the Cobertura generated pages only
> > > cover
> > > classes which are tested. Is there an option to include all the
> classes
> > > to
> > > see what hasn't been tested? Yes, a better approach would be to write
> > all
> > > the test cases; however that is not practical as we inherited a large
> > > amount
> > > of code from a previous developer team which did not see the value in
> > > JUnit
> > > (and yes, that team is gone!).
> > > TIA
> > > --G
> > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
>
>
Re: Cobertura report with Maven 2?
Posted by Rémy Sanlaville <re...@gmail.com>.
If you want to see all classes, you have to use the 2.0 version
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.0</version>
</plugin>
With the 2.1-SNAPSHOT, I also just have the tested classes.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
It would be nice to can see all the classes with the 2.1 version
Rémy
2006/11/29, George Stragand <ge...@gmail.com>:
>
> Thanks, that's the same config I have. It should be a no-brainer.
> What version are you using? I let M2 download what it wanted and ended up
> with 2.0.
> --G
>
> On 11/29/06, Grosskop, Kay <Ka...@ordina.nl> wrote:
> >
> > Hoi George,
> >
> > We use the cobertura plugin and it lets me navigate the sources of ALL
> > classes and shows their coverage, also when 0%. If that is what you
> want. So
> > it must be a configuration issue.
> > the configuration however is trivial, so I cannot imagine what went
> wrong:
> > [...]
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>cobertura-maven-plugin</artifactId>
> > </plugin>
> > </plugins>
> > </reporting>
> >
> > Kay
> >
> > ________________________________
> >
> > Van: George Stragand [mailto:george.stragand@gmail.com]
> > Verzonden: wo 29-11-2006 17:26
> > Aan: users@maven.apache.org
> > Onderwerp: Cobertura report with Maven 2?
> >
> >
> >
> > Hello,
> > I am upgrading our projects from M1 to M2 and would like to continue
> to
> > use the Cobertura plugin. With M2, the Cobertura generated pages only
> > cover
> > classes which are tested. Is there an option to include all the classes
> > to
> > see what hasn't been tested? Yes, a better approach would be to write
> all
> > the test cases; however that is not practical as we inherited a large
> > amount
> > of code from a previous developer team which did not see the value in
> > JUnit
> > (and yes, that team is gone!).
> > TIA
> > --G
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
Re: Cobertura report with Maven 2?
Posted by George Stragand <ge...@gmail.com>.
Thanks, that's the same config I have. It should be a no-brainer.
What version are you using? I let M2 download what it wanted and ended up
with 2.0.
--G
On 11/29/06, Grosskop, Kay <Ka...@ordina.nl> wrote:
>
> Hoi George,
>
> We use the cobertura plugin and it lets me navigate the sources of ALL
> classes and shows their coverage, also when 0%. If that is what you want. So
> it must be a configuration issue.
> the configuration however is trivial, so I cannot imagine what went wrong:
> [...]
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>cobertura-maven-plugin</artifactId>
> </plugin>
> </plugins>
> </reporting>
>
> Kay
>
> ________________________________
>
> Van: George Stragand [mailto:george.stragand@gmail.com]
> Verzonden: wo 29-11-2006 17:26
> Aan: users@maven.apache.org
> Onderwerp: Cobertura report with Maven 2?
>
>
>
> Hello,
> I am upgrading our projects from M1 to M2 and would like to continue to
> use the Cobertura plugin. With M2, the Cobertura generated pages only
> cover
> classes which are tested. Is there an option to include all the classes
> to
> see what hasn't been tested? Yes, a better approach would be to write all
> the test cases; however that is not practical as we inherited a large
> amount
> of code from a previous developer team which did not see the value in
> JUnit
> (and yes, that team is gone!).
> TIA
> --G
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Cobertura report with Maven 2?
Posted by "Grosskop, Kay" <Ka...@ordina.nl>.
Hoi George,
We use the cobertura plugin and it lets me navigate the sources of ALL classes and shows their coverage, also when 0%. If that is what you want. So it must be a configuration issue.
the configuration however is trivial, so I cannot imagine what went wrong:
[...]
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
</plugin>
</plugins>
</reporting>
Kay
________________________________
Van: George Stragand [mailto:george.stragand@gmail.com]
Verzonden: wo 29-11-2006 17:26
Aan: users@maven.apache.org
Onderwerp: Cobertura report with Maven 2?
Hello,
I am upgrading our projects from M1 to M2 and would like to continue to
use the Cobertura plugin. With M2, the Cobertura generated pages only cover
classes which are tested. Is there an option to include all the classes to
see what hasn't been tested? Yes, a better approach would be to write all
the test cases; however that is not practical as we inherited a large amount
of code from a previous developer team which did not see the value in JUnit
(and yes, that team is gone!).
TIA
--G