|
From: Jeff J. <jef...@up...> - 2006-06-02 17:37:41
|
Great info Lukas, thanks. I will change the plugin and add a doc note.
Quoting Lukas Theussl <lth...@ap...>:
>
> +1
>
> However, not having used cobertura for a long time, I had forgotten tha=
t
> you need to set maven.compile.debug=3Don when running the plugin,
> otherwise you don't get any coverage data. I had maven.compile.debug=3D=
off
> in one of my properties files and it took me a while to figure out what
> was wrong.
>
> AFAICS, this is nowhere mentioned in the docs on the web page. However,
> instead of letting the user figure this out himself, I'd suggest we
> force debug=3Don when executing the plugin, since otherwise, the report=
is
> completely useless anyway. Just put something like this in the
> cobertura:report goal when calling cobertura:on:
>
> <!-- Make sure maven.compile.debug =3D on -->
> <j:set var=3D"compileDebugOld" value=3D"${maven.compile.debug}"/>
> <j:set var=3D"maven.compile.debug" scope=3D"parent" value=3D"on"/>
> <attainGoal name=3D"cobertura:on"/>
> <j:set var=3D"maven.compile.debug" scope=3D"parent"
> value=3D"${compileDebugOld}"/>
>
>
> Actually, I just noticed that also findbugs needs debug=3Don for gettin=
g
> the line number information. You should do the same as above when
> calling java:compile in maven-findbugs-plugin:report.
>
>
> Cheers,
> -Lukas
>
>
> Jeff Jensen wrote:
> > Please vote to release Cobertura plugin from snapshot. I will do so =
on
> Sunday
> > if no objections.
> >
> >
> >
> > _______________________________________________
> > Maven-plugins-developer mailing list
> > Mav...@li...
> > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer
> >
>
|