Updike, Clark wrote:
>>But I really wanted to know your experience with org.* and com.*
> If you mean, did I get them to build error-free using the jython
> build.xml file? Yes. They also appear error free in eclipse with
> automatic build turned on. Now this is all for the now out-of-date
> new style branch, which is what I initially set up to work on.
> But the ant build doesn't seem to care if the jars exist one way
> or another, only the eclipse automatic build does. I'm guessing
> these are considered "client supplied" jars and aren't required
> for a valid build, but that's just a guess. Can anyone comment
> on this?
This is correct. A number of the jars for building the zxJDBC
extensions but are not required for running Jython unless you either
want them or are testing Jython for a release. I build and test them so
I'll know when they are broken. For the time being you can ignore them.
If the jars exist, then the classes dependent on them are compiled and
included in jython.jar, otherwise the build runs without them. For what
it's worth, IntelliJ has the same problem. It won't honor the build
file for a debugging session, so I build and run in bash and debug
>>What does the build do with them (shame on me: still haven't
>>got it working locally) ?
> If your asking does the build script copy these jars to dist
> (or anywhere), NAFAICT. build.xml doesn't even seem to know they
> exist, only eclipse does.
The dist target in build.xml doesn't use the jars.