Timothy, Akmel was kind enough to send these settings to make the tdk-2.2-b1 newapp run correctly: Add the following to the build.properties file in the tdk home directory, then run "ant" from the tdk home directory:
tdk.home = c:/path_to_your_kit/tdk target.database = mysql createDatabaseUrl = jdbc:mysql://127.0.0.1/mysql buildDatabaseUrl = jdbc:mysql://127.0.0.1/newapp databaseUrl = jdbc:mysql://127.0.0.1/newapp databaseDriver = org.gjt.mm.mysql.Driver databaseUser = databasePassword = databaseHost = 127.0.0.1 then add this to the build.properties in tdk/webapps/newapp/web-inf/build, ------------------------------------ tdk.home = c:/path_to_your_kit/tdk target.database = mysql database.driver = org.gjt.mm.mysql.Driver ----------------------------------- Then run "ani init" from the tdk/webapps/newapp/web-inf/build directory. Good luck, Randy Timothy N. Jones wrote: >Has there been any progress fixing the tdk build process? I've had an >extremely frustrating time unsuccessfully trying to build any of the >"releases" of tdk and turbine-2 I could find, and pulling down the >jakarta-turbine-tdk and jakarta-turbine-2 CVS packages (and those I could >find they depended on) and trying to build from the source was similarly >unsatisfying. > >With tdk-2.1 I get mysterious VerifyErrors about java method signature >mismatches (bad turbine-2.1.jar file?), and with tdk-2.2b1 there are >undefined properties and/or an imcomplete build.xml file. Building from the >CVS source ends in a maze of twisty little undefined property references. > >Can someone who has actually been able to set up "newapp" from either a tdk >release or the CVS tree kindly post their build.properties file(s)? I'm >using mysql, for what it's worth. > >Thanks, >Tim > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
