[ 
https://issues.apache.org/jira/browse/LUCENE-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046484#comment-15046484
 ] 

Uwe Schindler commented on LUCENE-6917:
---------------------------------------

bq. I could not get @link out to backward-codecs to render correctly into 
javadocs ... so I had to cutover to @code for links outside of core.

In modules you have to add {{<link>}} elements inside {{<links/>}} of the 
{{<invoke-module-javadoc>}} Ant element. Example from benchmark module:
{code:xml}
    <invoke-module-javadoc>
      <links>
        <link href="../memory"/>
        <link href="../highlighter"/>
        <link href="../analyzers-common"/>
        <link href="../queryparser"/>
        <link href="../facet"/>
        <link href="../spatial"/>
      </links>
    </invoke-module-javadoc>
{code}

If the javadoc target does not exist, you have to add it first.

> Move NumericField out of core to backwards-codecs
> -------------------------------------------------
>
>                 Key: LUCENE-6917
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6917
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 6.0
>
>         Attachments: LUCENE-6917.patch, LUCENE-6917.patch
>
>
> DimensionalValues seems to be better across the board (indexing time, 
> indexing size, search-speed, search-time heap required) than NumericField, at 
> least in my testing so far.
> I think for 6.0 we should move {{IntField}}, {{LongField}}, {{FloatField}}, 
> {{DoubleField}} and {{NumericRangeQuery}} to {{backward-codecs}}, and rename 
> with {{Legacy}} prefix?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to