Thanks for confirming, just to be clear - the module descriptor
shouldn't affect the existing (in-module) tests, you can run them with
a debugger with IDEs.
Problems can happen when running the inter-module tests via IDE (we
have three, lucene/core.tests, lucene/analysis.tests, and
Welcome, Lu.
On Wed, Jun 1, 2022 at 12:59 PM 陆徐刚 wrote:
> Thanks Adrien for the announcement and all for the welcome! It’s a great
> honor for me be a Lucene committer.
>
> I live in ShangHai, China and work at EOI company which focus on AIOps.
> Thanks to Lucene such a great project which
Welcome, Chirs!
On Wed, Jun 1, 2022 at 10:29 AM Chris Hegarty
wrote:
> Hi,
>
> I am both honoured and humbled to have been invited to become a committer.
> Thank you.
>
> I've been working on the development of the Java Platform and the JDK for
> a little more than 20 years. First in the
[
https://issues.apache.org/jira/browse/PYLUCENE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17545615#comment-17545615
]
Andi Vajda commented on PYLUCENE-64:
I believe there is an issue with running 'make test' in
I was able to run tests in IDEA by removing all the module-info.jar,
so indeed, seems to be some kind of interaction with modules
On Thu, Jun 2, 2022 at 11:36 AM Tomoko Uchida
wrote:
>
> Yes I agree with there may be bugs (I couldn't find the corresponding
> issue in IDEA's issue tracker), they
Yes I agree with there may be bugs (I couldn't find the corresponding
issue in IDEA's issue tracker), they are just not our bugs...
2022年6月3日(金) 0:17 Michael Sokolov :
>
> glad to know I'm not the only one! I think it's not OK though. Running
> tests in IDE is super useful, especially for
glad to know I'm not the only one! I think it's not OK though. Running
tests in IDE is super useful, especially for debugging, but also for
visualizing coverage. I think there must be a bug; we do say:
11:15 $ ./gradlew helpIDEs
> Task :helpIDEs
IntelliJ IDEA
=
Importing the
Hi Mike,
I also can't run the tests in lucene/core.tests with IntelliJ IDEA,
but it should be able to run with the plain gradle command from a
console.
./gradlew -p lucene/core.tests/ test
I'm not sure the exact cause of that though IDEs' java module support
looks far from perfect for now, I
In IntelliJ building Lucene main branch I see this:
.../workspace/lucene/lucene/core.tests/src/test/module-info.java:23:
error: module not found: org.apache.lucene.core.tests.main
requires org.apache.lucene.core.tests.main;
^
Am I doing it wrong? Does
Hi Mike,
I found a new issue in Solr SQL (SOLR-16227) and have a fix for it (
https://github.com/apache/solr/pull/887). Can you wait on the release for
8.11.2 till I can backport this?
Thank you,
Kiran.
On Tue, May 31, 2022 at 9:21 AM Mike Drob wrote:
> Howdy folks, now that Lucene 9.2 has
[
https://issues.apache.org/jira/browse/PYLUCENE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
anis amirouche updated PYLUCENE-64:
---
Description:
I'm trying to install Pylucene 8.11.0 on mac os. the jcc is built and
anis amirouche created PYLUCENE-64:
--
Summary: ModuleNotFoundError: No module named 'lucene' when
intalling PyLucene
Key: PYLUCENE-64
URL: https://issues.apache.org/jira/browse/PYLUCENE-64
Project:
Hi all,
Just a minor heads-up.
We will have a more fine-grained Java version check when starting
gradlew command shortly.
After PR #941 is merged into main, you need newer Java (17.0.3) for a build.
2022年5月18日(水) 19:00 Tomoko Uchida :
>
> Hi, I just wanted to note that I opened LUCENE-10578.
>
13 matches
Mail list logo
