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 13:52:06 GMT


Steven Rowe commented on LUCENE-3018:

When {{cpptasks.jar}} is committed to the Lucene source tree, it should have a version number
included in its name.  E.g., if the jar was built from the 1.0b5 sources, the committed jar
should be named {{cpptasks-1.0b5.jar}}.  

Varun, where did you get the {{cpptasks.jar}} from?  If you build it yourself, please use
a Java 1.5 JDK, to insure it will be compatible with 1.5 JVMs.

> 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, 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