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 2013/04/01 11:21:03 UTC
svn commit: r856842 - 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: Mon Apr 1 09:21:03 2013
New Revision: 856842
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 Mon Apr 1 09:21:03 2013
@@ -460,15 +460,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="https://twitter.com//statuses/318441572356194304">@</a>: <a href="http://twitter.com/search?q=%23Apache">#Apache</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://t.co/shkrlmpvlf">http://t.co/shkrlmpvlf</a> secure deployment of solr.war on jboss
+ <a href="https://twitter.com//statuses/318650473039159296">@</a>: OpenSource Connections to present at DC Hadoop User Group <a href="http://t.co/lYuEjy6p3W">http://t.co/lYuEjy6p3W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a>
</div>
<div class="section-content">
- <a href="https://twitter.com//statuses/318152944799326208">@</a>: Why did you pick Solr over ElasticSearch or vice versa? <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://twitter.com/search?q=%23ElasticSearch">#ElasticSearch</a>
+ <a href="https://twitter.com//statuses/318648942512443393">@</a>: [linkedin]LinkedIn Open Tech Talk: Grant Ingersoll on What's New in Lucene and Solr <a href="http://t.co/ZaYbF3mFpk">http://t.co/ZaYbF3mFpk</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23mahout">#mahout</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23linkedin">#linkedin</a>
</div>
<div class="section-content">
- <a href="https://twitter.com//statuses/318071911991099394">@</a>: <a href="http://twitter.com/FlaxSearch">@FlaxSearch</a> <a href="http://twitter.com/watchingsearch">@watchingsearch</a> each have merits. There's beauty to "set it/forget it" that is GSA. However, I prefer <a href="http://twitter.com/search?q=%23Solr">#Solr</a> almost universally.
+ <a href="https://twitter.com//statuses/318441572356194304">@</a>: <a href="http://twitter.com/search?q=%23Apache">#Apache</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://t.co/shkrlmpvlf">http://t.co/shkrlmpvlf</a> secure deployment of solr.war on jboss
</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 Mon Apr 1 09:21:03 2013
@@ -460,15 +460,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="https://twitter.com//statuses/318441572356194304">@</a>: <a href="http://twitter.com/search?q=%23Apache">#Apache</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://t.co/shkrlmpvlf">http://t.co/shkrlmpvlf</a> secure deployment of solr.war on jboss
+ <a href="https://twitter.com//statuses/318650473039159296">@</a>: OpenSource Connections to present at DC Hadoop User Group <a href="http://t.co/lYuEjy6p3W">http://t.co/lYuEjy6p3W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a>
</div>
<div class="section-content">
- <a href="https://twitter.com//statuses/318152944799326208">@</a>: Why did you pick Solr over ElasticSearch or vice versa? <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://twitter.com/search?q=%23ElasticSearch">#ElasticSearch</a>
+ <a href="https://twitter.com//statuses/318648942512443393">@</a>: [linkedin]LinkedIn Open Tech Talk: Grant Ingersoll on What's New in Lucene and Solr <a href="http://t.co/ZaYbF3mFpk">http://t.co/ZaYbF3mFpk</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23mahout">#mahout</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23linkedin">#linkedin</a>
</div>
<div class="section-content">
- <a href="https://twitter.com//statuses/318071911991099394">@</a>: <a href="http://twitter.com/FlaxSearch">@FlaxSearch</a> <a href="http://twitter.com/watchingsearch">@watchingsearch</a> each have merits. There's beauty to "set it/forget it" that is GSA. However, I prefer <a href="http://twitter.com/search?q=%23Solr">#Solr</a> almost universally.
+ <a href="https://twitter.com//statuses/318441572356194304">@</a>: <a href="http://twitter.com/search?q=%23Apache">#Apache</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a> <a href="http://t.co/shkrlmpvlf">http://t.co/shkrlmpvlf</a> secure deployment of solr.war on jboss
</div>
</div>