[
https://issues.apache.org/jira/browse/SOLR-17068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783319#comment-17783319
]
Chris M. Hostetter commented on SOLR-17068:
-------------------------------------------
This issue was created in specific response to this mailing list thread...
[https://lists.apache.org/thread/mfkf9sbdv16c9rbz6f2b81t3bw2rbvh1]
...but the Jira description/summary only addresses the topic of the ref-guide
containing references to {{bin/post}}
This seems to gloss over the bigger issue: We are still (as of 9.4) building a
{{post.jar}} that does contain the {{SimplePostTool.class}} and has
{{Main-Class}} pointing to a FQCN that doesn't exist in our code base -- making
it worse then useless.
* Bad: We really want people to use {{bin/solr post}} but some places in the
ref guide inconsistently suggest they use {{bin/post}}
** Slightly Worse: ... but they can't find {{bin/post}} in the distro so the
9hopefully) go hunting for other places in the refguide that talk about
{{post}} and find {{bin/solr post}} refrences
* Really Fucking bad: ... they **CAN** find {{bin/post}} in the distro but it
doesn't work, and gives an error about not being ableto find a class that it
will _never_ find no matter how much they change their classpath
> Migrate Ref Guide content to using bin/solr post command
> --------------------------------------------------------
>
> Key: SOLR-17068
> URL: https://issues.apache.org/jira/browse/SOLR-17068
> Project: Solr
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 9.4
> Reporter: Eric Pugh
> Priority: Minor
>
> The Ref Guide has many references to the old bin/post command (and it's
> sibling awkward windows version) while ALSO having bin/solr post commands.
> We need to finish the migration to bin/solr post so we don't have a awkward
> split of both approaches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
