The first release candidate of DojoBuilder has just been released. DojoBuilder is an Eclipse RCP based tool for generating customised builds of the Dojo Ajax toolkit. It provides a number of useful utilities for working with Dojo, including checking out the source code from source control (Subversion), configuring the build, and running the build. For information on what it can do, check out
Archive for the ‘Ant’ Category
Posted by Shane O'Sullivan on March 1, 2007
Posted by Shane O'Sullivan on February 19, 2007
The first Linux release of DojoBuilder beta has been released, after my epic effort at getting Ubuntu 6.10 installed on my Thinkpad. DojoBuilder is an Eclipse RCP based tool for generating customised builds of the Dojo Ajax toolkit. It provides a number of useful utilities for working with Dojo, including checking out the source code from source control (Subversion), configuring the build, and running the build. For information on what it can do, check out my first post on the subject.
The following downloads are available:
- Windows standalone version
- Linux standalone version (tested on Ubuntu Edgy)
- Eclipse update site , for integrating DojoBuilder with your development environment.
These previous posts explain further about the capabilities of DojoBuilder.
Posted by Shane O'Sullivan on January 8, 2007
Following on from my earlier post about the Eclipse RCP based tool I was building for Dojo, the first beta release is now available. You should read my first post on the subject for an overview on what it is, why it exists and what capabilities it has.
Steps to use the tool (Windows only for the moment, other builds coming soonish):
- Make sure you have Java 5 or greater installed on your machine. You can get it from http://java.sun.com/javase/downloads/index_jdk5.jsp , click on the download button next to “Java Runtime Environment (JRE) 5.0 Update 10“. Once it’s installed, make sure that you your PATH variable is set correctly by opening a command prompt (Start/Run/cmd) and typing “java -version”. It should print out a version of 1.5 or higher.
- Download my tool from http://www.skynet.ie/~sos/dojobuilder/downloads/DojoBuilder.zip .
- Extract the zip file and click on the DojoBuilder.exe file. This opens the application with four view panes.
- Ant Builder Control – This is used to specify the Ant build file to use
- Ant Properties – Lists the user editable properties on the Ant build project. Usually you shouldn’t have to touch these if you don’t want to, the Dojo tooling should take care of it.
- Ant Targets – Lists the available Ant targets. You shouldn’t have to touch these if you don’t want to, just use the “Target Set” combo box in the “Ant Settings” pane.
- Choose a Dojo build you want to use in the “SVN Repository” combo box (only nightly and 0.4.1 have been tested so far).
- Click the “Use customized Build Source” checkbox.
- Choose a Target Set you want to build. “Release” is the most common.
- Choose a “Build Profile” you want to build, or just leave it at the default.
- Click the “Build” button.
This should result in a Dojo build being created in the “release” folder of your checked out source files. By default, these are placed in your home directory, as shown in the “Svn Dir” text box. You can change this if you like. You can also change where you want the built files to be placed by changing the “Build Dest” text box.
As this is the very first beta release, it is of course not yet perfect. If you have any issues, please reply to this post with details.
Posted by Shane O'Sullivan on January 3, 2007
Just a tiny Ant tip – I’ve been fooling around with Apache Ant for the first time, and needed to change the working directory so that, rather than it being the folder in which the build.xml file is located, it be somewhere else. This enables files in other directories (which I don’t control) to use relative paths to other files. I tried setting the System’s “user.dir” and “basedir” properties, but these didn’t work.
So, the solution is very simple, in your <java> task, set “fork” to true, and then set the “dir” property to the folder you want to use as a working directory.
<java fork=”true” dir=”c:\work\lib”>
No doubt this has been documented somewhere else, but a quick search on Google didn’t readily find it for me, so here you go. Enjoy!