[Eclemma-jacoco-dev] Final preparations for release 0.5.3

[Evgeny M. <man...@gm...>]

Hi guys,

I'd like to start release of JaCoCo 0.5.3 with publishing to Maven
repository. But before doing so documentation must be updated and this is
exactly what I'm doing now, but there is two issues and I need an advice :

   1. Current Maven build behaves like Ant build - e.g. documentation
   contains qualified versions of libraries, but this is not always correct in
   case of jacoco-maven-plugin. E.g. current deployed documentation (
   http://www.eclemma.org/jacoco/trunk/doc/maven.html ) mentions
   jacoco-maven-plugin version "0.5.3.20110621172127" , but it should mention
   "0.5.3-SNAPSHOT" in case of unreleased version and qualified version in case
   of released. Well, this can be simply solved by replacing
   "@qualified.bundle.version@" on "@project.version@" in documentation for
   jacoco-maven-plugin. But in this case Ant build wouldn't behave as Maven
   build anymore. And in this case our documentation will always contain
   reference on "SNAPSHOT" version, because we deploy documentation from
   trunk. So my suggestion is to remove substitution on jacoco-maven-plugin
   page and to have several sections - how to use snapshot version of plugin
   and how to use released version of plugin.
   2. Maven build does not contain results of performance tests in
   documentation (
http://www.eclemma.org/jacoco/trunk/test/performance.txt ). And
   here's why : I've played with this tests. And from my point of view they
   completely useless, at least in documentation. Several executions of such
   tests in same environment will give us different results, so they are not
   stable. Moreover - results completely differ if I will make several
   executions using one JVM, or using different. So from developer point of
   view they useless, because they are not stable and can't provide comparison
   with previous release (to find degradations). And from user point of view
   they useless, because as a user I would expect not a generic numbers, but a
   real comparison with other coverage engines ( e.g. something like
   http://www.sonarsource.org/pick-your-code-coverage-tool-in-sonar-2-2/ ).
   So my suggestion Is to remove results of performance tests from
   documentation, at least for the moment.

So WDYT?

-- 
Best regards,
Evgeny Mandrikov aka Godin <http://godin.net.ru>
http://twitter.com/_godin_