Ryan McKinley 3c9db8e311 SOLR-560: Use SLF4J logging API rather then JDK logging. The packaged .war file is
shipped with a JDK logging implementation, so logging configuration for the .war should
    be identical to solr 1.3.  However, if you are using the .jar file, you can select 
    which logging implementation to use by dropping a different binding.  
    See: http://www.slf4j.org/  

git-svn-id: https://svn.apache.org/repos/asf/lucene/solr/trunk@696539 13f79535-47bb-0310-9956-ffa450edef68
2008-09-18 02:16:26 +00: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. 

---

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