You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by bu...@apache.org on 2012/04/19 16:21:15 UTC
svn commit: r813652 - in /websites: production/lucene/content/
production/lucene/content/core/ production/lucene/content/solr/
staging/lucene/trunk/content/ staging/lucene/trunk/content/core/
staging/lucene/trunk/content/solr/
Author: buildbot
Date: Thu Apr 19 14:21:15 2012
New Revision: 813652
Log:
Dynamic update by buildbot for lucene
Modified:
websites/production/lucene/content/core/index.html
websites/production/lucene/content/index.html
websites/production/lucene/content/solr/index.html
websites/staging/lucene/trunk/content/core/index.html
websites/staging/lucene/trunk/content/index.html
websites/staging/lucene/trunk/content/solr/index.html
Modified: websites/production/lucene/content/core/index.html
==============================================================================
(empty)
Modified: websites/production/lucene/content/index.html
==============================================================================
(empty)
Modified: websites/production/lucene/content/solr/index.html
==============================================================================
--- websites/production/lucene/content/solr/index.html (original)
+++ websites/production/lucene/content/solr/index.html Thu Apr 19 14:21:15 2012
@@ -438,15 +438,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/girllostinit/statuses/192946971533778945">@</a>explain the <a href="http://twitter.com/search?q=%23ApacheLucene">#ApacheLucene</a> case to me. everybody uses it. API documentation sucks. no recent books (a bit better with <a href="http://twitter.com/search?q=%23Solr).">#Solr).</a> why??
+ <a href="http://twitter.com/levyrecruits/statuses/192979706965000192">@</a>Hiring a Sr <a href="http://twitter.com/Java">@Java</a> Engineer <a href="http://twitter.com/TheLadders">@TheLadders</a> <a href="http://twitter.com/search?q=%23NYC">#NYC</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23scala">#scala</a> in New York, NY <a href="http://t.co/uDQkfydP">http://t.co/uDQkfydP</a> <a href="http://twitter.com/search?q=%23job">#job</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/dadoonet/statuses/192943897272516609">@</a><a href="http://twitter.com/plombard_00">@plombard_00</a> <a href="http://twitter.com/__jro">@__jro</a> non mais <a href="http://twitter.com/search?q=%23lucene">#lucene</a> qui est aussi utilisé dans <a href="http://twitter.com/search?q=%23solr">#solr</a>
+ <a href="http://twitter.com/sematext/statuses/192979706734329858">@</a><a href="http://twitter.com/Hiring">Hiring</a>: Search Engineer Lead: Solr, ElasticSearch, Lucene, lead dev/consulting team <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://t.co/9B2L6qQW">http://t.co/9B2L6qQW</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/TheMalloum/statuses/192916174852464640">@</a>RT <a href="http://twitter.com/olamy">@olamy</a>: <a href="http://twitter.com/dadoonet">@dadoonet</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23Devoxxfr">#Devoxxfr</a> nice talk. question : différences avec <a href="http://twitter.com/search?q=%23solr">#solr</a> ?
+ <a href="http://twitter.com/girllostinit/statuses/192946971533778945">@</a>explain the <a href="http://twitter.com/search?q=%23ApacheLucene">#ApacheLucene</a> case to me. everybody uses it. API documentation sucks. no recent books (a bit better with <a href="http://twitter.com/search?q=%23Solr).">#Solr).</a> why??
</div>
</div>
Modified: websites/staging/lucene/trunk/content/core/index.html
==============================================================================
(empty)
Modified: websites/staging/lucene/trunk/content/index.html
==============================================================================
(empty)
Modified: websites/staging/lucene/trunk/content/solr/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/index.html (original)
+++ websites/staging/lucene/trunk/content/solr/index.html Thu Apr 19 14:21:15 2012
@@ -438,15 +438,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/girllostinit/statuses/192946971533778945">@</a>explain the <a href="http://twitter.com/search?q=%23ApacheLucene">#ApacheLucene</a> case to me. everybody uses it. API documentation sucks. no recent books (a bit better with <a href="http://twitter.com/search?q=%23Solr).">#Solr).</a> why??
+ <a href="http://twitter.com/levyrecruits/statuses/192979706965000192">@</a>Hiring a Sr <a href="http://twitter.com/Java">@Java</a> Engineer <a href="http://twitter.com/TheLadders">@TheLadders</a> <a href="http://twitter.com/search?q=%23NYC">#NYC</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23scala">#scala</a> in New York, NY <a href="http://t.co/uDQkfydP">http://t.co/uDQkfydP</a> <a href="http://twitter.com/search?q=%23job">#job</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/dadoonet/statuses/192943897272516609">@</a><a href="http://twitter.com/plombard_00">@plombard_00</a> <a href="http://twitter.com/__jro">@__jro</a> non mais <a href="http://twitter.com/search?q=%23lucene">#lucene</a> qui est aussi utilisé dans <a href="http://twitter.com/search?q=%23solr">#solr</a>
+ <a href="http://twitter.com/sematext/statuses/192979706734329858">@</a><a href="http://twitter.com/Hiring">Hiring</a>: Search Engineer Lead: Solr, ElasticSearch, Lucene, lead dev/consulting team <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://t.co/9B2L6qQW">http://t.co/9B2L6qQW</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/TheMalloum/statuses/192916174852464640">@</a>RT <a href="http://twitter.com/olamy">@olamy</a>: <a href="http://twitter.com/dadoonet">@dadoonet</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23Devoxxfr">#Devoxxfr</a> nice talk. question : différences avec <a href="http://twitter.com/search?q=%23solr">#solr</a> ?
+ <a href="http://twitter.com/girllostinit/statuses/192946971533778945">@</a>explain the <a href="http://twitter.com/search?q=%23ApacheLucene">#ApacheLucene</a> case to me. everybody uses it. API documentation sucks. no recent books (a bit better with <a href="http://twitter.com/search?q=%23Solr).">#Solr).</a> why??
</div>
</div>