lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3774) check-legal isn't doing its job
Date Sun, 12 Feb 2012 22:12:59 GMT


Steven Rowe commented on LUCENE-3774:

Timings for me under Ant 1.7.1:

     [echo] License check under: C:\cygwin\home\s\svn\lucene\dev\trunk\lucene
 [licenses] Scanned 7 JAR file(s) for licenses (in 0.79s.), 0 error(s).

     [echo] License check under: C:\cygwin\home\s\svn\lucene\dev\trunk\modules
 [licenses] Scanned 11 JAR file(s) for licenses (in 1.38s.), 0 error(s).


     [echo] License check under: C:\cygwin\home\s\svn\lucene\dev\trunk\solr
 [licenses] Scanned 73 JAR file(s) for licenses (in 1.37s.), 1 error(s).
> check-legal isn't doing its job
> -------------------------------
>                 Key: LUCENE-3774
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 3.6, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>         Attachments: 3774.patch, LUCENE-3774.patch, LUCENE-3774.patch, LUCENE-3774.patch,
> In trunk, the {{check-legal-lucene}} ant target is not checking any {{lucene/contrib/\*\*/lib/}}
directories; the {{modules/**/lib/}} directories are not being checked; and {{check-legal-solr}}
can't be checking {{solr/example/lib/\*\*/\*.jar}}, because there are currently {{.jar}} files
in there that don't have a license.
> These targets are set up to take in a full list of {{lib/}} directories in which to check,
but modules move around, and these lists are not being kept up-to-date.
> Instead, {{check-legal-\*}} should run for each module, if the module has a {{lib/}}
directory, and it should be specialized for modules that have more than one ({{solr/core/}})
or that have a {{lib/}} directory in a non-standard place ({{lucene/core/}}).

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