[
https://issues.apache.org/jira/browse/LUCENE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989514#comment-12989514
]
Hoss Man commented on LUCENE-2894:
----------------------------------
could probably solve this in the general case using a combination of javadocs
"-header" option, combined with the "{@docRoot}" macro, and putting the JS file
in doc-files at the project root...
http://download.oracle.com/javase/1.4.2/docs/tooldocs/windows/javadoc.html#header
http://download.oracle.com/javase/1.4.2/docs/tooldocs/windows/javadoc.html#{@docRoot}
http://download.oracle.com/javase/1.4.2/docs/tooldocs/windows/javadoc.html#unprocessed
...then it should be available in every generated HTML file
> Use of google-code-prettify for Lucene/Solr Javadoc
> ---------------------------------------------------
>
> Key: LUCENE-2894
> URL: https://issues.apache.org/jira/browse/LUCENE-2894
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Koji Sekiguchi
> Assignee: Koji Sekiguchi
> Priority: Minor
> Fix For: 3.1
>
>
> My company, RONDHUIT uses google-code-prettify (Apache License 2.0) in
> Javadoc for syntax highlighting:
> http://www.rondhuit-demo.com/RCSS/api/com/rondhuit/solr/analysis/JaReadingSynonymFilterFactory.html
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
