<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/eclemma/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/eclemma/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/eclemma/feature-requests/</id><updated>2013-05-27T08:45:19.938000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#86 Merge task fails if one input file is corrupted</title><link href="https://sourceforge.net/p/eclemma/feature-requests/86/?limit=25#21bb" rel="alternate"/><published>2013-05-27T08:45:19.938000Z</published><updated>2013-05-27T08:45:19.938000Z</updated><author><name>Marc R. Hoffmann</name><uri>https://sourceforge.net/u/mtnminds/</uri></author><id>https://sourceforge.net8dc5302197343d3fc95e3be5ed1e38f4deb264f4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed-fixed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; Eclipse3.3&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#87 Hit Counter</title><link href="https://sourceforge.net/p/eclemma/feature-requests/87/?limit=25#388c" rel="alternate"/><published>2013-05-27T08:44:08.728000Z</published><updated>2013-05-27T08:44:08.728000Z</updated><author><name>Marc R. Hoffmann</name><uri>https://sourceforge.net/u/mtnminds/</uri></author><id>https://sourceforge.net7cf254ff90d439813087b576db9c3b9575d05856</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: pending --&amp;gt; closed-wont-fix&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>Cover a single test from JUnit view</title><link href="https://sourceforge.net/p/eclemma/feature-requests/88/" rel="alternate"/><published>2012-08-09T22:32:17Z</published><updated>2012-08-09T22:32:17Z</updated><author><name>Ryan Gustafson</name><uri>https://sourceforge.net/u/rgustav/</uri></author><id>https://sourceforge.netf3a56593287f8f677b9db210a472d9cc1ff7f0ac</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When I'm writing a single @Test method, I'll often run the entire TestClass, and right click a test in the JUnit view, and run just that one test, and rerun until it works as desired.  Even if I ran the TestClass originally using coverage, the single test run does not get covered.  It would be great if I could run coverage for just that test (preferably sticky based upon original TestClass run).&lt;/p&gt;
&lt;p&gt;This would offer great insight into what precisely that one test is hitting.  Is the test doing what I think it is doing?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Hit Counter</title><link href="https://sourceforge.net/p/eclemma/feature-requests/87/" rel="alternate"/><published>2012-07-30T13:57:56Z</published><updated>2012-07-30T13:57:56Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net635f868ca19f7be74c15aab5b9caaebbbd969d35</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I would love to see the number of hits per line executed. For example a statement in a for loop is executed 10 times but an unreachable statement is executed 0 times. It is displayed on the side parallel to the line numbers.&lt;/p&gt;
&lt;p&gt;This can be found in commercial alternatives such as Clover and in other open source code coverage tools such as Gcov. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Hit Counter</title><link href="https://sourceforge.net/p/eclemma/feature-requests/87/" rel="alternate"/><published>2012-07-30T13:57:56Z</published><updated>2012-07-30T13:57:56Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net3326ca35d49c4f74d6c19e1efb9a7415963ea6a8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 87 has been modified: Hit Counter&lt;br /&gt;
Edited By: Marc R. Hoffmann (mtnminds)&lt;br /&gt;
Status updated: u'pending' =&amp;gt; u'closed-wont-fix'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Merge task fails if one input file is corrupted</title><link href="https://sourceforge.net/p/eclemma/feature-requests/86/" rel="alternate"/><published>2012-07-09T14:17:18Z</published><updated>2012-07-09T14:17:18Z</updated><author><name>Ivan</name><uri>https://sourceforge.net/u/ebaan/</uri></author><id>https://sourceforge.nete6259ab081c164ae88dff43947aa9f26bdc59e46</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have a lot of coverage result files that come from many different sources (Junit, testNG, other)&lt;br /&gt;
So when I want to generate a report, a merge all the files into one with this ant call:&lt;/p&gt;
&lt;p&gt;&amp;lt;merge destfile="${env.WORKSPACE}/coverage.es"&amp;gt;&lt;br /&gt;
&amp;lt;fileset dir="${env.WORKSPACE}" includes="**/*.ec" /&amp;gt;&lt;br /&gt;
&amp;lt;/merge&amp;gt;&lt;/p&gt;
&lt;p&gt;But some files can be corrupted (the test crashed or even isn't finished yet.&lt;br /&gt;
And then the whole task fails:&lt;br /&gt;
15:07:25  /tmp/jenkins_slave/workspace/DAILY_TESTS_ENDER/BuildUtil/advanced-tasks.xml:168: Unable to read /tmp/jenkins_slave/workspace/DAILY_TESTS_ENDER/jacoco.1340966180.ec&lt;/p&gt;
&lt;p&gt;I would like to be able to say to the "merge" task that it should ignore corrupted/illegal/abnormal files instead of stopping. &lt;br /&gt;
IE:&lt;br /&gt;
Log a warning in MergeTask#loadSourceFiles() at line 116 instead of raising an exception.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Merge task fails if one input file is corrupted</title><link href="https://sourceforge.net/p/eclemma/feature-requests/86/" rel="alternate"/><published>2012-07-09T14:17:18Z</published><updated>2012-07-09T14:17:18Z</updated><author><name>Ivan</name><uri>https://sourceforge.net/u/ebaan/</uri></author><id>https://sourceforge.netcc8e3d41f43692079f3416570acfc55c82894391</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 86 has been modified: Merge task fails if one input file is corrupted&lt;br /&gt;
Edited By: Marc R. Hoffmann (mtnminds)&lt;br /&gt;
Status updated: u'open' =&amp;gt; u'closed-fixed'&lt;br /&gt;
_milestone updated: '' =&amp;gt; u'Eclipse3.3'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>JaCoCO Maven: exec file parameter naming</title><link href="https://sourceforge.net/p/eclemma/feature-requests/85/" rel="alternate"/><published>2012-07-02T18:51:53Z</published><updated>2012-07-02T18:51:53Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netd316c79a7e22e6ef659ba8e7e5504b86b8ebf59f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have observed that the report goal and the prepare-agent goal have different names for the destFile. &lt;br /&gt;
The prepare-agent uses the name destFile whereas the report goal uses dataFile. It would be nice to use the same name which would make life easier.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Made possible to aggregate Report</title><link href="https://sourceforge.net/p/eclemma/feature-requests/84/" rel="alternate"/><published>2012-06-20T12:32:18Z</published><updated>2012-06-20T12:32:18Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net82520d32a886df93d0aabeb750a3e4b585d026ea</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sometimes when using maven I wanna see the coverage result for the whole project and not just for single modules.&lt;/p&gt;
&lt;p&gt;The attached patch introduces a new configuration aggregate.  When true, maven will collect jacoco.exec from each module and combine then all in order to create A report for the entire project.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>get Maven plugin report task configurable with command-line</title><link href="https://sourceforge.net/p/eclemma/feature-requests/83/" rel="alternate"/><published>2012-06-14T15:40:43Z</published><updated>2012-06-14T15:40:43Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net3f6e3ff124f739006367ef63c471b1fd0491ac60</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In order to be able to be able to generate reports in a non-intrusive way in build process, it would be useful to provide ability to invoke and configure the "report" task from command-line.&lt;br /&gt;
It's basically about adding "expressions" annotations to the Mojo.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>