Simple fix to missing tools.jar in JDK on Mac OS X

Today I ran into a situation where a 3rd-party pom.xml had a dependency on tools.jar.  I'm stuck using Java 6, due to project requirements, which means I have to use the Apple supplied JDK.  The problem is Apple bundled all the classes normally found in tools.tar into classes.jar.  Since I couldn't modify the pom file, I simply creating a symbolic link to classes.jar.

 $> sudo ln -s /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/classes.jar /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/tools.jar  
 $> sudo ln -s /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/lib  

Problem solved!

Building Growl 2.0.1 to Save $4.99

Today I figured it was time that I bit the bullet and upgraded my instillation of Growl from 1.2.2 to the latest - 2.0.1.  I resisted upgrading before because 1.2.2 was the last free compiled version available.   I am way too cheap to pay for an Open Source project but I never had the ambition to build it.  Hello Mr. Ambition!

Building Growl...how hard can it be?  The Growl developers even have a little write up here on how to do it.  Let's find out.

Requirements

The official build notes list the following requirements:

• OS X Lion - 10.8
• Xcode
• A tool to pull down a clone of the repo, the mercurial client
• A working Git client
• A working subversion client

How many different version control systems does one project need?  I'm running OS X Lion 10.7.5 so it looks like I meet all the requirements.  No version of Xcode is recommended so I'm going with the latest that I have - 4.6 (4H127).