[jira] [Commented] (PYLUCENE-28) JCC reuses JVM instances in impl, if compile() is called twice.

2023-06-25 Thread Andi Vajda (Jira)
[ https://issues.apache.org/jira/browse/PYLUCENE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736851#comment-17736851 ] Andi Vajda commented on PYLUCENE-28: I see 2 things:   - if a constructor takes no

Re: [jira] [Commented] (PYLUCENE-28) JCC reuses JVM instances in impl, if compile() is called twice.

2013-12-18 Thread Andi Vajda
On Wed, 18 Dec 2013, Martin Scherer wrote: Hi Andi, do you suppose that adding to the classpath by runtime is possible via python or a java workaround? You can see the horrible kludge implemented in JCCEnv::setClassPath(). It is possible to modify the classpath at runtime. I think it is ve

Re: [jira] [Commented] (PYLUCENE-28) JCC reuses JVM instances in impl, if compile() is called twice.

2013-12-18 Thread Martin Scherer
Hi, I've implemented your second suggestion and made the env an optional parameter to the jcc function. In addition there are performed some checks for classpath and vmargs for sanity. This fixes the silent failure, when a different classpath should be used. I didn't figure out, how to add dynami

Re: [jira] [Commented] (PYLUCENE-28) JCC reuses JVM instances in impl, if compile() is called twice.

2013-12-18 Thread Martin Scherer
Hi Andi, do you suppose that adding to the classpath by runtime is possible via python or a java workaround? I think it is very error prone if the user has to maintain his own classpath and can not rely on jcc. Best, Martin Am 04.11.2013 16:02, schrieb Andi Vajda (JIRA): > > [ > https://