You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Erick Erickson <er...@gmail.com> on 2014/11/16 23:15:23 UTC
I think LUCENE-5929 broke the ability to run unit tests in IntelliJ
At least every time I try to run a unit test, these two imports (and
of course the references) are undefined:
import org.apache.lucene.search.join.ToChildBlockJoinQuery;
import org.apache.lucene.search.join.ToParentBlockJoinQuery;
If I hack
<orderEntry type="module" module-name="join" />
into highlighter.iml it fixes things up. So my question is, I suppose,
whether this is the right fix.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: I think LUCENE-5929 broke the ability to run unit tests in IntelliJ
Posted by Steve Rowe <sa...@gmail.com>.
+1 for the highlighter.iml change, benchmark.iml needs it too.
Steve
> On Nov 16, 2014, at 7:15 PM, Erick Erickson <er...@gmail.com> wrote:
>
> Michael:
>
> NP, I need to understand the build/IDE world better...
>
> I'll wait until tomorrow probably and give folks like Steve a chance
> to weigh in.
>
> Erick
>
> On Sun, Nov 16, 2014 at 2:44 PM, Michael McCandless
> <lu...@mikemccandless.com> wrote:
>> Oh sorry this could very well be! I had to add a dep in highlighter's
>> build.xml on join (and also in benchmark's build.xml), but I don't run
>> IDEA so I'm not sure how to fix/test this ... I think if that fixes it
>> for you then commit away :)
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>> On Sun, Nov 16, 2014 at 5:15 PM, Erick Erickson <er...@gmail.com> wrote:
>>> At least every time I try to run a unit test, these two imports (and
>>> of course the references) are undefined:
>>>
>>> import org.apache.lucene.search.join.ToChildBlockJoinQuery;
>>> import org.apache.lucene.search.join.ToParentBlockJoinQuery;
>>>
>>>
>>> If I hack
>>> <orderEntry type="module" module-name="join" />
>>> into highlighter.iml it fixes things up. So my question is, I suppose,
>>> whether this is the right fix.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: I think LUCENE-5929 broke the ability to run unit tests in IntelliJ
Posted by Erick Erickson <er...@gmail.com>.
Michael:
NP, I need to understand the build/IDE world better...
I'll wait until tomorrow probably and give folks like Steve a chance
to weigh in.
Erick
On Sun, Nov 16, 2014 at 2:44 PM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> Oh sorry this could very well be! I had to add a dep in highlighter's
> build.xml on join (and also in benchmark's build.xml), but I don't run
> IDEA so I'm not sure how to fix/test this ... I think if that fixes it
> for you then commit away :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Nov 16, 2014 at 5:15 PM, Erick Erickson <er...@gmail.com> wrote:
>> At least every time I try to run a unit test, these two imports (and
>> of course the references) are undefined:
>>
>> import org.apache.lucene.search.join.ToChildBlockJoinQuery;
>> import org.apache.lucene.search.join.ToParentBlockJoinQuery;
>>
>>
>> If I hack
>> <orderEntry type="module" module-name="join" />
>> into highlighter.iml it fixes things up. So my question is, I suppose,
>> whether this is the right fix.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: I think LUCENE-5929 broke the ability to run unit tests in IntelliJ
Posted by Michael McCandless <lu...@mikemccandless.com>.
Oh sorry this could very well be! I had to add a dep in highlighter's
build.xml on join (and also in benchmark's build.xml), but I don't run
IDEA so I'm not sure how to fix/test this ... I think if that fixes it
for you then commit away :)
Mike McCandless
http://blog.mikemccandless.com
On Sun, Nov 16, 2014 at 5:15 PM, Erick Erickson <er...@gmail.com> wrote:
> At least every time I try to run a unit test, these two imports (and
> of course the references) are undefined:
>
> import org.apache.lucene.search.join.ToChildBlockJoinQuery;
> import org.apache.lucene.search.join.ToParentBlockJoinQuery;
>
>
> If I hack
> <orderEntry type="module" module-name="join" />
> into highlighter.iml it fixes things up. So my question is, I suppose,
> whether this is the right fix.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org