Created on 2013-12-19.13:06:16 by eaaltonen, last changed 2014-10-24.07:41:22 by eaaltonen.
This is about supporting multiple applications which have a different CLASSPATH, essentially giving everyone their individual namespace.
I have a shell scripting based implementation which may better explain what I am proposing.
Suppose we have two applications: a and b.
$ ls -R *
a:
a.py setclasspath.sh
b:
b.py setclasspath.sh
In linux you can specify the interpreter, for example you can start a.py with
#!/usr/bin/env jython
which is awfully convenient, since you can then run you jython script by simply calling it:
$ ./a.py
The attached 'runjython' script acts like the jython interpreter, but will first call setclasspath.sh, setting the classpath for the current application.
This of course only works on linux, but demonstrates the aim of having separate 'classpath namespaces'. It also combines very nicely with IPython.
After experementing with this recently, I think the conxtextual behaviour should be as follows
if (passed a script as an argument):
trySetClassPathBasedOnLocation(script)
else:
trySetClassPathBasedOnLocation(current_working_directory)