Hello,
I first want to thank you for your excellent work; I've just installed the recently announced new version 1.7 of the Maven-Clover-Plugin and it works great.
However, I've got one question:
Until know, our Clover license (yes, we've bought one) was lying beside the clover.jar in the local Maven repo on the build machine. Today someone deleted this directory for debugging purposes (since it contains only copies from the lokal http repo anyway) and our builds failed immediately because Clover didn't find it's license anymore.
To avoid such accidents for the future I've put the licencse into our local Maven http repo in a folder named "licences" within the clover folder. I thought, it then should be downloaded and used together with the jar out of the accompanying "jars" directory. For me that behaviour would have been very intuitive.
As you know, it didn't. When I then read the documentation I found out about the maven.clover.license.path parameter or the classpath (I use the param now) but still wonder why my tacit understanding to put the licence in a license folder of the local Maven http repo shall not work.
Another (small) point: I've noticed that - even when I've set the maven.clover.license.path parameter and the respective license is used by Clover - still the clover-license-20060130.license file from ibiblio is downloaded. It's only 5k - but completely unnecessary.
I think it should not be a dependency in the project.xml of the maven-clover plugin but rather the default entry for maven.clover.license.path in the plugin.properties. Probably the license had to be distributed with the plugin then what I'd consider an advantage.
Thanks for your patience. Gisbert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
