2023 07:07 PM
> *To:* external-opensource-requests(mailer list) <
> external-opensource-reque...@cisco.com>
> *Cc:* java-user@lucene.apache.org
> *Subject:* Re: Info required on licensing of Lucene component
>
>
>
> Thank you Mike S for adding the 9.6.0 Milestone tag to the issue!
@lucene.apache.org
Subject: Re: Info required on licensing of Lucene component
Thank you Mike S for adding the 9.6.0 Milestone tag to the issue!
I wonder if we are able to close an issue AND attach a milestone label in a
commit message? I tried to research a bit and didn't find anything except all
gt;>
>> Thanks,
>>
>> Open Source Request Team
>>
>>
>>
>>
>>
>> *From:* Michael McCandless
>> *Sent:* 06 April 2023 03:39 PM
>> *To:* java-user@lucene.apache.org; external-opensource-requests(mailer
>> list)
>> *Subjec
el McCandless
> *Sent:* 06 April 2023 03:39 PM
> *To:* java-user@lucene.apache.org; external-opensource-requests(mailer
> list)
> *Subject:* Re: Info required on licensing of Lucene component
>
>
>
> > In that case, can you’ll update your source repo for Lucene to exclude
&g
to?
Thanks,
Open Source Request Team
From: Michael McCandless
Sent: 06 April 2023 03:39 PM
To: java-user@lucene.apache.org; external-opensource-requests(mailer list)
Subject: Re: Info required on licensing of Lucene component
> In that case, can you’ll update your source repo for Lucene
Thank you, Michael. This will definitely help.
Thanks,
Open Source Request Team
From: Michael McCandless
Sent: 06 April 2023 03:39 PM
To: java-user@lucene.apache.org; external-opensource-requests(mailer list)
Subject: Re: Info required on licensing of Lucene component
> In that case,
> In that case, can you’ll update your source repo for Lucene to exclude
references to ‘junit’ from Notices.txt file since it is something which is
not part of distribution for Lucene.
That sounds reasonable to me. I'll open an issue in our GitHub repo, but
IANAL and I'm not sure how to specifica
of distribution for Lucene.
Thanks,
Open Source Request Team
From: Michael McCandless
Sent: 04 April 2023 06:52 PM
To: java-user@lucene.apache.org
Cc: external-opensource-requests(mailer list)
Subject: Re: Info required on licensing of Lucene component
Hello,
You maybe missed the two
rnal-opensource-requests(mailer list)
> Sent: 21 March 2023 07:42 PM
> To: 'java-user@lucene.apache.org'
> Subject: Info required on licensing of Lucene component
>
> Hello Team
>
> I hope you are doing well!!
>
> This is regarding Lucene component licensing.
>
equired on licensing of Lucene component
Hello Team
I hope you are doing well!!
This is regarding Lucene component licensing.
The maven repo link
https://mvnrepository.com/artifact/org.apache.lucene/lucene-queries/4.10.4 for
lucene-queries 4.10.4 shows Apache 2.0 license associated with the compo
I suppose this begs the question, why are we including NOTICE.txt in our
distribution for *anything* we don't distribute?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Tue, Mar 21, 2023 at 7:57 PM Michael Sokolov wrote:
> Lucene is licensed under
Lucene is licensed under the Apache license, just as it says in the
LICENSE file. junit is used for testing Lucene and is not
redistributed with it. Using Lucene in your code does not mean you are
using junit, except in some extremely philosophical sense. EG Lucene
developers may have developed Luc
Hello Team
I hope you are doing well!!
This is regarding Lucene component licensing.
The maven repo link
https://mvnrepository.com/artifact/org.apache.lucene/lucene-queries/4.10.4 for
lucene-queries 4.10.4 shows Apache 2.0 license associated with the component.
Also, the archive (lucene-querie
13 matches
Mail list logo
