lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
Date Thu, 14 Apr 2011 16:01:06 GMT


Steven Rowe commented on LUCENE-3018:

bq. I should have named it cpptasks-1.0b4.jar

Did you use 1.0-beta4 (dated 2006) instead of 1.0-beta5 (dated 2008; the most recent version
AFAICT) simply because 1.0-beta4 includes a precompiled jar and 1.0-beta5 does not?  IMHO
you should compile 1.0-beta5 and include it instead.

bq. Should I upload the LICENSE file which came with it ?

Yes.  Our build will fail if a jar without a LICENSE file is included in the source tree.
 The LICENSE file naming requirement is spelled out on the Lucene wiki at

> Lucene Native Directory implementation need automated build
> -----------------------------------------------------------
>                 Key: LUCENE-3018
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Wish
>          Components: Build
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Assignee: Varun Thacker
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar
> Currently the native directory impl in contrib/misc require manual action to compile
the c code (partially) documented in 
> yet it would be nice if we had an ant task and documentation for all platforms how to
compile them and set up the prerequisites.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message