You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2007/04/05 08:10:21 UTC
[jira] Updated: (MCLOVER-21) License discovery is broken
[ http://jira.codehaus.org/browse/MCLOVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Massol updated MCLOVER-21:
----------------------------------
Fix Version/s: (was: 2.1)
> License discovery is broken
> ---------------------------
>
> Key: MCLOVER-21
> URL: http://jira.codehaus.org/browse/MCLOVER-21
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Matthew Beermann
> Assigned To: Vincent Massol
> Priority: Critical
>
> Even when a valid, unexpired "clover.license" is located alongside the clover jar, it does not appear to be located and used as Cenqua's documentation says it should. In the example below, the directory contains a "clover.license" that is known to work properly with the Clover plugin in Maven 1.
> Yes, there is a <licenseFile/> configuration parameter that can work around this, but that doesn't address the underlying problem (and furthermore the fix isn't particularly portable).
> [INFO] [clover:instrument]
> Clover Version 1.3.11, built on November 02 2005
> loaded from: C:\maven\local_repository\clover\clover\1.3.11\clover-1.3.11.jar
> [INFO] ----------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] This license has now expired.
> [INFO] ----------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira