John McNally wrote:

> I would recommend the head of 2.x tree over 2.1, but better yet try
> using the code in the standalone torque repo.  And there is no need to
> have webmacro for torque, are you using it for your application screens?


The standalone torque repo - excuse my ignorance but does this include a 
full version of turbine? How does it differ from the turbine-2 repo?

I am not using webmacro at all - I went through and binned a lot of the 
webmacro-related files in places like turbine/modules/actions. Also 
python stuff etc. Perhaps I messed up the inital build which I know 
should detect which optional jars are present - but am I right in 
thinking that it doesn't do this test for webmacro?

Also John - did you happen to notice my mail about postgres stuff 
yesterday? I seem to be running up against a lot of small build errors 
for postgres. For instance, as well as the  missing torque templates, 
the unix.vm template is not properly populated with a user parameter 
when calling createdb and dropdb.

In a previous post I also mentioned the bad foreign key references that 
are generated when an alias to the turbine_user table is specified in 
the torque schema.

In connection with a previous poster mistakenly capitalising idbroker in 
their torque schema, it is worth noting that it is shown capitalised in 
the example at the top of:

http://jakarta.apache.org/turbine/turbine-2/howto/torque-schema-ref.html

Cheers,
colm



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to