Oh, well, sorry but I missed that discussion on the list.
But I now reviewed both your problem as well as the solution provided by Krishna Kumar.
First of all, your problem had nothing to do with this, but was caused by incorrect settings in your build environment.
The failed sql statement you showed:
[sql] Failed to execute: INSERT INTO PREFS_NODE VALUES(1,NULL,'',0,'/','2004-05-22 14:57:53.586','2004-05-22 14:57:53.586')
is not from the Oracle specific populate-userinfo-for-default-psml.sql, but from the one for Derby.
Anyway, I also looked at the solution Krishna Kumar proposed.
Although it might "work" more or less, I don't find it a "proper" solution.
Oracle8i simply doesn't support TIMESTAMP fields. Its finest time resolution is only 1 second!
Simply replacing TIMESTAMP values with DATE values doesn't cut it for me.
On Oracle8i the only way to store TIMESTAMP level time resolution is storing the millisecond representation itself.
I've been developing and testing Jetspeed for over 2 years now using Oracle9i, so be assured it doesn't need any patching for that.