<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>LuckyCatLabs</title>
	<link>http://blog.luckycatlabs.com</link>
	<description>Making code suck less</description>
	<lastBuildDate>Tue, 16 Mar 2010 01:37:56 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Release (Sort-of): RubySunrise Gem</title>
		<description><![CDATA[As a follow-up to the Java sunrise/sunset calculator I released early last year, I&#8217;m releasing a ruby gem that does essentially the same thing.  Just in A LOT less code, but with the same attention to test goodness.
To install and use the RubySunrise gem just:
$ gem install RubySunrise
or download from RubyGems. 
The current version [...]]]></description>
		<link>http://blog.luckycatlabs.com/2010/03/15/release-sort-of-rubysunrise-gem/</link>
			</item>
	<item>
		<title>Maven with Ruby Part II</title>
		<description><![CDATA[Want to add something to your projects Maven builds (like code coverage&#8230;) but don&#8217;t want to CTL-C/CTL-V your way to boredom?  Use the below script to lend a hand.  Substitute the XML in the SNIPPET variable to the artifact/plugin/dependency to be injected (leave the  tag in place) and use the command:

$>ruby mavenInjector.rb [...]]]></description>
		<link>http://blog.luckycatlabs.com/2009/03/20/maven-with-ruby-part-ii/</link>
			</item>
	<item>
		<title>Using Ruby To Help Maven</title>
		<description><![CDATA[Maven projects can become a wasteland of neglected, old dependencies: huge, unmanageable pom files  and a local repository that&#8217;s catalog of every Apache project in the past 10 years.  Who knows if your project still requires that old version of Xerces?
This script takes the name of a dependency and removes it from every [...]]]></description>
		<link>http://blog.luckycatlabs.com/2009/03/13/using-ruby-to-help-maven/</link>
			</item>
	<item>
		<title>Licensing Your Code the Ruby Way</title>
		<description><![CDATA[Do you have an existing project you want to open-source?  Does the thought of manually adding the license comment block to EVERY. SINGLE. SOURCE. FILE. sound not-so-exciting?  Here&#8217;s some help, ruby style:

class Licenser

    def licenseFiles(dir)
          filenames = Dir[dir.chop + "**/*.java"]
	  [...]]]></description>
		<link>http://blog.luckycatlabs.com/2009/01/31/licensing-your-code-the-ruby-way/</link>
			</item>
	<item>
		<title>Release: Sunrise/Sunset Java Library</title>
		<description><![CDATA[New from LuckyCat Labs is a Java library that computes the sunrise / sunset using GPS coordinates and today&#8217;s date.  To use, simply download the tar or zip file from the GitHub page, or use git to pull the source:
$ git clone git://github.com/mikereedell/sunrisesunsetlib-java
Once you have the source, use the command:
$ ant all
To compile the source, [...]]]></description>
		<link>http://blog.luckycatlabs.com/2009/01/27/release-sunrisesunset-java-library/</link>
			</item>
</channel>
</rss>
