[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019880#comment-13019880
]
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 http://wiki.apache.org/lucene-java/Validation.
> Lucene Native Directory implementation need automated build
> -----------------------------------------------------------
>
> Key: LUCENE-3018
> URL: https://issues.apache.org/jira/browse/LUCENE-3018
> 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
>
> https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
