On Thu, 31 Jul 2008, Bill Janssen wrote:
On Thu, 24 Jul 2008, Andi Vajda wrote:
On Jul 24, 2008, at 2:04, Bill Janssen <[EMAIL PROTECTED]> wrote:
Well, I'm pretty sure the offending class is java.awt.BufferedImage.
Which, unfortunately, I need.
Better yet, find out what the offending class' name is and add it to
the command line with --exclude
OK, how? Should I add a print statement somewhere?
The stacktrace you sent in errors on findclass() called in cpp.py. That
function takes a classname. Put a try/except around this call and print the
classname in question.
If it's a class you need, then refer to the first reply in this thread. If
not, just exclude the class.
Out of curiosity, what did you end up doing to work around this issue ?
No workaround yet, I've just been busy with other things. The Web
seems to advise setting "java.awt.headless=true" when initializing the
JVM for JCC:
http://www.digitalsanctuary.com/tech-blog/java/eclipse-startonfirstthread-error-and-fix.html
I don't know if that will work.
Well, trying that is easier than playing threading tricks.
Can you try it by changing line 341 in cpp.py to say:
env = initVM(os.pathsep.join(classpath) or None,
vmargs='-Djava.awt.headless=true')
Thanks !
Andi..
_______________________________________________
pylucene-dev mailing list
pylucene-dev@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
