On Mon, 14 Oct 2002 11:27, you wrote:
> > Should I wait until the TDK is mavenized before I migrate over to using
> > maven for the migration howto?
> >
> > To mavenize or not to mavenize, that is the question :)
>
> The migration howto is really important. If considering maven is going to
> slow you down in any way I would say don't bother - we can address the
> mavenization process at a later date. That said, if you need to juggle
> directory structures, heading in the direction of the structure dictated by
> maven will make things easier in the long run.
Hi all,
OK, I have done a bit of digging and I now realise that TDK-2.2b3 allows you
to generate/develop an application using either the "classic" layout (ie:
same as TDK-2.1) or the newer "cvs" layout, which is similar to Scarab's
layout. See the "cvslayout" target in ${tdk.home}/build.xml. However, the
project build scripts that are generated do not yet fully support a webapp
using a cvs layout; work on these is required.
AFAICS, maven doesn't actually dictate a directory structure. The <build>
element in project.xml controls the project's build process and allows you to
specify the source directory, unit test directory and other resources'
directories; maven is pretty flexible in this regard. But maven doesn't take
into account templates, static html, images, logs etc, so I think the TDK
will still be relying on ant scripts to setup the directory structure of a
webapp. Someone please correct me if I am missing something.
So, I have decided to migrate my TDK-2.1 webapp to TDK-2.2b3 using the
classic layout and I will document this migration process, unless anyone has
any objections?
Is there a TODO list anywhere for TDK-2.2b3? So far, apart from the
migration howto, the things that spring to mind are:
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.
4. The TDK should generate a mavenized webapp, rather than an ant based
webapp.
Does anyone have any priorities or suggestions?
Thanks,
-- Rodney
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
