On Sat, 03 Dec 2011 08:53:14 -0200, derkoe
wrote:
Is this some build glitch with the switch to Gradle? Or is this the
problem with meta-programming and measuring coverage?
I'd guess it's caused by the switch.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hiberna
Just found out that Tapestry's metrics are published via Sonar at Apache:
https://analysis.apache.org/dashboard/index/48022
But I guess there's something wrong - since Tapestry has a coverage of 25.7%
there!? And it used to have coverage > 90%. I guess that's because the
integration tests with bro
I guess this should be re-enabled in the Gradle build - this shows one
of Tapestry's qualities. When I show Tapestry I always mention the 92%
coverage.
Chris
Am 23.11.2011 19:29, schrieb Howard Lewis Ship:
> Actually, the cobertura link was part of the Maven build, something we
> lost in the swit
Actually, the cobertura link was part of the Maven build, something we
lost in the switch to Gradle. We can update the link to point to 5.2,
where the report was still active.
On Mon, Nov 21, 2011 at 11:42 AM, derkoe
wrote:
> Link "See Tapestry's code coverage report" on Tapestry home page leads
