From: Jeff A. <ja...@fa...> - 2016-07-11 09:07:13
|
Hi Isaiah, I'm using Eclipse (and mostly on Windows), so this is likely to be different for you, however ... Jython-the-program has always run very badly for me under the IDE: I just don't seem to be able to give it the environment it needs, and console I/O is a basket case. I always run Jython at the command prompt. If I need to single-step the code, I use remote debugging. JUnit tests, on the other hand, work brilliantly under the IDE, including debugging. The only niggle I commonly encounter is that to raise a PyException I have to create an instance of the interpreter (static PythonInterpreter interp = new PythonInterpreter(); ) in my test fixture. Finding the built-in types uninitialised is, for me, a symptom of having the build path in the wrong order. In some circumstances (debugging exposed classes, and between "clean" and "build", I think) one has to have the ~/src directory first, but this then means that when loading classes, the JVM finds the unexposed version of the class instead of the exposed one -- not that ~/src contains any classes, but I think Eclipse helpfully finds them. So mostly I have the ~/exposed directory first, and ensure "expose" has run on the latest source. Now if you're actually testing the exposer ... that seems likely to add a whole new layer of confusion, but I hope some of the above helps. Jeff Jeff Allen On 08/07/2016 10:15, Isaiah Peng wrote: > Hi Guys, > > When run the java tests with intellij, it fails initialize the > PySystemState in the setup phrase, digged a bit, I think that the > exposed types are not correctly instrumented. The same test runs with > the ant task: > > ant singlejavatest -DExposedTypeProcessorTest > > I've added the `ant expose` task to intellij run configuration, but it > doesn't make any difference. > > Not sure if it is even possible to run the tests in IDE, do you have > any suggestions? > > Best, > Isaiah > |