<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maven on Wojciech Programming Blog</title>
    <link>https://www.wlangiewicz.com/tags/maven/</link>
    <description>Recent content in Maven on Wojciech Programming Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Oct 2014 11:47:00 +0000</lastBuildDate>
    <atom:link href="https://www.wlangiewicz.com/tags/maven/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Add code coverage metrics to your maven project</title>
      <link>https://www.wlangiewicz.com/2014/10/06/add-code-coverage-metrics-to-your-maven-project/</link>
      <pubDate>Mon, 06 Oct 2014 11:47:00 +0000</pubDate>
      <guid>https://www.wlangiewicz.com/2014/10/06/add-code-coverage-metrics-to-your-maven-project/</guid>
      <description>While working on the bitcoinj project I have added support for code coverage collection and tracking. This post summarizes steps you have to take to add that for your own maven projects.&#xA;Figure out what type of code coverage you want For the bitcoinj library it is important to have a “unit test coverage” - it works by verifying which parts of the source code are reached during unit testing phase during build process.</description>
    </item>
  </channel>
</rss>
