Hi all, I have cross-posted this to turbine-user as I noticed that there were many people already using TDK-2.2b3 on the turbine-user list, so maybe some of them would like to help us with the TDK-2.2 release.
I have been carefully migrating my TDK-2.1 webapp to TDK-2.2b3 between interruptions here at work and in the meantime taking lots of notes and trying to find and fix any bugs that I find along the way. I am going to attempt to use the coupled services rather than Fulcrum, as Martin and Jason have agreed that we should backport the stuff from fulcrum to turbine-2. However, the latest version of Torque doesn't allow me to use the coupled version of Intake... see Issue #TRQS37. I have also found some other problems with TDK-2.2b3... see issues #TDKS4, #TTWS7, #TRQS35, #TRQS39 and #TRQS40. Unfortunately, I need to do some more work on my application here at work, but I should be able to start working on the TDK again in a couple of weeks. I will compile my notes into a Migration Howto as soon as some of the abovementioned issues have been resolved. Apart from the Migration Howto and any additional bug fixes, the following still needs to be done before a TDK-2.2 release: 1. The TDK howto needs to be rewritten for TDK2.2. 2. The build scripts of a TDK generated webapp should allow the webapp to access multiple databases (ie: support for multiple torque schema.xml files), rather than assuming that all the tables are in the same database. 3. The build scripts should support development of webapps in both the "classic" and "cvs" layouts. The classic layout works fine, but the cvs layout needs some more testing/fixing. 4. The Turbine 2.x website documentation should be brought up to date. Is anybody aware of anything else that needs to be done? Regards, -- Rodney -- To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
