[
https://issues.apache.org/jira/browse/PYLUCENE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361765#comment-16361765
]
Ryan J Ollos commented on PYLUCENE-40:
--
Yes, typo, should be {{JCC_JDK}}. The issue is about
[
https://issues.apache.org/jira/browse/PYLUCENE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361762#comment-16361762
]
Andi Vajda commented on PYLUCENE-40:
Similarly for JAVAC: if you don't set it, it'll pickup
[
https://issues.apache.org/jira/browse/PYLUCENE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361761#comment-16361761
]
Andi Vajda commented on PYLUCENE-40:
Note, that, as the code is currently, if you *only* set JCC_JDK
Ryan J Ollos created PYLUCENE-40:
Summary: Document use of JCC_JDK
Key: PYLUCENE-40
URL: https://issues.apache.org/jira/browse/PYLUCENE-40
Project: PyLucene
Issue Type: Improvement
> On Feb 12, 2018, at 12:09, Milo H. Fields III wrote:
>
> No worries
> -- we are testing pylucene against original delivery in Windows, RHEL7 and
> CentOS 7 as we support these platforms and have started integration of
> pylucene & lucene/tika into our business
> On Feb 12, 2018, at 12:09, Milo H. Fields III wrote:
>
> No worries
> -- we are testing pylucene against original delivery in Windows, RHEL7 and
> CentOS 7 as we support these platforms and have started integration of
> pylucene & lucene/tika into our business
No worries
-- we are testing pylucene against original delivery in Windows, RHEL7 and
CentOS 7 as we support these platforms and have started integration of pylucene
& lucene/tika into our business logic/CIE systems..
We target python3 but I will make sure the changes can be reflected in the
> On Feb 12, 2018, at 09:33, Milo H. Fields III wrote:
>
> Andi,
> I have integrated PyLucene into a Visual Studio 2017 project space including
> support for VS Python unit test fixture (AKA Test Explorer) and other IDE
> platforms we use that instrument the unit test
Andi,
I have integrated PyLucene into a Visual Studio 2017 project space including
support for VS Python unit test fixture (AKA Test Explorer) and other IDE
platforms we use that instrument the unit test sets. This required some minor
tweaking to the test classes to support running the test