The following comment has been added to this issue:
Author: Guillaume Nodet
Created: Tue, 28 Sep 2004 1:33 PM
Body:
Indeed it is the same problem, but this is not a bug in jcoverage because jcoverage
offers two alternatives:
* give all class names to be instrumented on the command line
* give a list of directories in which all classes will be
instrumented.
Maybe it is possible to use a list of class files exclusion in addition to the list of
directories to handle source modifications, but i'm not sure. For my purpose, i wrote
a plugin that gives jcoverage the list of directories to instrument.
I also wrote a report that works in conjunction with the one generated by the current
plugin but which is an xml that is put in the generated-xmldocs directory and which
integrates better in the look-and-feel of maven.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJCOVERAGE-13?page=comments#action_24710
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJCOVERAGE-13
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJCOVERAGE-13
Summary: When instrumenting a project with a thousand files, the instrumentation
fails
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jcoverage-plugin
Versions:
1.0.7
Assignee: Emmanuel Venisse
Reporter: Guillaume Nodet
Created: Wed, 21 Jul 2004 6:52 AM
Updated: Tue, 28 Sep 2004 1:33 PM
Description:
When instrumenting a project with a thousands files, the instrumentation fails because
it tries to give jcoverage the whole list of files. So the command line length exceeds
the limit...
I have a patch which consists in redefining an ant task that gives to jcoverage the
directory names instead of files.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
