Note an link to subversion downloads: SVN repository

Building HausKeys

To build HausKeys you need to install a few things. First off you'll need a version of both the JDK and the J2ME installed and configured. Furthermore you'll need to install and configure the build tool we use, Maven. Below are links to these resources where you can download them. Pay attention to the version requirements.

Setting up the JDK and WTK are pretty self explanitory however Maven may be new to you. In this case we recommend looking at this quick start guide here http://maven.apache.org/start/quick-start.html.

Setting up antenna plugin

Our build automatically pulls down the antenna plugin for working with jad files and building J2ME applications. However to properly use it you'll have to setup a build.properties file in your home directory. Here's what you'll need to put into this file:

# j2me plugin (antenna) properties
antenna.wtk.home=/usr/java/WTK2.2

This property's value is the path to your J2ME (a.k.a. WTK) installation. Set it appropriately for where you installed the J2ME on your machine.

Compiling the midlet

Once you check out the trunk or a tagged release you'll want to CD into the midlets directory. Here you can issue the following command to build the and package the sources:

maven antenna:WtkPackage
Show once ag

You can also trigger the J2ME emulator to run the application using the following command:

maven antenna:WtkRun

Problems with antenna

We're finding some issues with antenna and the jar/jad files it generates. Sometimes the Jars and Jads do not work with all phones and can often contain JDK versions of classes that are not compatible with the J2ME.
Show Although using antenna allows us to test and experiment with new features it is not the definative tool we recommend you use. It might be best for you to use ktoolbar which comes with WTK2.2. It can build, obfiscate and package the jar and generate the jad. We recommend you use this when you are ready to deploy the jar/jad to a wap server. Or better yet use our wap server by attaching the jar/jad to the HausKeys JIRA requesting it to be uploaded and installed for you in your specific area on the server.

Testing

We recommend using the WTK to test then deploying to the actual phone. Note that sometimes what you see on one phone is not what you get on another. We are currently working on ways to rectify this side effect of the J2ME platform. The application can be installed on the phone in multiple ways depending on the capabilities of the phone.

• Using a wap server (works on most J2ME phones)
• Using IrDA
• Using Bluetooth
• Using Serial or USB connector (BlackBerry)

Versioning HausKeys

There are issues with using Maven SNAPSHOT versions. The problem rests in the fact that J2ME JAD files do not accept 0.6-SNAPSHOT as a valid version string. One must not include alpha characters. So the revision in the trunk is considered to be equivalent to the latest snapshot version. Since other applications do not depend on this midlet its ok to do this. When we are ready with the trunk we can release it and stabilize a version by tagging it and bumping the revision up in the trunk.
So if we're at revision 0.6 in the trunk this is the current snapshot. It can change as does any snapshot since it has not been released. When we're ready we
svn cp it to the tags folder and at the same time we bump the revision in the trunk to 0.7.