New report generation changes to the project files

I've posted two changes that turn on a number of report
options that 
appear when you run "mvn site"

Running "mvn site" will generate a local copy of
the project web site 
and include quite a few reports.

To see what they look like you can visit the online version
that the 
build system generates daily:

     http://cos
mo.osafoundation.org/docs/cosmo/

If you want to run the new code coverage reports you will
need to 
initialize the clover plugin:

     mvn clover:instrument

this creates a local clover database (which is in the source
tree so 
will be removed if you do a mvn clean).

To run the coverage check:

     mvn clover:check

See http://maven.apache.org/plugins/maven-clover-plugi
n/usage.html for 
more information

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bearosafoundation.org
http://www.osafoundation
.org

bearcode-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822
40B3 CD29


_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Mike Taylor wrote:
> If you want to run the new code coverage reports you
will need to 
> initialize the clover plugin:
> 
>     mvn clover:instrument

I've filed bug 10217 reporting that the build is broken for
me 
currently, throwing a Clover error.

The issue has been filed as P1 blocker.

-- Jared

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

After an IRC debug of the issue it was resolved in two
ways.

First I saw that jared's build was invoking
"package" and "install".  
In the case he was running the command for, the
"install" step is 
redundant  *and* also was  the step where clover was being
invoked - so 
removing it fixed the immediate issue.

I also moved in the pom.xml the clover plugin definition to
be in the 
non-release profile so it will not be invoked during
release-mode 
builds.

On Jul 27, 2007, at 4:04 PM, Jared Rhine wrote:

> Mike Taylor wrote:
>> If you want to run the new code coverage reports
you will need to 
>> initialize the clover plugin:
>>     mvn clover:instrument
>
> I've filed bug 10217 reporting that the build is broken
for me 
> currently, throwing a Clover error.
>
> The issue has been filed as P1 blocker.
>
> -- Jared
>
>
---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bearosafoundation.org
http://www.osafoundation
.org

bearcode-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822
40B3 CD29



_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev