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.
If you wish to use the remote repository it is still possible (I could a FAQ for this) by doing the following: - add the license as a dependency in your project.xml - use maven.clover.license.path = ${pom.getDependencyPath('clover:yourlicensename')
Thanx, it worked.
However, there's the disadvantage that I have to repeat this (global configuration, at least for us) for every project. OTOH it's not a big problem since I'm about to create templates for new projects.
>>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.
Yeah but then who performs the download of the license? ATM this done by the Maven dependency manager. If we do this (and this may be possible but I'm not sure it's worth it) we'll need to hook in the Maven API (like using HttpUtils but I'm not sure it's a public API).
If it was possible and not too much work it would be nice. It's certainly not necessary for survival ;-)
Regards, Gisbert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
