<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Solr Integration: why do we bring Lucene 2.4.1 in the solr home libs? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/solr-integration-why-do-we-bring-lucene-2-4-1-in-the-solr-home/m-p/304505#M257635</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm still puzzled by the &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr-integration&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; jar and &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; zip artifacts.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Solr official release notes says 2.9.3. Why the dependencies of &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr-integration&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; artifacts all points to 2.4.1?&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 May 2013 15:01:00 GMT</pubDate>
    <dc:creator>pl_componize</dc:creator>
    <dc:date>2013-05-02T15:01:00Z</dc:date>
    <item>
      <title>Solr Integration: why do we bring Lucene 2.4.1 in the solr home libs?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/solr-integration-why-do-we-bring-lucene-2-4-1-in-the-solr-home/m-p/304504#M257634</link>
      <description>I'm working around Solr in Alfresco. I've sucessfully followed the docs to set up my Solr running, but I was wondering:The solr war (patched or unpatched) contains Lucene 2.9.3 already. However in the solr zip provided by Alfresco, you can see that the lib folder of the solr home contains the Lucene</description>
      <pubDate>Mon, 29 Apr 2013 14:20:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/solr-integration-why-do-we-bring-lucene-2-4-1-in-the-solr-home/m-p/304504#M257634</guid>
      <dc:creator>pl_componize</dc:creator>
      <dc:date>2013-04-29T14:20:54Z</dc:date>
    </item>
    <item>
      <title>Re: Solr Integration: why do we bring Lucene 2.4.1 in the solr home libs?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/solr-integration-why-do-we-bring-lucene-2-4-1-in-the-solr-home/m-p/304505#M257635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm still puzzled by the &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr-integration&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; jar and &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; zip artifacts.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Solr official release notes says 2.9.3. Why the dependencies of &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;alfresco-solr-integration&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; artifacts all points to 2.4.1?&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 May 2013 15:01:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/solr-integration-why-do-we-bring-lucene-2-4-1-in-the-solr-home/m-p/304505#M257635</guid>
      <dc:creator>pl_componize</dc:creator>
      <dc:date>2013-05-02T15:01:00Z</dc:date>
    </item>
  </channel>
</rss>

