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

Karl Richter commented on SOLR-11032:
-------------------------------------

> And we should probably move it to the ref-guide too. Or would the SolrJ 
> tutorial work better as a GitHub repo with multiple examples that you could 
> run, study, modify, copy/paste?

Can't it be both? Maintaining documentation resources outside the code is 
painful (and maybe therefore didn't happen for 5 years in this afaik), so it 
should be easy to contribute and there's no easier way than PRs. However, if 
it's a plain project that one has to build with tools with different 
installation routines on different OS (which is what a GitHub tutorial is in my 
understanding), then maintenance need and user frustration might increase. 
Consequently, an automatically built and updated version in form of HTML should 
be provided in the ref-guide and the maintenance occur on GitHub.

> Update solrj tutorial
> ---------------------
>
>                 Key: SOLR-11032
>                 URL: https://issues.apache.org/jira/browse/SOLR-11032
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation, SolrJ, website
>            Reporter: Karl Richter
>
> The [solrj tutorial](https://wiki.apache.org/solr/Solrj) has the following 
> issues:
>   * It refers to 1.4.0 whereas the current release is 6.x, some classes are 
> deprecated or no longer exist.
>   * Document-object-binding is a crucial feature [which should be working in 
> the meantime](https://issues.apache.org/jira/browse/SOLR-1945) and thus 
> should be covered in the tutorial.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to