<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>JR Boyens</title>
 <link href="http://jboyens.github.com/atom.xml" rel="self"/>
 <link href="http://jboyens.github.com/"/>
 <updated>2010-03-15T18:44:27-07:00</updated>
 <id>http://jboyens.github.com/</id>
 <author>
   <name>JR Boyens</name>
   <email>jboyens@fooninja.org</email>
 </author>

 
 <entry>
   <title>Fixing Grails Dependency Resolution</title>
   <link href="http://jboyens.github.com/2010/03/15/fixing-grails-dep-resolution.html"/>
   <updated>2010-03-15T00:00:00-07:00</updated>
   <id>http://fooninja.org/2010/03/15/fixing-grails-dep-resolution</id>
   <content type="html">&lt;p&gt;In Grails 1.2 an Ivy dependency resolution &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; was added to&lt;br /&gt;
BuildConfig.groovy that allowed you to specify your dependency resolution in&lt;br /&gt;
Groovy.&lt;/p&gt;
&lt;p&gt;This was good.&lt;/p&gt;
&lt;p&gt;The problem was, it doesn&amp;#8217;t support Maven classifiers.&lt;/p&gt;
&lt;p&gt;This is bad.&lt;/p&gt;
&lt;p&gt;I&amp;#8217;ve looked at the &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; implementation and I don&amp;#8217;t think it&amp;#8217;s really that&lt;br /&gt;
hard to add it and I&amp;#8217;m going to try my hand at fixing it in the next few days,&lt;br /&gt;
but in the meantime, I&amp;#8217;ve come up with a workaround.&lt;/p&gt;
&lt;p&gt;The workaround (really hacky I may add) is below:&lt;/p&gt;
&lt;script src=&quot;http://gist.github.com/333354.js?file=fix-grails-classifiers.groovy&quot;&gt;&lt;/script&gt;</content>
 </entry>
 
 <entry>
   <title>GitHub repo for groovy snipMate snippets</title>
   <link href="http://jboyens.github.com/2010/02/15/snipMate-snippets.html"/>
   <updated>2010-02-15T00:00:00-08:00</updated>
   <id>http://fooninja.org/2010/02/15/snipMate-snippets</id>
   <content type="html">&lt;p&gt;I&amp;#8217;ve forked the snipMate snippets &lt;a href=&quot;http://github.com/scrooloose/snipmate-snippets&quot;&gt;repo&lt;/a&gt; and created &lt;a href=&quot;http://github.com/jboyens/snipmate-snippets&quot;&gt;mine&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#8217;ve added some basic snippets that I used daily, mostly for &lt;a href=&quot;http://groovy.codehaus.org&quot;&gt;groovy&lt;/a&gt;, &lt;a href=&quot;http://www.grails.org&quot;&gt;grails&lt;/a&gt;, and &lt;a href=&quot;http://www.spockframework.org&quot;&gt;spock&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Maybe someday I have the main repo pull once it&amp;#8217;s cleaned up a little&lt;/p&gt;</content>
 </entry>
 
 <entry>
   <title>Trying out hacker blogging</title>
   <link href="http://jboyens.github.com/2009/02/02/trying-hacker-blogging.html"/>
   <updated>2009-02-02T00:00:00-08:00</updated>
   <id>http://fooninja.org/2009/02/02/trying-hacker-blogging</id>
   <content type="html">&lt;p&gt;I&amp;#8217;ve been thinking about blogging some more and I really didn&amp;#8217;t want to go through the hassle of dealing with setting up some blogging software. I&amp;#8217;ve even &lt;span class=&quot;caps&quot;&gt;WRITTEN&lt;/span&gt; blogging software (See &lt;a href=&quot;http://svn.rifers.org/elephant/trunk&quot;&gt;Elephant&lt;/a&gt;) before and I didn&amp;#8217;t want to deal with it. Either I&amp;#8217;m really lazy or the state of software today favors complexity instead of thinking of existing systems in new ways.&lt;/p&gt;
&lt;p&gt;I had just left the thoughts, frustrations, and comments well up inside. I&amp;#8217;ve lost more ideas than I care to count. So, I had to do something. Then &lt;a href=&quot;http://tom.preston-werner.com&quot;&gt;Tom Preston-Werner&lt;/a&gt; wrote a post about &lt;a href=&quot;http://tom.preston-werner.com/2008/11/17/blogging-like-a-hacker.html&quot;&gt;Blogging Like a Hacker&lt;/a&gt; &lt;sup class=&quot;footnote&quot;&gt;&lt;a href=&quot;#fn1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;. Initially, I was a little confused, but it seemed cool. I threw it off for a time and went about my business. My mind kept coming back to it though. I enjoyed the idea that you could use the filesystem, Git and &lt;a href=&quot;http://www.github.com&quot;&gt;GitHub&lt;/a&gt; (more on that later) in such a way. It seemed so clean, so light, so… perfect.&lt;/p&gt;
&lt;p&gt;I&amp;#8217;ve got a GitHub account, but most of the stuff I write, is, of course, owned by my employer, &lt;a href=&quot;http://www.chacha.com&quot;&gt;ChaCha Search&lt;/a&gt;. As such, my GitHub account is very bare. I&amp;#8217;ve only thrown one project up there that I didn&amp;#8217;t spend more than an hour or so on. Still, I love they way the way that GitHub works and storing my blog in a Git repository (which is by far the most incredible source control on the planet) seemed too cool to pass up.&lt;/p&gt;
&lt;p&gt;So here I am. One tiny voice in an ocean of content. I don&amp;#8217;t know if this will be useful to any one but it lets me express myself.&lt;/p&gt;
&lt;p class=&quot;footnote&quot; id=&quot;fn1&quot;&gt;&lt;sup&gt;1&lt;/sup&gt; If you didn&amp;#8217;t notice, I used Tom&amp;#8217;s templates and &lt;span class=&quot;caps&quot;&gt;CSS&lt;/span&gt; to build my own blog here. I plan on changing it, but it helps to stand on someone else&amp;#8217;s shoulders.&lt;/p&gt;</content>
 </entry>
 
 
</feed>