For the past few months the migration tool has been developed as an Eclipse plug-in as well as a stand-alone wizard. The reasons behind this were to make use of the Eclipse development and runtime environments and with Apache maven and ant create a process for the release lifecycle. Fortunately and timely Google donated WindowBuilder, recognized as the leading GUI builder for Java, to Eclipse enabling the wizard pages to be developed more easily. We set-up an internal version of Jira, an issue tracker running on Ingres 10, used a central mercurial repository for source control and an internal maven repository for dependencies.
The project was divided into the GUI and the migration library and the initial release was a re-factored version of the initial Swing application together with extensive release processes built around it. Thank heavens for maven lifecycle plug-ins.
One of the more serious challenges was the incorporation of the antlr parser into our build that lead to the development of an ant plug-in that split the generated Java code into multiple interfaces.
As you will notice the source for the project is not hosted on the original Ingres Migration Toolset project; that was our original intention, but our attempts to maintain the development history in mercurial when integrating changes back to the subversion repository failed (lesson learned).