Recent changes to patches

#10 Add a setting for the character encoding of source files

2019-05-19T04:56:52.926000Z

I have merge this patch on:
https://github.com/jiangxincode/Emma/commit/4a7040b2768a56901d41413687f820758b6464f4
So I think this issues should be closed.

Add a setting for the character encoding of source files

2013-03-03T14:31:27Z

This patch adds a feature that set the character encoding of source files. Currently, character encodings of source files and the platform have to be matched.

This patch adds two ways to set the character encoding of source files.
1) "report.source.encoding" property as EMMA report generation property.
2) "sourceencoding" attribute of html element for Ant.
If the character encoding of source files is not set, the default encoding of the platform ("file.encoding" property) is set. If "file.encoding" property is also not defined, UTF-8 is set.

Currently, the character encoding of source files and the platform have to be matched. Because the current HTML report generator uses "file.encoding" property of JRE while reading source files.

enable specifying emma port number

2009-04-07T19:25:54Z

Our product consists of 4 different servers. The idea is that you can spread the load across different machines. The servers communicate with one another through JMS. As a developer I run all the servers on my development box. I instrument and merge into a single directory. If I instrument the code for only one of the servers I can run our 'integration tests' with the emma instrumentation directory at the front of the classpath and I can determine the code coverage. It breaks down when I instrument the code for multiple servers and try to run them concurrently. I see this in the log for the 2nd server I try to start:

EMMA: collecting runtime coverage data ...
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at com.vladium.emma.rt.RTController.start(RTController.java:99)
at com.vladium.emma.rt.RT.reset(RT.java:222)
at com.vladium.emma.rt.RT.<clinit>(RT.java:540)
at com.ali.statusserver.StatusServerBootstrap.$VRi(StatusServerBootstrap.java)
at com.ali.statusserver.StatusServerBootstrap.<clinit>(StatusServerBootstrap.java)
java.lang.Error: EMMA: runtime controller could not be started, aborting
at com.vladium.emma.rt.RT.reset(RT.java:233)
at com.vladium.emma.rt.RT.<clinit>(RT.java:540)
at com.ali.statusserver.StatusServerBootstrap.$VRi(StatusServerBootstrap.java)
at com.ali.statusserver.StatusServerBootstrap.<clinit>(StatusServerBootstrap.java)

I believe if I could specify the port number for emma for each server I could run the servers concurrently under emma. Unless I missed something in the documentation there is no property that can be used to specify the port.

This request seems similar to: 1280012 - but in that case it looks like the expectation is that servers will be running on different hosts

Add ability to get metadata using CtlProcessor

2008-09-17T16:29:07Z

This enables the user to get metadata information without having to do offline instrumentation.

The patch adds a new CtlProcessor RPC command, metadata.get, which contacts the remote EMMA and generates a coverage.em file.

This is done using the following command:

java -cp emma.jar emma ctl -connect $HOST:$PORT -command metadata.get

This is followed by the existing command:

java -cp emma.jar emma ctl -connect $HOST:$PORT -command coverage.get

and the reporting command that takes both metadata and coverage information as input:

java -cp emma.jar emma report -r html -in coverage.em,coverage.ec -Dreport.out.file=coverage.html --sp [source paths]

(metadata + coverage = session data -> report)

allow filtering during report generation

2007-03-12T15:17:20Z

This patch address RFE 1059959 - allow filtering during report generation.
http://sourceforge.net/tracker/index.php?func=detail&aid=1059959&group_id=108932&atid=651900

The diff was generated against the trunk.

With this patch, both <instr> and <report> can contain <filter> sub-elements.

Both task implementations now use FilterCfg, so I moved the class from com.vladium.emma.instr to com.vladium.emma.ant. However, I wasn't able to 'cvs add' it in the new location and so the last part of the diff contains the file in its entirety.

To apply the diff please truncate the attachment at "-------- FilterCfg.java moved from com.vladium.emma.instr --------------" and then apply the diff. Then you would need to put the new FilterCfg.java in the right place - com.vladium.emma.ant - and commit it.

hth,
Arvind

Maven 2 plugin contenders

2006-05-03T22:50:17Z

Here is an initial plugin submitted by Roger (user butenuth).

Using Emma Eclipse Plugin with J2EE

2006-02-20T20:42:16Z

Ok, here we go,

Remember my problem when enabling the plugin (and
losing the instrumented classes)?
That problem remains...
So I did a few modifications at the plugin code,
adding/changing actions.

Requirements:
- emma-2.1.5320

ResetDataAction:
- Remove coverage.ec
- Remove internal xml and html report
- Instrument the classes (not using
BuildRunner.startBuild())

CleanExistingCoverageData (new):
- Run ctl coverage.reset

BuildReportAction
- Automatically dump the coverage data by ctl

J2EE test:

Configuration to Work:
- Project with emma-2.1.5320 in the classpath
- Project with emma.properties in the classpath (this
file can't be in Jboss deploy folder.
It will be just in classpath project).
emma.properties must contain the "rt.control = false"
property.
- The project classes must be in an exploded jar into
deploy folder.

Classpath example:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="implementacao/src/java"/>
<classpathentry output="target/exp-eclipse-only"
kind="src" path="target/exp-eclipse-only"/> 
<classpathentry kind="var"
path="MAVEN_REPO/emma/jars/emma-2.1.5320.jar"/>
<classpathentry kind="output"
path="systemparameters-geral-cactus.ear/systemparameters-geral-ejb-2.0.0.jar"/>
</classpath>

Steps to test:
- Enable Emma Plugin
- Use ResetDataAction
- Run JBOSS
- Run Tests
- BuildReportAction
- ShowCoverage
- CleanExistingCoverageData
- BuildReportAction
- Show Coverage

The test worked fine, and I got the expected coverage.
So I just needed to use ResetDataAction,
BuildReportAction, CleanExistingCoverageData and
ShowReportAction
to do anything that I want with the plugin.

- Summarizing -

So what is the ideia?
Make a simple plugin!

What we need to do to make the plugin works in
different enviroment?
Turn it very configurable.

Interesting Options to add in Emma's Project property
(checkbox):
- Add jar to the classpath
- Get the coverage by dump

Interesting feature to add to the Plugin:
- Use ctl (to dump, reset...)

Interesting Modifications:
- A better way to instrument the code

----------------------------------------------

--Saraiva

Eclipse plugin classpath addition

2006-01-25T05:56:09Z

This patch will add the absolute path of the emma.jar
to a project's classpath without having to copy the jar
into the project.

Using the absolute path is safe unless the user changes
the location of their eclipse install (although that in
itself would cause a mass of other problems).

Add control flow information to metadata

2005-12-28T11:02:35Z

This patch enable control flow information to be
collected during instrumentation stage. This
information is available from metadata. The following
public members added to metadata classes and interfaces:

int IMetadataConstants.METHOD_NO_CONTROL_FLOW_TBL;

int IMetadataConstants.METHOD_NO_CONTROL_FLOW_DATA;

boolean IMetaData.hasControlFlowData ();

boolean ClassDescriptor.hasControlFlowData ();

boolean MethodDescriptor.hasControlFlowData ();

int [][] MethodDescriptor.getControlFlow ();

Control flow is int [][] array. For each basic block
it holds an array of basic block ids, that can be
executed just after this basic block.

bind rt port to a specific IP

2005-09-01T19:00:44Z

This patch adds the following property:
rt.control.bind=hostname.example.com

If set, the listening port for RT will be bound to that
hostname. It's handy if you're running multiple
servers, each listening on different IPs, and you need
coverage turned on for all of them (like I do!)