I used to use WP-Syntax but I think this looks oh so nicer!
public class Hello {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}
Check it out at here.
I’ve recently moved to Firefox 3 on my MacBook Pro. The first thing I noticed was pretty much all of my Firefox plugins stopped working. This didn’t really bother me until I started developing on the laptop. The two things I really missed were Web Developer and FireBug.
After a little bit of googling, I was able to find other people with the same problem and fixes. While these are not official releases, they seem to be working just fine for me.
Check them out below:
I rebuilt my slice from scratch after screwing up my installations of ruby and rubygems. Good thing I had the WP-DB-Backup or else I would have lost all of my posts!
Yay! I got apache upgraded to 2.2 from 2.0. It was a lot easier after I was told by Aaron that Feisty has 2.2 in their apt-get repositories. I just had to update from Dapper to Feisty. Prior to updating I did have to comment out all of the repositories I had added to my /etc/apt/sources.list. I was running into some broken wgets otherwise.
After commenting out the additional repository lines, I just followed the steps here and viola! apache2.2 comes up.
I did have to reinstall mod_jk for apache2.2 but that was a easy.
And the day is mine.
Well, I got to like the second step before I hit another roadblock. Looks like kodefoo’s repository only supports binary-i386 releases. Too bad my slice is on an AMD64 machine which means I need the amd64 release. I guess if I want to cluster mongrel with apache, I’ll have to compile from source. Sigh…
Prior to hitting this road block, I ran apt-get remove apache2 and it didn’t remove apache2 from my slice even though it said it did. So that’s a little confusing. I continued with the kodefoo tutorial regardless until I came across the problem noted above. I’ll eventually have to figure out how to do a clean remove of apache2.
At this point, I think I am just going to try to get a single mongrel served up through apache2. Hopefully, this will be easier…