<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:cc="http://web.resource.org/cc/"
xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://weblogs.java.net/blog/fabianocruz/">
<title>Fabiano Cruz&apos;s Blog</title>
<link>http://weblogs.java.net/blog/fabianocruz/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator></dc:creator>
<dc:date>2006-10-04T16:42:15-08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.01D" />


<items>
<rdf:Seq><rdf:li rdf:resource="http://weblogs.java.net/blog/fabianocruz/archive/2006/10/java_static_ana_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/fabianocruz/archive/2006/06/junit_4_you_1.html" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://weblogs.java.net/blog/fabianocruz/archive/2006/10/java_static_ana_1.html">
<title>Java Static Analysis made easy with Apache Maven 2</title>
<link>http://weblogs.java.net/blog/fabianocruz/archive/2006/10/java_static_ana_1.html</link>
<description>Many of today&apos;s software development projects are changing the ordinary code/compile/test/debug cycle to accommodate some other concerns, like: keeping track of what is being developed and consequently if the project is achieving its stated quality and goals. Therefore, no matter what process you use, but at some point of the project timeline, the source code [one of your most valuable assets] needs to be reviewed.</description>
<dc:subject>Open Source</dc:subject>
<dc:creator>fabianocruz</dc:creator>
<dc:date>2006-10-04T16:42:15-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/fabianocruz/archive/2006/06/junit_4_you_1.html">
<title>JUnit 4 you</title>
<link>http://weblogs.java.net/blog/fabianocruz/archive/2006/06/junit_4_you_1.html</link>
<description>I think it&apos;s quite impressive how software testing has grown in popularity in the past decade. A lot of tools (open-source and commercial) and practices such as continuous testing and integration, code coverage, static analyzers and so forth. Some of that fancy stuff you&apos;ve probably heard about, they were originated, disseminated and now getting lift from agile development processes &quot;spaceship&quot; (e.g.: Extreme Programming, Scrum and so on). But, the agile methodologies&apos; boom is a topic for another talk. ;)</description>
<dc:subject>Testing</dc:subject>
<dc:creator>fabianocruz</dc:creator>
<dc:date>2006-06-11T15:01:52-08:00</dc:date>
</item>


</rdf:RDF>
