Hi,
If you've had Clover license issues recently while attempting to build/
release Magnolia, a module or project, fear not, this will be resolved
soon, with parent poms v9. As soon as those are released, or if you
feel like using the 9-SNAPSHOT version, you'll have two options:
1) live with the evaluation license that's bundled in the Clover Maven
plugin itself - this should work for a little while now, as I've just
updated the pom to use the latest version of Clover.
2) use your own license: the parent pom configures the plugin so that
it uses a cloverLicenseLocation property. You can, for instance,
define it in your ~/.m2/settings.xml file, using a profile, such as :
<profiles>
<profile>
<id>my-default-profile</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<cloverLicenseLocation>${user.home}/.m2/clover.license</
cloverLicenseLocation>
</properties>
[...]
Provided that your license key is indeed in ~/.m2/clover.license
If the property isn't defined/found, the plugin will fall back to the
evaluation license. On the other hand, you'll get an explicit error
message if you define the property but make it point to an non-
existent or invalid file.
I just deployed a fresh snapshot of all parent poms 9-SNAPSHOT, so,
enjoy, and raise the coverage !
Cheers,
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
