[SOLR-6703] Umbrella JIRA for improvements after restructuring directory layout.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0, 6.0
• Fix Version/s: 5.0
• Assignee: Timothy Potter
• Reporter: Erick Erickson
• Created: 04/Nov/14 15:35
• Updated: 01/Aug/17 17:05
• Resolved: 01/Aug/17 17:05

Description

After the new work to revamp how we lay out the Solr file structure and the scripts to start up SolrCloud, there is room for some polish. This is an umbrella JIRA for things we'd like to change.

Issue Links

• is related to: SOLR-3619 Rename 'example' dir to 'server' and pull examples into an 'examples' directory
• relates to: SOLR-7016 techproducts example does not start on windows with "solr.cmd -e techproducts" if install dir contains whitespace
• relates to: SOLR-6708 Smoke tester couldn't communicate with Solr started using 'bin/solr start'
• relates to: SOLR-6767 Improve user experience when starting Solr in standalone mode using scripts
• relates to: SOLR-6833 bin/solr -e foo should not use server/solr as the SOLR_HOME
• relates to: SOLR-6851 Scripts to help install and run Solr as a service on Linux
• relates to: SOLR-6848 Typing incorrect configuration name for cloud example aborts the script, leaves nodes running
• relates to: SOLR-6705 SOLR Start script generates warnings on java 8 due ot experimental options
• relates to: SOLR-6773 Remove the multicore example as the DIH and cloud examples illustrate multicore behavior
• relates to: SOLR-6867 bin/solr -e foo should use collection/cores api to check if collection/core exists before trying to create it
• relates to: SOLR-6778 Dead end UX when following README
• relates to: SOLR-6866 the collection created by "bin/solr -e schemaless" should be named "gettingstarted"
• relates to: SOLR-6726 Specifying different ports with the new bin/solr script fails to start solr instances
• relates to: SOLR-6474 Smoke tester should use the Solr start scripts to start Solr