[jira] Updated: (MPCLOVER-15) maven.clover.jar property not working - doesn't work with registered versions > 1.2.3

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Carlos Sanchez (mailto:apache@carlos.cousas.net)
       Date: Wed, 9 Jun 2004 12:03 PM
    Comment:
This patch is a trimmed version of the previous one and avoids
"Compiler Adapter 'org.apache.tools.ant.taskdefs.CloverCompilerAdapter' can't be found."

    Changes:
             Attachment changed to patch.diff
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPCLOVER-15?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-15

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPCLOVER-15
    Summary: maven.clover.jar property not working - doesn't work with registered versions > 1.2.3
       Type: Bug

     Status: Unassigned
   Priority: Critical

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-clover-plugin
   Versions:
             1.4
             1.5

   Assignee: 
   Reporter: fabrizio giustina

    Created: Sat, 20 Mar 2004 6:21 AM
    Updated: Wed, 9 Jun 2004 12:03 PM
Environment: maven rc1, both on windows and linux

Description:
The maven.clover.jar property which should override the standard dependency used by the clover plugin doesn't work for me.

The plugin adds the maven.clover.jar to the and classpath but the ant task is always registered using the standard dependency in project.xml (check plugin.jelly, the new jar is added to the claspath only after the task registration).
Also, the dependency in plugin's project.xml is added to the root classloader: the only way I found to make the clover plugin work properly is to add a clover dependency to my project.xml with the root classloader property (shouldn't it be avoided?) and use the jar override in project.properties.

This is a major problem when your registered clover jar version is not the same as the one used by the plugin (1.2.3). Note you can only download the latest version of clover when you apply for a license, there is no way to get a registered 1.2.3 version now.

In this situation clover starts (using the default dependency) to instruments all classes and then uses maven.clover.jar to run the tests! It crashes with a bunch of method not found errors for the differences in the 2 clover versions.

The plugin should only use 1 clover jar at a time, and the standard, unregistered one, should not be added to the root classloader.
Is there any way to remove the dependency from project.xml and add it dinamically only if maven.clover.jar is not defined?




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org