-
We have this on the task list. See [Filtering Options][1] and [Task #22][2].
[1]: https://sourceforge.net/apps/trac/eclemma/wiki/FilteringOptions
[2]: https://sourceforge.net/apps/trac/eclemma/ticket/22.
2010-01-04 21:55:46 UTC in EclEmma - Java Code Coverage for Eclipse
-
mtnminds made 1 file-release changes.
2010-01-01 20:40:02 UTC in EclEmma - Java Code Coverage for Eclipse
-
mtnminds committed revision 821 to the EclEmma - Java Code Coverage for Eclipse SVN repository, changing 1 files.
2009-12-21 20:21:06 UTC in EclEmma - Java Code Coverage for Eclipse
-
The reason might be Bug [1641403 (Logger breaks EMMA)][1]. The EMMA Eclipse plug-in EclEmma runs a patched version of EMMA for exactly this reason.
-marc
[1]: https://sourceforge.net/tracker/?func=detail&aid=1641403&group_id=108932&atid=651897.
2009-12-20 05:36:56 UTC in EMMA code coverage
-
mtnminds committed revision 818 to the EclEmma - Java Code Coverage for Eclipse SVN repository, changing 1 files.
2009-12-16 08:16:13 UTC in EclEmma - Java Code Coverage for Eclipse
-
If a method is overwritten in a subclass and the method is only called on instances of that subclass the method in the base class is obviously never executed. EclEmma simply reflects that fact.
If the base class is always overwritten in your code base, you might consider making the class and method abstract, then the red color will go away (no code to execute).
Keep on testing,
-marc.
2009-12-01 06:10:22 UTC in EclEmma - Java Code Coverage for Eclipse
-
You're observation is correct, the bundle list does not accept wildcards.
Alternatively you might look at our new project [JaCoCo][1] which is a replacement for EMMA and works directly with any Java application (including OSGi apps). It allows to include/exclude classes via wildcard expressions. The runtime overhead in terms of CPU usage and memory is minimal, coverage files are more compact...
2009-11-24 07:59:52 UTC in EclEmma - Java Code Coverage for Eclipse
-
Hi,
It looks like the system can't determine the parent directory of your output location. The line that causes the NPE:
new File(file.getParent()).mkdirs();
Have you tried to specify an absolute path, that actually exists?
-marc.
2009-11-24 07:27:22 UTC in EclEmma - Java Code Coverage for Eclipse
-
PROBLEM
EclEmma needs to add additional class path entries for instrumented versions of the class files. This may result in very long class paths that exceed the maximum process command length of 8191 characters.
PROPOSED SOLUTION
Christoph Bimminger has proposed to specify the class path in the Class-Path header of the Manifest of the generated config JAR...
2009-11-20 09:33:46 UTC in EclEmma - Java Code Coverage for Eclipse
-
I really like the idea of adding the extra class path entries into the manifest of a config JAR (which is already created today). Here is how EclEmma works. Lets assume the class path of an application is
A;B;C
If classes in A and C should get analyzed, EclEmma modifies the class path as follows:
emma.jar;config.jar;A';A;B;C';C
Where emma.jar is the EMMA runtime, config.jar...
2009-11-20 08:54:03 UTC in EclEmma - Java Code Coverage for Eclipse
