Well, in that case, you'd have to install JPython.
And then, you'd need to have a .bat/.sh routine to start up the java based
startup script...But, hey, we can do THAT in JPython too! But wait....
Since the scripts basically just set a couple of ENV variable and then "java
xxx", you're in an endless loop.
The simplest solution is that the tools can be distributed completely as a
single .jar file, and be started with: java -jar app.jar. I believe in
Linux, you could make a .jar file "executable", and then only have to type
app.jar. On Mac OS X, they have their own bundler that makes ".jar"s
launchable from the desktop. I don't recall if .jar can be appropriately
associated on Windows or not.
Best Regards,
Will Hartung
([EMAIL PROTECTED])
From: "Christopher Berry" <[EMAIL PROTECTED]>
Sent: Wednesday, June 06, 2001 3:21 PM
> I have another suggestion. In a sense, a reversal. I think it might be
> cleanest to centralize the scripts to a single, 100% Java-based solution.
> Say, Jython. Then, just like Ant, we stay completely OS-agnostic.
