I've been trying out Joomla on a prototype site. It's called http://www.tedkubaska.com. It uses Joomla 1.5RC4.

I hosted it on GoDaddy. It costs $6.99 a month. It's basically a streamlined version of the web site at http://www.ieee-or.org.

I chose to download my own copy of Joomla rather than use the one provided by GoDaddy. I don't know what version of Joomla GoDaddy has, but in December (when I started the site) I suspect it was not as recent as 1.5RC4.

There were some problems getting 1.5RC4 up and running, specifically with the JEvents package. First of all, the JEvents component would just not work with 1.5RC4. There was a name change in the code that was not thoroughly propagated. JEventDispatcher was changed to JDispatcher in most but not all instances. So you have to make that change explicitly.

There are other event packages. I used this one because it was the first one that worked for me; but then, as I said above, it didn't work right way.

The files I downloaded were the following (these are alpha; a beta is available):
    com_events1.4.3alpha.zip
    mod_events_cal_1.4.3alpha.zip
    mod_events_latest_1.4.3alpha.zip
    mod_events_legend_1.4.3alpha.zip
    bot_events_search1.4.3alpha_joomla1.5.zip

These consist of the component, a calendar module, a latest module, a legend module, and a search bot (Joomla calls bots plugins; the term bot here seems to be left over from Mambo). I'm not using latest and legend; but they work. At first both the calendar and legend modules appeared twice on the page. Fix the duplicate calendar by removing some duplicate lines in mod_events_cal.php. Fix the duplicate legend by deleting (or commenting out if you're nervous) what for me is line 48 in mod_events_legend.php. It's a line that says if your version is >= 1.5 echo the content.

I've also been working with ReMOSistory, but I'll talk about that another time.

I saw these going to pick up the mail this morning

The Eclipse Portland DemoCamp is scheduled for 12/10/07 at the Kennedy School. Details (list of presenters and attendees, schedule of demos, directions) are on http://wiki.eclipse.org/Portland_DemoCamp .

I'm giving a demo on setting up an automated build system (continuous integration) for the Eclipse ECF project.

Here are my slides.

AutoBuild.ppt (1.16 MB)

Here is a writeup.

AutoBuild001.pdf (2.65 MB)

Here is another demo for a prototype website

ieeeDemoB.wmv (1.15 MB)

Here is a demo for a prototype web site

ieeeDemoA.wmv (433.57 KB)

I went to the Wallowas again this year. Lory went with me. Just a short trip ... two nights. We couldn't do a car shuttle, so we just went up the Wallowa Lake trail to Six Mile Meadow. We camped there and we're all alone. The next day we went to Horseshoe Lake and again we were the only ones there. We camped for the second night and then the next day retraced out steps. Here are some photos.

Wallowas2007.zip

The default 64-bit Java that came with my Suse 10.2 installation does not work for me. I can get a Java that works by downloading the 64-bit Java from Sun. Here are the details.

SuseJava001.pdf (219.68 KB)

Lory, Archie, and I did this hike on Saturday. We hiked as far as Eclola Park. It's another mile or so to our house, but we had left a car at Ecola Park and then drove home.

Here are some photos (about 7MB).

SeasideToCB.zip

Here are yet some more notes on setting up CruiseControl to run with ECF.

StartingUpCC005.pdf (2.04 MB)

This file describes how to access CruiseControl remotely. I use ssh to start vncserver on the Linux build machine, then run realvnc on Windows. The file then shows running the Java WebStart CruiseControl GUI, the CruiseControl Web Reporting Project, and the JMX console through the resulting connection. The file ends with instructions on how to create a login window with PHP.

I'm not posting Part 6 of my notes. This part deals mainly with setting up MySQL and Apache2 on Ubuntu. Apache2 on Ubuntu (at least the Apache2 brought down with Ubuntu's Synaptic Package Manager) is configured differently than the Apache installed on OpenSuse 10.2 through YaST. A key point is using --bind-address when invoking MySQL so that I can invoke it with -h <hostname> and not just -h localhost. The Apache2 instructions are described well at the following URL: http://linuxhelp.blogspot.com/2006/02/host-websites-on-your-local-machine.html

I got three more files of notes.

StartingUpCC007.pdf (288.39 KB)

StartingUpCC008.pdf (186.34 KB)

StartingUpCC009.pdf (424.13 KB)

The first file (Part 7) shows how to rotate the cruisecontrol.log file and set up a crontab entry to delete old build log files. The second file (Part 8) describes how to make ssh key pairs. The third file (Part 9) discusses how to treat scheduled builds and user-initiated builds.

Here are some more notes on setting up CruiseControl to run with Eclipse ECF.

StartingUpCC003.pdf (676.02 KB)

StartingUpCC004.pdf (885.84 KB)

The first file describes the two kinds of builds we are interested in: an Auto Build and a Daily Build. We're building from the HEAD and offering the HEAD for download. The file also describes the CruiseControl GUI that runs under Java Web Start; the file shows how to force a build with this CruiseControl GUI.

The second file describes the installation necessary before you do anything specific about ECF. The file describes how to install CruiseControl and Ant. Then, the file descrbes how to test the installation, using an example from Mike Clark's Pragmatic Project Automation. Next, the file describes how to install TomCat and create the cruisecontrol.war file. Finally, the file contains a copy of a vsftpd.conf that works for me. When I wrote this, I thought we were going to use ftp (rather than scp) to transfer files.

I've been setting up an automated build system for Eclipse's ECF project. Here are some notes ...

StartingUpCC001.pdf (1.05 MB)

StartingUpCC002.pdf (715.33 KB)

The first file describes how to invoke CruiseControl and TomCat. Then, it describes CruiseCntrol's Web Reporting Project (CCWR), which is a cruisecontrol.war file that gets placed in TomCat's webapps directory and is accessible via port 8080. You can use this CCWR to force builds. The file also describes CruiseControl's JMX console. Then, the files shows where the built zip files and built update site reside.

The second file describes how to set up the build environment for ECF. A sample build is performed with ant outside of CC. Then, the file describes some details about CC's config.xml file. The file contains an explanation of quiet time ... with a figure. Then, the file describes how the built files are uploaded and gives more details about config.xml.