lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Updated: (LUCENE-2894) Use of google-code-prettify for Lucene/Solr Javadoc
Date Fri, 18 Mar 2011 11:50:29 GMT


Robert Muir updated LUCENE-2894:

    Priority: Blocker  (was: Minor)

setting to blocker, i don't think the prettify directory should be in dev-tools as it breaks
the lucene-only build.

dev-tools was just supposed to be some developer-only/maintained on as-is/optional stuff to
help developers.

in this case i would recommend moving the prettify stuff to under lucene/

> Use of google-code-prettify for Lucene/Solr Javadoc
> ---------------------------------------------------
>                 Key: LUCENE-2894
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Javadocs
>            Reporter: Koji Sekiguchi
>            Assignee: Koji Sekiguchi
>            Priority: Blocker
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-2894-solr-analysis-AtoC.patch, LUCENE-2894-solr-analysis-DtoH.patch,
LUCENE-2894-solr-analysis-ItoN.patch, LUCENE-2894-solr-analysis-OtoR.patch, LUCENE-2894-solr-analysis-StoZ.patch,
LUCENE-2894.patch, LUCENE-2894.patch, LUCENE-2894.patch, LUCENE-2894.patch, LUCENE-2894.patch,
> My company, RONDHUIT uses google-code-prettify (Apache License 2.0) in Javadoc for syntax
> I think we can use it for Lucene javadoc (java sample code in overview.html etc) and
Solr javadoc (Analyzer Factories etc) to improve or simplify our life.

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