Updated my Eclipse Platform Extensions plug-in

Since Eclipse released 3.3/Europa I thought I should update my plug-in to match the release.  Plus there were a couple of people nagging nudging me to do it in the help forum.

There was not much changes in Eclipse that would affect the plug-in, but I decided that I won't cheese it and just increment the version number support on my plug-in and instead do some of the things I was meaning to learn, namely i18n of the plug-in.  That objective was completed successfully.

Here are some of the things I have learned while making this release.

• The current instructions for internationalizing Eclipse plug-ins using fragments is woefully out of date.  Eclipse 3.3 does not use fragments.xml I think they got rid of that requirement long ago and use MANIFEST.MF instead.
• When doing IVT of your plug-in with fragments, use the -clean parameter when starting up Eclipse.  I spent a lot of time trying to figure out why my plug-in did not switch to Japanese.
• Fragments do not automatically get built from the site, which is weird.  I have opened a bug report for it.
• Maven and Eclipse plug-in development is currently a lost cause (or at the very least a big pain).  I have removed the use of Maven from my plug-in, but I am keeping the Maven project layout since it seems more sane.

My attempts at Japanese and French are woefully laughable, maybe someone would release a patch for it.  Well I am trying to relearn Japanese and maybe Chinese as well as French.  So this provides me a way of doing this.

Along with this, I made some attempt to write yet another Ruby script to update my site.  I still don't like the libraries for Ruby, the language I can get around a bit.  Some findings I had were:

• I much prefer Java's import over the require.  At least whatever I import matches what I am going to use, rather than trying to figure out what the classes are in the module.
• There should be an ri that loads up the browser.  Or at least something that would update a core documentation like Perl does.
• They seriously need to work up on the consistency even in the Core libraries.  e.g. RUNIT::CUI vs RSS::RSS vs Sync_m.  Java's API naming may sometimes suck, but at least they suck relatively consistently with minor exceptions such as URL.
• Someone should refactor net/sftp to work like net/ftp or at the very least provide some useful and easy to find examples within their RDocs.  I had to Google to find an article that provides an example on how to do it (not really the best way of doing something, but the most efficient with the stuff out there).
• I wish the Maven repository was as good as Gem in terms of amount of JARs sometimes, thankfully there is a search engine for Mavenized JARs.

This is also my first attempt at using Windows Live Writer for my blog entry as Blogger's WYSIWYG editor is quite painful to use.