[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13009240#comment-13009240 ] Yonik Seeley commented on LUCENE-2894: -- bq. Do you mean Solr javadocs see the prettify stuff under lucene/ also? Yep, seems reasonable. > 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: 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, 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] Commented: (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:comment-tabpanel&focusedCommentId=13008433#comment-13008433 ] Koji Sekiguchi commented on LUCENE-2894: bq. in this case i would recommend moving the prettify stuff to under lucene/ Do you mean Solr javadocs see the prettify stuff under lucene/ also? (Sorry if I missed something in community these days.) > 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: 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, 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] Commented: (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:comment-tabpanel&focusedCommentId=12998859#comment-12998859 ] Koji Sekiguchi commented on LUCENE-2894: Sounds reasonable, thanks for reviewing and correcting them, Robert! Please commit the patch. > 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 > > > 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] Commented: (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:comment-tabpanel&focusedCommentId=12998671#comment-12998671 ] Koji Sekiguchi commented on LUCENE-2894: Committed O-to-R in r1074017 (trunk) and r1074023 (3x). Abe-san, ReversedWildcardFilterFactory should be applied only index time analysis, I've fixed your patch. Please see schema.xml for example. Thanks anyway for your great contribution! > 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 > > > 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] Commented: (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:comment-tabpanel&focusedCommentId=12998660#comment-12998660 ] Koji Sekiguchi commented on LUCENE-2894: Committed S-to-Z in r1074009 (trunk) and r1074011 (3x). > 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 > > > 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] Commented: (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:comment-tabpanel&focusedCommentId=12998433#comment-12998433 ] Koji Sekiguchi commented on LUCENE-2894: bq. This is a really great start towards improving the documentation in this area. I agree. I've committed I-to-N in r1073806 (trunk) and r1073810 (3x). I'll check and commit the rest of patches tomorrow. Thanks again, Abe-san! > 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 > > > 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] Commented: (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:comment-tabpanel&focusedCommentId=12998357#comment-12998357
]
Robert Muir commented on LUCENE-2894:
-
{quote}
Solr.analysis classes(I to Z) have been implemented by google-code-prettify.
{quote}
I just wanted to say thank you for adding these examples to all of the analysis
factories!
This is a really great start towards improving the documentation in this area.
> 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
>
>
> 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] Commented: (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:comment-tabpanel&focusedCommentId=12997822#comment-12997822 ] Koji Sekiguchi commented on LUCENE-2894: bq. solr.analysis classes(A to H) are implemented by google-code-prettify.Please confirm the patch. trunk: Committed revision 1073336. 3x: Committed revision 1073344. > 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.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] Commented: (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:comment-tabpanel&focusedCommentId=12997622#comment-12997622 ] Koji Sekiguchi commented on LUCENE-2894: Looks fine. Thanks, Abe-san! I'll look into them and commit tonight. > 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.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] Commented: (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:comment-tabpanel&focusedCommentId=12994759#comment-12994759
]
Koji Sekiguchi commented on LUCENE-2894:
{quote}
but Solr javadoc on hudson looks not good:
https://hudson.apache.org/hudson/job/Solr-trunk/javadoc/org/apache/solr/handler/component/TermsComponent.html
{quote}
The problem was gone.
> 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
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12991173#comment-12991173 ] Steven Rowe commented on LUCENE-2894: - Both of the nightly Hudson Maven builds failed because javadoc jars were not produced by the Ant build (scroll down to the bottom to see the error about javadoc jars not being available to deploy): https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-trunk/17/consoleText https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-3.x/16/consoleText > 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
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12991165#comment-12991165
]
Koji Sekiguchi commented on LUCENE-2894:
On my mac, there is prettify correctly under api directory after ant package:
{code}
$ cd solr
$ ant clean set-fsdir package
$ ls build/docs/api/
allclasses-frame.html deprecated-list.html package-list
allclasses-noframe.htmlhelp-doc.html prettify
constant-values.html index-all.html resources
contrib-solr-analysis-extras index.html
serialized-form.html
contrib-solr-cell orgsolr
contrib-solr-clusteringoverview-frame.htmlsolrj
contrib-solr-dataimporthandler overview-summary.html
stylesheet+prettify.css
contrib-solr-uima overview-tree.html
{code}
> 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
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12989704#comment-12989704 ] Koji Sekiguchi commented on LUCENE-2894: TODO: - Support not only javadoc-core, but also javadoc-solrj, javadoc-all, javadoc-contrib. They should share a common prettify. - Support lucene javadocs. - Support modules javadocs? > 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 > > Attachments: 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] Commented: (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: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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12989503#comment-12989503
]
Koji Sekiguchi commented on LUCENE-2894:
bq. on a related note maybe this would encourage us to add more examples to our
javadocs, which I think is really helpful for users.
I agree.
bq. Any idea what it takes to integrate this with an ant task for javadocs?
Nothing special at this moment. So the author of javadoc should know where
prettify script is:
{code}
{code}
He should write it in another javadoc:
{code}
{code}
I don't like it...
(where prettify.js needs to be copied from somewhere (dev-tools? for example)
to output dir of javadoc by ant task.)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12989005#comment-12989005 ] Robert Muir commented on LUCENE-2894: - I like this idea: on a related note maybe this would encourage us to add more examples to our javadocs, which I think is really helpful for users. Any idea what it takes to integrate this with an ant task for javadocs? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
