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 11:21:34 UTC
svn commit: r813631 - 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 09:21:33 2012
New Revision: 813631
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 09:21:33 2012
@@ -438,15 +438,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/basvandewiel/statuses/192889984045420544">@</a>The only disadvantage to <a href="http://twitter.com/search?q=%23SOLR">#SOLR</a> on <a href="http://twitter.com/search?q=%23TYPO3:">#TYPO3:</a> you need to get all this Java stuff going.
+ <a href="http://twitter.com/irnnr/statuses/192904133580308481">@</a><a href="http://twitter.com/"EXT">"EXT</a>:indexed_search PRO Edition" aka "EXT:solr" ;) <a href="http://twitter.com/search?q=%23TYPO3">#TYPO3</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/jigalvh/statuses/192884989883449344">@</a><a href="http://twitter.com/jugglefish">@jugglefish</a> Use <a href="http://twitter.com/search?q=%23solr">#solr</a> instead? :-)
+ <a href="http://twitter.com/gregsochanik/statuses/192897240371699712">@</a>Great <a href="http://twitter.com/search?q=%23nservicebus">#nservicebus</a> talk last night. Looking forward to giving it a try with our new <a href="http://twitter.com/search?q=%23solr">#solr</a> incremental indexing "thing"! Thanks <a href="http://twitter.com/UdiDahan">@UdiDahan</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/KamillSokol/statuses/192877377414627330">@</a>lucidworks enterprise 2.1 out now <a href="http://t.co/wIiJgQ31">http://t.co/wIiJgQ31</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a>
+ <a href="http://twitter.com/basvandewiel/statuses/192889984045420544">@</a>The only disadvantage to <a href="http://twitter.com/search?q=%23SOLR">#SOLR</a> on <a href="http://twitter.com/search?q=%23TYPO3:">#TYPO3:</a> you need to get all this Java stuff going.
</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 09:21:33 2012
@@ -438,15 +438,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/basvandewiel/statuses/192889984045420544">@</a>The only disadvantage to <a href="http://twitter.com/search?q=%23SOLR">#SOLR</a> on <a href="http://twitter.com/search?q=%23TYPO3:">#TYPO3:</a> you need to get all this Java stuff going.
+ <a href="http://twitter.com/irnnr/statuses/192904133580308481">@</a><a href="http://twitter.com/"EXT">"EXT</a>:indexed_search PRO Edition" aka "EXT:solr" ;) <a href="http://twitter.com/search?q=%23TYPO3">#TYPO3</a> <a href="http://twitter.com/search?q=%23Solr">#Solr</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/jigalvh/statuses/192884989883449344">@</a><a href="http://twitter.com/jugglefish">@jugglefish</a> Use <a href="http://twitter.com/search?q=%23solr">#solr</a> instead? :-)
+ <a href="http://twitter.com/gregsochanik/statuses/192897240371699712">@</a>Great <a href="http://twitter.com/search?q=%23nservicebus">#nservicebus</a> talk last night. Looking forward to giving it a try with our new <a href="http://twitter.com/search?q=%23solr">#solr</a> incremental indexing "thing"! Thanks <a href="http://twitter.com/UdiDahan">@UdiDahan</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/KamillSokol/statuses/192877377414627330">@</a>lucidworks enterprise 2.1 out now <a href="http://t.co/wIiJgQ31">http://t.co/wIiJgQ31</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23lucene">#lucene</a>
+ <a href="http://twitter.com/basvandewiel/statuses/192889984045420544">@</a>The only disadvantage to <a href="http://twitter.com/search?q=%23SOLR">#SOLR</a> on <a href="http://twitter.com/search?q=%23TYPO3:">#TYPO3:</a> you need to get all this Java stuff going.
</div>
</div>