Oliver Heger wrote:
Just one question: I noticed that the links to the Cobertura report open
an empty site for some components (did not check all). Is there a
problem? (I am asking because I had some trouble when playing with the
maven 2 cobertura plug-in a while ago.)
There are 2 things that can cause this:
1. It's a multi module build. Cobertura does not support aggregated
reports yet, so components like jci will not get any report on the top
level.
2. The tests for some sandbox components will not run in Surefire out of
the box, so I have disabled the tests in some of them. This leads to no
tests for Cobertura to check. The problems are usually class loader related.
But, this has nothing to do with the skin itself. This has to do with
the build and the reports, which I will start a another discussion about.
Otherwise I am +1 for both.
Oliver
Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because...
2. Release commons-skin 1.0 based on revision 495809. I have not created
an RC for it, since it is in the sandbox. If that is needed, I'll do it
once the move to commons proper has been completed.
Examples of how it looks can be found at the address below, where the
entire sandbox has been staged. Note that the staged sites have been
built with Maven components that were built from SVN and have not yet
been released.
http://people.apache.org/~dennisl/commons-sandbox/
[ ] +1 Do it
[ ] -1 No not yet, because...
The votes will be open for at least 72 hours.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
