Yes, I did not address the issue of including the jython runtime. In
my case, my app is distributed over Java Web Start, with the various
jars having their own jnlp file.
1. jython.jar: the runtime.
2. jython-lib.jar: the compiled contents of the jython Lib directory.
3. app.jar: my app.
Etc. In this way, when my app is updated, users only have to download
app.jar, not the entire runtime and libraries (as long as their Java
Web Start cache has not been cleared).
The price of using python on top of java is that you must have a the
jython runtime. For some, this is a high price, either due to
complexity, size, the difficulty of selling it to management, etc. In
my case, the payoff of programming in python and delivering it as a
java app is well worth it.
PS. Sorry for the double reply Alan.
On Thu, Nov 12, 2009 at 12:32 PM, Alan Kennedy <jython-dev@...> wrote:
>> 4. So when you make a jar, it is only necessary to include the java .class files
>> For example,
>> mymodule.py -> mymodule$py.class
>> It would not be necessary to include mymodule.py in the jar, only
> This looks like the sort of thing that "jump" could do, although I
> don't know if it does right now.
> Perhaps the OP might enter a feature request for it?