[derby] DERBY_HOME can not be properly set

[martin.osx@…]

Hello,

one can not set the DERBY_HOME variable propperly in derby. See extract from "/opt/local/bin/derby_common.sh":

[...]

# set DERBY_LIB location
DERBY_LIB="${DERBY_HOME}/lib"

[...]

# set local classpath, don't overwrite the user's
LOCALCLASSPATH=$DERBY_LIB/derby.jar:$DERBY_LIB/derbynet.jar:$DERBY_LIB/derbytools.jar:$DERBY_LIB/derbyclient.jar

[...]

As you can see it is expected that ${DERBY_HOME}/lib/derby.jar exits but derby.jar is installed in /opt/local/share/java/derby.jar.

I suggest that installation is done similar to ant or maven2 which both create a subdirectory in /opt/local/share/java/.

[blair (Blair Zajac)]

Well, given we're installing Derby into a non-standard install (for it), I think I would rather patch derby_common.sh to change DERBY_LIB to point to the share/java. We don't install any jar's into lib, so we'll have to patch it. Installing all the Derby jar's into a subdirectory, say /opt/local/share/java/derby, won't fix this, we'll have to patch derby_common.sh.

I don't have too many cycles, but if you agree, could you send a patch to have derby_common.sh set DERBY_HOME to $prefix and DERBY_LIB to $DERBY_HOME/share/java.

Regards, Blair

[martin.osx@…]

Suggested changes

[martin.osx@…]

I noticed some other problems when trying to start a server: Not all shell scripts are installed into bin. I attached a patch which will install all files into /opt/local/share/java/derby and symlinks the shell scripts to /opt/local/bin. This is the same technique used by ant and maven2. It think this is a far better approach.

Martin

[blair (Blair Zajac)]

I've taken your approach and in r64413 dropped the entire Derby install into ${prefix}/share/derby then set up the appropriate symlinks.

I didn't set up the other tools in bin besides ij, syinfo and dblook. Are all of them needed?

[blair (Blair Zajac)]

Please reopen or open a new ticket for additional modifications.