[jira] Reopened: (LUCENE-2894) Use of google-code-prettify for Lucene/Solr Javadoc
[ https://issues.apache.org/jira/browse/LUCENE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir reopened LUCENE-2894: - reopen as the lucene-only javadocs are broken > 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, 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, LUCENE-2894.patch > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Reopened: (LUCENE-2894) Use of google-code-prettify for Lucene/Solr Javadoc
[ https://issues.apache.org/jira/browse/LUCENE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi reopened LUCENE-2894: Reopening the issue. Lucene javadoc on hudson looks fine (syntax highlighting works correctly): https://hudson.apache.org/hudson/job/Lucene-trunk/javadoc/all/overview-summary.html but Solr javadoc on hudson looks not good: https://hudson.apache.org/hudson/job/Solr-trunk/javadoc/org/apache/solr/handler/component/TermsComponent.html Building of both javadocs on my local is working fine. > 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, 4.0 > > Attachments: 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 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
