[Pljava-dev] problems running test suite

John R Pierce wrote:
> I've built pl/java for Solaris 10 Sparc 64bit, with Sun JDK 1.5.0
> 64bit and Postgres 8.4.3 64bit... I used `HEAD` from the pljava CVS
> about 5 days ago (I see Jurka has checked in some new stuff since
> then, if there's a reason to go ahead and rebuild I will...). To get
> this build to work, I had to track down the packager of the Solaris
> binaries, and acquire pg_config.h and Makefile.global from him as he
> mistakenly packaged the wrong 32bit files with the 64 bit binaries. ....

and, even stranger. So I bundle up my files with instructions and
pass them off to our production folks to deploy on their staging/test
server. After some minor issues with sorting out the CLASSPATH,
LD_LIBRARY_PATH and PATH and JAVA_HOME, they get it installed just fine
by running the Deployer...

but, when we try and load the examples.jar, we get this...

$ psql -c "SELECT
sqlj.install_jar('file:///app/postgres/8.4/pljava/examples.jar',
'samples',true)" dbname pgadmin
Password for user pgadmin:
ERROR: java.lang.SecurityException: read on
/app/postgres/8.4/pljava/examples.jar

pgadmin is the superuser and the owner of the 'dbname' database..
also the owner of the examples.jar file. in fact, also the owner of the
whole postgres cluster.

I dunno how to get any more info on why this is happening.... but... I
compiled and tested on postgres 8.4.3 with Sun JDK 1.5.0_24, and this
staging server has postgres 8.4.1 and Sun JDK 1.5.0_18... could that
make a difference like this? I've asked them to update their
postgresql. and they can probably update their Java too, if it will
matter.

Or should I build from HEAD again, since I grabbed CVS HEAD on the 15th,
and as I note above, I saw there were a couple minor updates in the
meantime ?.