lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3331) solr NOTICE.txt is missing information
Date Fri, 06 Apr 2012 13:21:22 GMT


Robert Muir commented on SOLR-3331:

Thanks also for the changes.

I'm going to commit this to fix licensing.

Note: the solr example test is going to be broken on windows,
but thats ok, the smoketester is just a tool and is not part of the release
(bugs in it cannot block releases).
> solr NOTICE.txt is missing information
> --------------------------------------
>                 Key: SOLR-3331
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Michael McCandless
>            Priority: Blocker
>             Fix For: 3.6
>         Attachments: SOLR-3331.patch, SOLR-3331.patch
> Solr depends on some modules from lucene, and is released separately (as a source release
including lucene),
> thus its NOTICE.txt has a lucene section which includes notices from lucene:
> {noformat}
> =========================================================================
> ==  Apache Lucene Notice                                               ==
> =========================================================================
> {noformat}
> however, its missing the IPADIC (which is required to be there).
> Furthermore, there is no way to check this, except via manual inspection.
> This gets complicated in 4.0 because of modularization, but we need to fix the
> 3.6 situation in order to release (hence, this issue is set to 3.6 only and
> we can open a separate issue for 4.0 and discuss things like modules there,
> its irrelevant here).
> My proposal for *3.6* is:
> 1. add the IPADIC notice
> 2. have look for this specific block of text indicating
>    the notices from lucene, and cross check them to ensure everything is consistent.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message