Alexandre Rafalovitch a57ba25400
SOLR-14783: Remove DIH from 9.0 (#1794)
* Remove DIH example directory

* Remove contrib code directories

* Remove contrib package related configurations for build tools

* Remove mention of DIH example

* remove dih as build dependencies and no-longer needed version pins

* Remove README references to DIH

* Remove dih mention from the script that probably does need to exist at all

* More build artifact references

* More removed dependencies leftovers (licenses/versions)

* No need to smoke exclude DIH anymore

* Remove Admin UI's DIH integration

* Remove DIH from shortname package list

* Remove unused DIH (related? not?) dataset
Unclear what is happening here, but there is no reference to that directory anywhere else
The other parallel directories ARE referenced in a TestConfigSetsAPI.java

* Hidden Idea files references

* No DIH to ignore anymore

* Remove last Derby DB references

* Remove DIH from documentation
Add the information in Major Changes document with the link to the external repo

* Added/updated a mention to CHANGES

* Fix leftover library mentions

* Fix Spellings
2020-08-29 10:52:04 -04:00
..
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2013-03-04 11:01:32 +00:00
2013-03-04 11:01:32 +00:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00
2017-01-29 12:18:34 -05:00

         --------------------------
         Information For Committers
         --------------------------

Under no circumstances should any new files be added to this directory
without careful consideration of how LICENSE.txt and NOTICE.txt in the
parent directory should be updated to reflect the addition. 

Even if a Jar being added is from another Apache project, it should be
mentioned in NOTICE.txt, and may have additional Attribution or
Licencing information that also needs to be added to the appropriate
file.  

---

If an existing Jar is replaced with a newer version, the same
consideration should be given as if it were an entirely new file:
verify that no updates need to be made to LICENSE.txt or NOTICE.txt
based on changes in the terms of the dependency being updated. 

---

When adding a jar or updating an existing jar, be sure to include/update 
xyz-LICENSE.txt and if applicable, xyz-NOTICE.txt.  These files often
change across versions of the dependency, so when updating be SURE to 
update them to the recent version. This also allows others to see
what changed with respect to licensing in the commit diff.

---

Any changes made to this directory should be noted in CHANGES.txt,
along with the specific version information.  If the version is a
"snapshot" of another Apache project, include the SVN revision number.

---

When upgrading Lucene-Java Jars, remember to generate new Analysis
factories for any new Tokenizers or TokenFilters.  See the wiki for
details...

  http://wiki.apache.org/solr/CommitterInfo