Re: [Exist-development] SourceForge Repo Clone Complete

[Hungerburg <pc...@my...>]

Am 2012-08-15 12:12, schrieb Dannes Wessels:
> You command is a fresh checkout, right? The URL should work for ReadOnly
> access to the new repository (but some of Adam's recent fixes are not
> migrated yet)

Dannes, the fresh checkout worked alright. I prefer stable over trunk 
and I guess that 2.0.x is where maintenance gets performed. The build 
with openJDK6 worked out OK too. eXist is now running, everything fine 
so far, below my commands from the terminal:

$ svn checkout svn://svn.code.sf.net/p/exist/code/stable/eXist-2.0.x
$ echo "include.module.xslfo = true" > extensions/local.build.properties
$ export JAVA_HOME=/usr/lib/jvm/default-java
$ export EXIST_HOME=/opt/eXist-2.0.x
$ unset DISPLAY # must not point at remote host by ssh
$ ./build.sh svn-download # to make the build system
$ ./build.sh svn-prepare  # tag releases with the revision
$ ./build.sh
$ ./build.sh -f build/scripts/jarsigner.xml
$ bin/startup.sh

Pointing the browser at http://...:8080/exist/admin/admin.xql I notice, 
that I cannot set the password of admin from the WEB panel, because that 
requires a group to be set, and there are no groups to select from 
there! (Like stated there though, the RPC client works.)

Creating a new user, I notice, that I cannot create new groups, not from 
the RPC client, but can do from the WEB admin panel ;)

> About OpenJDK6 ... the old statement still applies: It might work (it
> will certainly), but we don;t test against it ourself, hence support is
> limited from our side. JDK7/OpenJDK7 wil make it different.....

Does that say, that I should rather use OpenJDK 7 instead of 6? I would 
like to share my experiences, and if I understand you correctly, using 
openJDK6 will make them worthless… So should I better start from scratch 
with 7?

-- 
peter